Kagome, Miroku, and Sango: Desperate Situation!


InuYasha Season 4 - Episode 24

← Prev Episode 106 Next →

Episode information


Kagome, Miroku, Sango, Zettai Zetsumei






Shinjitsu no Uta




Original Airdate

April 14, 2003

Episode Statistics


Inuyasha and Kagome


(no credits available)

Kagome, Miroku, and Sango: Desperate Situation! (かごめ、弥勒、珊瑚、絶体絶命) is the one hundred sixth episode of the InuYasha anime.


  1. Inuyasha continues his battle with Ginkotsu, and he is unaware that Kagome and the others are currently with another member of the Shichinintai, Renkotsu.
  2. Inuyasha eventually defeats Ginkotsu, and rushes over the temple they are at where he also meets Renkotsu, still disguised as an innocent monk.
  3. Jakotsu confronts Kōga and intends to steal his Shikon no Tama shards, but before he can, Kōga runs off after Kagome.
  4. The still living Ginkotsu arrives at the temple and attacks Inuyasha again, and Renkotsu steals Kagome's Shikon no Tama shards, sets the temple on fire, and reveals his true identity to Inuyasha.
  5. Inuyasha manages to defeat Ginkotsu again and rushes to the burning building; Inuyasha finds a crying Shippō, who believes that Kagome and the others have died from Mukotsu's poison.



Inuyasha arrives at the temple where Kagome and the others are under Renkotsu's spell, but is distracted by the return of the supposedly destroyed Ginkotsu. Renkotsu sets the temple afire before revealing that he is also a member of the Band of Seven. By the time Inuyasha finds his friends with hopes to save them from the burning temple, Shippo tearfully informs him that they have all stopped breathing horrifying him.

This article or section is a stub. You can help by expanding it or contributing to the discussion.

Characters in Order of AppearanceEdit

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.