I noticed that according to the Wikipedia page for Jakotsu, he’s estimated to be about 5’10 (178cm) while Bankotsu is estimated to be 5’6 (172cm) which made me curious given that the height difference between them is definitely more than four inches.
Their heights were only speculated though whereas Kagome and Inuyasha’s listed heights had a source (The Art of Inuyasha) and while there is a height chart, no numbers are listed. Instead, the numbers came from a fan back in 2014 who did these estimations with research and math.
So while these heights aren’t really canon (it’s unlikely Rumiko will ever directly give them canon heights as the manga and anime both tend to be inconsistent with height) but the charts give us a good reference point into the heights of the main cast, so I took it upon myself to use them to make my own estimations, based on the height chart for the Band of Seven.
Thanks to @chickenstilldancing 's guide, I was able to find an actual scan of it online.
The height difference between Inuyasha and Kagome is six inches, so I put a grid over the image and changed the size until there were six boxes between the two to represent inches. From that, I got these numbers.
Bankotsu: 5’1”
Jakotsu: 5’11-6’0“ ~ish
Renkotsu: Just a little over 6’5”
Suikotsu: 6’3”~ish
Ginkotsu: 7’0” ½
Mukotsu: 2’11” ~ish
Kyōkotsu: Over 13 feet tall in first life
Additionally, while I was unable to find reference art of Bankotsu next to Banryū for height comparison, I was able to find Jakotsu next to the Jakotsutō.
I overlayed Jakotsu + the Jakotsutō over Jakotsu’s height until it roughly matched up, and marked the Jakotsutō as standing at about 3’2” feet, or 36 inches. Each individual blade is about 22 inches long and roughly 7 ½ inches at the longest point
This is funny because it means Jakotsutō is taller than Mukotsu is.
I did the same for Banryū after getting my grubby little hands on the Animation Settings Document book (thank you, sister). It measures at approximately 10 feet tall and 21 ½ inches wide.
As these are estimations the results are questionable, but it gives us an approximation which I think is fun.
I had a personal computer that was purchased when the screens were transisisting from the bulky cube into a flat screen technology.
I wanted to be able to type as if I was typing on an electric typewriter.
I wanted a Hewitt Packard “Envy” laptop in order to see # YouTube videos that were in a specified range of video choices.
The Hewlutt apackard laptop was the latest laptop 10 years ago that would enable anyone to see videos.
The good 👍 thing about the said laptop was that it was portable and I was able to carry it with me on a Greyhound bus to the New London [CT] ferry dock during daytime hours.
This is in the range of 1998 through 2001.
I was lucky enough to
I was lucky that a Greyhound employee “volunteered” to hold a “small” piece of luggage [that is standard in 2026-]
I was lucky that a restaurant allowed me to eat and finish my drink and still remain seated until [my “ plan” was complete]
This occurred a numismatic moments of completed time frames.
so who said girls with glasses are not allowed to have up-to-speed time framed passes?
Rethinking estimations in AI-driven processes has become essential in the fast-paced world of IT and software development. Estimations shape project timelines, budgets, and expectations, yet traditional practices often lead to inefficiency and frustration. In a previous post, I explored the #NoEstimates movement and its call to move beyond traditional estimation techniques. Here, I’ll dive deeper…
This is a well known fact that humans suck at estimations.
We always think that we can estimate how long something would take and when we try to do it — never comes out to be anywhere close.
The main reason is that we always take the happy path while estimating something, which is often not what happens in reality. Even if we try to factor in the complexities and hurdles, we end up being wrong…