Fisher Wood Stove - Anybody know the year?

  • Active since 1995, Hearth.com is THE place on the internet for free information and advice about wood stoves, pellet stoves and other energy saving equipment.

    We strive to provide opinions, articles, discussions and history related to Hearth Products and in a more general sense, energy issues.

    We promote the EFFICIENT, RESPONSIBLE, CLEAN and SAFE use of all fuels, whether renewable or fossil.

Sully1515

Member
Jun 5, 2017
61
New Hampshire
Just curious,

My wife and I purchased a small farm that had a Fisher Grandma Bear wood stove in it. She's a beast, great BTU's from that stove. One of the best wood stoves I've ever owned.

My only question is the year. Does anybody know just by looking at this image the approximate year it was made? Is there anywhere on the stove that may show this information?

I can always take more pictures if need be.
fisher wood stove.jpg
 
That stove looks very close the wall behind it. What is behind the stone?
 
Behind the stone is concrete board-ish material, similar to tile board, then sheet-rock.

The stove guy came to inspect it and actually moved it closer to the wall. Originally, it was about 1' further (in front) than where the stove stands now.
Do you think that could cause damage to the wall, sheetrock or combust any way possible?
 
My only question is the year. Does anybody know just by looking at this image the approximate year it was made? Is there anywhere on the stove that may show this information?
There should be a serial # on the rear of the wood stove , near the bottom & from what I've learned the last 2 digits will tell the year made. I've also seen serial # on the front too, just above the doors . You will have to look very closely with a good light too. Digits are usually 1/4 " tall . I"m guessing maybe a '77 or '78 model . With the older style draft caps.
 
The stove guy may have moved the stove closer to the corner if the hearth requirement in front of the stove was inadequate. It appears to be a code and safety violation. What is the actual distance from the stove back corners to the wall? Unlisted stoves are supposed to have 3' clearance to the nearest combustible which in this case would be the sheetrock. The stone veneer wall is not an NFPA 211 shielded wall.
 
  • Like
Reactions: bholler
The stove guy may have moved the stove closer to the corner if the hearth requirement in front of the stove was inadequate. It appears to be a code and safety violation. What is the actual distance from the stove back corners to the wall? Unlisted stoves are supposed to have 36" clearance to the nearest combustible which in this case would be the sheetrock. The stone veneer wall is not an NFPA 211 shielded wall.

I was also thinking the same thing....I'll have to give him a call and re-do the piping. Thanks..
 
Last edited by a moderator:
There were no serial numbers before UL Listing began. Some used "Stove Numbers" in the order built. UL tags have serial number, fabricator name, location, and date separate. The date is not part of the Serial Number.

I don't think NH stamped theirs. NY and NJ stamped the top right rear corner and PA used weld on bottom.
They usually added the state initials first.
The springs are a newer plated style which was quite a while AFTER All-Nighter was formed by that fabricator in February of 1977. It could have been one sitting around when their license was revoked, and the newer more common springs were added when sold OR it came from somewhere else using up the old style draft caps. That was common since you'll see many with later bent handles and newer springs with the old Baxter caps.
The All-Nighter hearings weren't until 1980, so it's unsure how many Fishers were sold by them during that time.
The stainless springs of the time gave no problems and few to none were replaced with the newer style as far as I know.
 
  • Like
Reactions: Sully1515
@begreen: I want to thank you for recommending to move the stove further from the wall. To me, I thought it was too close, but, it was good to have someone else have a look at this. This issue has been taken care of and pulled back up to code Thank you for pointing that out!