Mini-Series: This is Part 12 — Bangalore Solo (Season 2). Previous: Part 11 — Bangkok. Part 9 roadmap: Bangalore Roadmap. Series start: Part 1 — Rock Bottom Pattern.

Bangalore Solo: No Partner, No Hiding

Doubles is honest.

Solo is brutal.

That’s the cleanest way I can put it.

In doubles, even when the race gets ugly, there is still some shared damage. You can split work. You can recover while someone else carries the station for a few extra reps or a few extra meters. You still have to be fit, obviously. You still have to suffer. But the event gives you small places to hide.

Solo does not.

In Solo, every run is yours. Every bad transition is yours. Every rep that slows down because your legs have gone on strike is yours. Every stupid decision you make in the first half comes back personally in the second half. There is no one to rescue the pace. No one to absorb the backend damage. No one to quietly patch the hole you created five stations earlier.

And that is exactly why Bangalore Solo matters so much to me.

Not because it’s glamorous.
Not because “solo” sounds hardcore in a caption.
Not because I want to manufacture some dramatic hero arc.

It matters because it is the cleanest test of whether this whole transformation has really matured.

By now, the external proof is already there. I’m not starting from the same body or the same mindset I had when I was drifting through the heavier years. I’ve gone from 103 kg at my heaviest to 90 kg at the official start of this serious transformation, down to the low-70s by January 2026 (73.8 kg on Jan 11). I’ve finished HYROX Mumbai. I’ve raced Yoddha. I’ve raced Bangkok. The story has already changed.

So Bangalore Solo is not about proving that I can change.

It’s about proving that I can hold structure when there is nowhere left to hide.

That is a very different thing.

If I strip away all the fluff, this race comes down to three real questions.

1. Can I run under fatigue without turning every kilometer into a recovery lap?

This is still the biggest lever in the whole event.

HYROX does not politely separate running from stations. That fantasy disappears the moment the race starts. The entire point is that you have to keep returning to the run while carrying station damage forward. That means the problem is not only how fast you can run fresh. The problem is how little you fall apart after the event has already started taxing you.

For me, this means one thing: compromised running has to be real, not theoretical.

Not “I can run one good kilometer.”
Not “my watch says my pace is improving.”
Not “I felt strong on Tuesday.”

The question is whether I can keep finding decent kilometers after SkiErg, after sleds, after rowing, after lunges, when the body is trying to talk me into protection mode.

2. Can I manage the backend without cramping or collapsing?

If you want the ugly truth about my race profile, here it is: backend stations are still where the race can start charging interest.

Lunges. Wall balls. Late fatigue. Calves making threats. Quads tightening. Form getting expensive. Breathing getting more emotional than it should.

That is not some mystery. It’s the obvious place where Solo can expose me.

And honestly, I’d rather say that clearly now than act surprised later.

Because this is where a lot of race goals become nonsense. People chase a time without respecting which part of the race is likely to mug them in broad daylight. I know where my danger lives. That is actually an advantage, as long as I don’t become lazy with that knowledge.

3. Can I keep transitions disciplined when tired?

This one sounds boring, which is exactly why it matters.

Bad transitions don’t feel cinematic. They feel small. A little walk here. A little drift there. A little pause because your brain wants to renegotiate effort. But races like HYROX are built on those tiny leaks. A casual Roxzone becomes a habit. A habit becomes a minute. A minute becomes the difference between a race you control and a race that controls you.

So one of my rules for Bangalore is simple:

No default strolling.
No emotional wandering.
No pretending transitions don’t count.

They count.

What “ready” actually means

Now, what does “ready” actually mean for this race?

It does not mean one magical simulation where everything clicks.
It does not mean feeling invincible in the taper.
It does not mean trying to bully the race with motivation.

Ready means boring things are in place.

The engine is built enough to protect heart-rate chaos.
The calves and shins are durable enough to not become a side quest.
The fueling is handled like an adult, not guessed like a gambler.
The pacing is controlled early enough that the backend still has a functioning person left inside it.
The key weak stations have been trained honestly, not hidden behind stronger ones.

That’s readiness.

Not hype. Structure.

What support made possible

This is where I have to mention something else that matters in the story, because pretending otherwise would be fake: none of this transformation happened in a vacuum.

Shubhangini has been part of this journey from the beginning. She was there in the years when the discipline wasn’t automatic. She was there in the push out of drift mode. She was there when health became more than a loose plan. She was there in the races too, not just as a spectator, but as someone whose own consistency kept mine from floating away. That matters. In a story like this, support is not a soft footnote. Sometimes it’s the scaffolding.

But Solo is where scaffolding meets structure.

At some point, the building has to stand on its own.

That’s what Bangalore is to me.

Not a motivational poster.
Not a fantasy clock goal dressed up as destiny.
Not some grand statement that everything is now perfect.

It’s a test of whether I can put together a race that looks disciplined from the inside.

That means:

* no panicking early because adrenaline made me stupid,
* no overspending in the first half because ego wanted a better screenshot pace,
* no pretending the backend will magically behave if I ignore its history,
* no leaving hydration, sodium, or fueling to chance,
* no acting shocked if sloppy transitions create a sloppy finish.

What success looks like

And what does success look like?

Success is not perfection.
Success is not some fantasy where the whole race feels easy.
Success is not proving something to strangers who will forget your split chart in twelve seconds.

Success is this:

I race with control.
I respect the event.
I do not hand free time away in transitions.
I do not let backend weakness turn into backend collapse.
I finish knowing the result came from structure, not desperation.

That’s the standard.

Because at this point in the journey, I’m not chasing a dramatic breakthrough.

I’m chasing mastery of the obvious things I used to ignore.

And there is no better race than Solo to tell me whether I’ve actually earned that next version of myself.

No partner.
No hiding.

Perfect.

---

If you’re racing Bangalore too, tell me your two biggest limiters. I’ll turn them into a simple 4–6 week fix.