“Take this package to Mr. X.”
Normal delivery requires an address, a label, collection, sorting, line-haul transport, and last-mile delivery.
With Tonkaraton, the workflow is different.
In the comic that inspired this thought experiment, the user first survives the verbal rule, then says that a certain person “became one of your companions.” Tonkaraton then heads toward that person.
If it can also be made to carry a parcel, it stops looking like a monster and starts looking like a bizarre delivery platform:
a zero-fee, bicycle-equipped last-mile courier whose routing key is a person’s name.
There is one small problem.
The more the system scales, the more Tonkaratons there are and the fewer humans remain.
Eventually, not only the labor shortage but also delivery demand itself disappears.
1. The baseline Tonkaraton specification
【Verified baseline】
Tonkaraton is commonly described as a bandage-wrapped figure carrying a sword and riding a bicycle.
The usual rule is:
- It orders a passerby to say “Tonkaraton.”
- If the person says it after being ordered, it leaves.
- If the person refuses, the person is attacked.
- In some variants, saying “Tonkaraton” before being ordered is also a failure.
- Many retellings add that victims become new Tonkaratons.
The character appeared in the 1994 series “Gakkou no Kowai Uwasa: Hanako-san ga Kita!!” (“School’s Scary Rumors: Hanako-san Has Come!!”). Nippon Columbia’s official DVD listing confirms that the series aired inside “Ponkickies” in 1994, and Apple TV lists “Kaijin Tonkaraton” in the second episode package.
So the core cluster—bicycle, verbal rule, punishment for failure, and replication—has roots in older media, not merely recent internet summaries.
2. “X became your companion” is a routing extension, not a universal rule
This distinction matters.
The comic that triggered this discussion depicts an additional trick: after giving the correct response, the person says that someone else has become one of Tonkaraton’s companions, causing it to head toward that person.
The general reference sources checked for this article do not consistently describe that behavior as a standard Tonkaraton rule.
So the article separates:
widely documented folklore/media rules from the routing gimmick used in this particular work.
Otherwise, different versions of an urban legend get flattened into a fake single canon.
Even monsters need version control.
3. As a logistics system, it is absurdly powerful
Assume the routing gimmick works and Tonkaraton is willing to carry a parcel.
The input requirements are minimal:
- Encounter Tonkaraton.
- Say its name at the correct time.
- Give the destination person through the “companion” clue.
- Hand over the parcel.
- Let the built-in bicycle handle the last mile.
A large chunk of ordinary delivery infrastructure—address entry, map lookup, navigation, route optimization—would effectively be hidden inside the monster.
And it ships with a bicycle.
Its last-mile fit is suspiciously good.
No salary negotiation.
No recruitment.
No onboarding.
No gasoline.
A logistics executive staring only at cost metrics would glow for about three seconds.
4. The fatal flaw: voice-only UI
The accessibility design is catastrophic.
The protocol depends on spoken interaction.
Lose your voice.
Damage your throat.
Freeze in panic.
Speak at the wrong time.
Any of these can turn a delivery request into a personal safety incident.
The single point of failure is not GPS, a cloud server, or payment infrastructure.
It is the user’s ability to speak.
There is no documented handwriting mode, smartphone input, sign-language mode, API, or barcode reader.
As supernatural SaaS, this gets a P0 in the first UX review.
5. Scaling increases couriers while deleting customers
The replication rule is worse.
Let H be the number of humans and T the number of Tonkaratons.
Each conversion roughly produces:
H → H - 1
T → T + 1
From the carrier’s narrow viewpoint, that looks like one new worker.
From the market’s viewpoint, it is one fewer potential customer.
If delivery demand per human is d and delivery capacity per Tonkaraton is c:
Demand ≈ dH
Capacity ≈ cT
As conversion spreads:
capacity rises while demand falls.
The supply-demand gap therefore improves at terrifying speed.
Society did not improve.
The denominator was removed.
6. Against real logistics shortages, the KPI dashboard looks beautiful
Japan does face genuine logistics labor constraints.
Japan’s Ministry of Land, Infrastructure, Transport and Tourism has long cited a counterfactual estimate that, without measures, freight capacity could be short by about 14% in FY2024 and about 34% in FY2030.
But there is an important update.
Later ministry material states that the projected roughly 14% FY2024 gap was “largely resolved” through public-private measures. The 2030 challenge remains, and the government adopted the Comprehensive Logistics Policy Outline for FY2026–FY2030 in March 2026.
So “Japan is currently 34% short of freight capacity” would be wrong.
The 34% figure is a future no-action scenario.
Now insert Tonkaraton into the KPI dashboard:
- Courier count: up
- Hiring cost: near zero
- Labor cost: near zero by fictional rules
- Fuel cost: low because bicycles
- Delivery demand: down as population falls
- Redelivery: probably solved in the worst possible way
- Labor shortage ratio: improved
On the dashboard, it is excellent.
At the highest-level goal—“keep human society functioning”—it is a total failure.
7. Free is powerful, but the external cost is infinite
The sales pitch is obvious: delivery is free.
Within the fictional setup, Tonkaraton does not invoice for wages, benefits, recruitment ads, uniforms, training, or vehicle fuel.
Accounting loves it.
Society does not.
The external costs include:
- safety risk to sender
- safety risk to recipient
- human loss after protocol failure
- self-replication of couriers
- shrinking market population
- no workable insurance or legal framework
- the concept of a “delivery incident” collapsing entirely
Shipping fee: ¥0. Total social cost: unmeasurable.
Cheap services often have hidden costs.
This one hides civilization in the footnotes.
8. The real joke is local optimization
The funniest part is not the monster. It is KPI design.
If the only objective is “reduce the logistics labor shortage,” Tonkaraton is extremely effective:
increase delivery workers, reduce delivery demand, do both at once.
But the actual objective is:
deliver necessary goods to necessary places while humans remain safe and alive.
Solving delivery by removing the people who need delivery reverses means and ends.
This is Goodhart-style comedy: when a metric becomes the target, it can stop being a good metric.
Optimize one shortage ratio hard enough and you can destroy the larger system the metric was supposed to serve.
Companies, governments, and AI systems can make the same category of mistake.
Tonkaraton just demonstrates it while wrapped in bandages.
9. Conclusion: the logistics problem disappears because the logistics society disappears
The final spec sheet:
- bicycle included
- person-name routing in the comic variant
- no wage demand
- no recruitment
- self-replicating workforce
- falling population reduces demand
- voice UI failure can be fatal
- multiple Tonkaratons can create contradictory rule traps in some variants
As a labor-shortage solution, it is brutally efficient.
As social policy, it is brutally insane.
The endpoint looks like this:
Couriers: many
Packages waiting: almost none
Destinations: almost none
Logistics labor shortage: solved
Humanity: out of stock
“Use it because delivery is free” is correct price comparison.
It just forgot to include the cost of keeping civilization.
