FANDOM


Icon-zero-one
This article is about a/an episode in Kamen Rider Zero-One.

Firefighters Battling the Blaze (ワレら炎の消防隊 Ware-ra Honō no Shōbōtai) is the twenty-sixth episode of Kamen Rider Zero-One. It features the first on-screen transformation of Kamen Rider Jin Burning Falcon.

Synopsis

The fourth round of the "5-Round Workplace Showdown" between Hiden Intelligence and ZAIA Enterprise has arrived! This time, it is a showdown among firefighters! By creating drills simulating real-life fire scenarios, both sides will determine whether a Firefighter-Type Humagear or a human firefighter with a ZAIA Spec will be able to rescue the most civilians! A building has been set up to recreate a rubble rescue on the basement floor, the first floor a fire rescue, and the second floor from a smoke rescue! However, suddenly during the midst of their competition, a mysterious Raider appears and causes an explosion!

Plot

to be added

Cast

Guest Cast

Suit Actors

Forms and Collectibles Used

Progrisekeys

  • Key Used:
    • Zero-One
      • Freezing Bear, MetalCluster Hopper
    • Vulcan
      • Assault Wolf
    • Jin
      • Burning Falcon
    • Thouser
      • Amazing Caucasus, Freezing Bear (Jacking Break)
  • Form Used:
    • Zero-One
      • Freezing Bear, MetalCluster Hopper
    • Vulcan
      • Assault Wolf
    • Jin
      • Burning Falcon

Zetsumerisekeys

  • Key Used:
    • Thouser
      • Awaking Arsino

Errors

  • The firefighters (and Aruto) reacted to the reveal of the victims on each floor of the building, which shouldn't have been possible as they could not see the visual review that was shown only to the viewers.
    • Although given that Yua had a holographic display up to explain the rules, that may be how they saw the victims.
  • After their duel, both Jin and Fuwa conclude that Sting Scorpion Progrisekey must be with ZAIA because it was Yua who recovered Horobi, despite the Progrisekey was last seen with Jin during his fight with Aruto.
    • Although it could be possible it was discovered and confiscated by Yua at the aftermath of the battle as in the next episode, Gai is shown using the Scorpion Progrisekey in the Thousand Jacker.

Notes

Zero-One Ep 26 Closing Screen
  • Viewership: 3.9%
  • Closing Screen Progrisekeys:
    • Kamen Riders: Zero-One, Thouser
    • Progrisekeys:
      • Zero-One: MetalCluster Hopper
      • Thouser: Amazing Caucasus
  • Ending Sponsers Progrisekeys
    • 1. Rising Hopper
    • 2. Shooting Wolf
    • 3. Rushing Cheetah
  • Count at episode end
    • Progrisekeys in Zero-One's possession: Rising Hopper, Biting Shark, Flying Falcon, Flaming Tiger, Freezing Bear, Breaking Mammoth, Shining Hopper, Hopping Kangaroo, MetalCluster Hopper
    • Progrisekeys in Vulcan's possession: Shooting Wolf, Punching Kong, Gatling Hedgehog, Trapping Spider, Assault Wolf
    • Progrisekeys in Valkyrie's possession: Rushing Cheetah, Lightning Hornet
    • Progrisekeys in Jin's possession: Burning Falcon
    • Progrisekeys in Thouser's possession: Amazing Caucasus, Sparking Giraffe, Crushing Buffalo, Exciting Stag, Splashing Whale, Dynamaiting Lion, Storming Penguin, Sting Scorpion
    • Progrisekeys in Daiki Kyogoku's possession: Scouting Panda
    • Progrisekeys in unknown possession: Amazing Hercules
    • Humagear Progrisekeys in Zero-One's possession: Is, Uchuyaro Subaru, Saikyo Takumi Oyakata, Dr. Omigoto, Sumida Smile, Mamoru, Bengoshi Bingo, Ikkan Nigiro, Okureru, Matsuda Enji, G-Pen, Matsurida Z
    • Zetsumerisekeys in Thouser's possession: Awaking Arsino, Berotha, Kuehne, Ekal, Neohi, Onycho, Gaeru, Dodo
  • This episode features an updated opening that includes Jin Burning Falcon.
  • The act of resuscitation performed by Takeshi Homura on the victim that suffered cardiac arrest is not practical to be done at the scene of fire and smoke in real life situation because it would risked himself being another victim to be rescued. In actuality, he should have evacutated all the victims first and leave the cardiac arrest patient to the medics for that purpose.

External links

References

Community content is available under CC-BY-SA unless otherwise noted.