No injuries in Rochester Subway fire that forced crews to open roof

Zero injuries were reported after an overnight fire damaged a Subway restaurant in northwest Rochester, Minnesota—a fortunate outcome for an emergency that required firefighters to open the roof to reach hidden flames. The damage extended beyond the restaurant’s interior, but its financial cost and the timetable for getting the business back into service have not been established. ^{1 2}

The Rochester Fire Department was called to 1103 Seventh St. NW at about 3 a.m. on Sunday, November 1, 2026. The restaurant was closed when the fire broke out, according to the Winona Journal’s account of the aftermath. That report described reopening as “not imminent,” without giving a schedule. ^{1 6}

When crews arrived, smoke was coming from the roof and from inside the building. Firefighters initially sprayed water from outside, but that did not finish the job: concealed areas of fire and remaining hot spots required access through the roof, the Post Bulletin reported. ¹

Crews opened portions of the roof to reach those areas, then opened it further to ventilate the structure and let smoke escape. KTTC’s subsequent account, citing the Rochester Fire Department, confirmed that the fire had extended into the roof. The openings were part of the effort to extinguish the fire and clear the building, not an explanation of how the blaze began. ^{1 2}

Rochester police and Mayo Clinic Ambulance Service also responded. The Post Bulletin reported no injuries either in the fire or during the emergency response. The accounts do not establish how many people, if any, were inside when the fire started, and they provide no basis for describing a rescue or evacuation at the restaurant. ¹

The response accounts establish what firefighters encountered and why they needed roof access. They do not establish an ignition source. A fire reaching the roof is a description of its spread; it is not, on its own, evidence of an electrical fault, a kitchen-equipment failure or any other particular cause.

The Post Bulletin’s November 1 report said the damage remained to be calculated. KTTC reported on November 2 that both the cause and the cost were still undetermined. Those are dated assessments, not proof that investigators or the business have made no determination since. No verified later cause finding or final dollar-loss figure is available to report here. ^{1 2}

The dates also matter in reading the coverage: KTTC’s November 2 publication described the same Sunday fire, not a second incident. The call at about 3 a.m. belongs to November 1. Local reporting supplies the response details, including the fire department’s account relayed by KTTC. ^{1 2}

For customers and the business, the unresolved practical question is when the restaurant can operate again. The Winona Journal’s November 1 description supports only that reopening was not expected soon in the immediate aftermath. It does not establish a permanent closure, a defined shutdown period or a later reopening date. ⁶

Subway’s official page for the address lists regular hours and ordering services, but it is undated and carries no fire-related reopening announcement. A location listing is useful for identifying a restaurant; without a dated update, it cannot demonstrate that this restaurant resumed service after this fire. Its current operating status therefore remains unverified. ⁷

In its safety message, reported by KTTC, the fire department encouraged commercial property owners to reduce fire risks and protect occupants, and asked business owners to ensure employees know their evacuation procedures. That is a general prevention reminder, not a finding that this restaurant violated a safety rule or that employee actions contributed to the blaze. The established outcome remains a damaged restaurant and no reported injuries; the cause, final loss and recovery timetable require further confirmation. ²