At 34 years old and 106 kg (235 lbs), I decided my first marathon would be sub-4 hours.
No “just finish.”
No soft landing.
Straight to 3:59:59 or bust.
I had just run a 1:49 half marathon and in my head the math was clean. Double it. Add a few minutes. Done. That version of me had no idea what 42.2 km actually demands.
Eight months later — after pre-dawn alarms, humid Bali long runs, one calf strain, and more ego checks than I care to admit — I understood something: sub-4 isn’t a math problem. It’s a durability project. It’s pacing discipline. It’s fueling on schedule. It’s showing up when your legs feel like bricks and running anyway.
If you’re heavier. If you’re not built like a string bean. If you’re wondering whether sub-4 is realistic for a first marathon — this isn’t about hype. It’s about what it actually takes. And what changes in you over months when you commit to chasing it the right way.
The 10K That Humbled Me
Early in training, I signed up for a local 10K “to see where I’m at.”
Translation: I wanted reassurance.
I went out at around 7:30 per mile.
Which had absolutely nothing to do with my 9:09 marathon pace target.
But adrenaline told me I was invincible.
By mile 3, I was cooked.
Lungs on fire. Legs like lead. That awful metallic taste in your mouth when you know you’ve blown it.
The runners I had confidently surged past early?
They floated by me one by one.
That 10K wasn’t even a quarter of a marathon. And it exposed me.
It taught me something critical:
Pace isn’t a suggestion. It’s respect.
The Quiet Grind
Most training wasn’t dramatic. It was quiet.
5:00 a.m. alarms.
Slipping out while the house slept.
Running through Bali’s thick humidity before sunrise. (Yes, even at dawn the air can feel like soup.)
Some mornings my legs felt like bricks. Other mornings I’d find rhythm and feel strangely powerful.
The heat became its own kind of training partner. If I could survive 28 km in tropical humidity, surely race day in cooler weather wouldn’t break me.
Over months, I lost some weight.
But more importantly, I changed mentally.
I started thinking like a marathoner.
I read obsessively. Foam-rolled while watching TV. Overanalyzed every niggle. Started viewing easy days as strategic instead of lazy.
The Calf Strain (Because Of Course)
Mid-cycle, I pushed a long run too far.
Arrogance.
I added extra distance because I “felt good.”
Two days later? Calf strain.
Two weeks off.
That was torture.
Not because of fitness loss — but because of identity. I was so locked into the sub-4 vision that stopping felt like failure.
That injury taught me something important:
Consistency beats hero workouts.
Always.
The Mental Battle
The hardest runs weren’t the fastest ones.
They were the 20+ km solo efforts where doubt creeps in.
“Why are you doing this?”
“You’re too heavy for this.”
“You’re not built for sub-4.”
But every time those thoughts surfaced, I pictured the clock.
3:5X:XX.
Crossing the line.
Probably crying.
That image became fuel.
Eight Months Later
By the time I stood at the start line, I wasn’t the same runner.
I was lighter.
Stronger.
Less naive.
Whether the clock said 3:59 or 4:02, I knew I had done the work.
And that matters.
Sub-4 isn’t just about pace math.
It’s about building durability. Respecting recovery. Managing ego. Learning patience. Fueling properly. Surviving doubt.
The guy who thought “double the half plus a few minutes” was enough?
He had no idea what he was signing up for.
The version of me on that start line?
He did.
And that’s what eight months really gave me.
Why Sub-4 Is Tough but Reasonable
Let’s just say it clearly.
Sub-4 means 42.2 km at 5:41 per km (9:09 per mile).
That’s not sprinting.
But it’s not jogging either.
It’s that uncomfortable middle. The pace where you’re working. Where you can talk in short phrases but you’d rather not.
Holding that for a few miles? Fine.
Holding it for four hours?
Different animal.
It’s basically running two half marathons back-to-back at a pretty serious effort… and then tossing in an extra 2 km at the end just because the marathon gods felt petty.
For a first-timer, that’s not small.
It’s Not Just Pace. It’s Fatigue Stacking Up.
If you’re aiming for 3:59, you’ll probably hit halfway in about 1:58–1:59.
Pause there.
That’s already almost two hours of running.
And then you have to do it again.
On legs that are getting progressively heavier.
For me, somewhere around 30 km (18–20 miles) is where the unknown begins. That’s where pace starts slipping if you’ve made even one mistake. Went out too fast. Skipped a gel. Didn’t respect the heat.
That’s “the wall” territory.
Sub-4 isn’t just about speed. It’s about durability. Energy management. Not falling apart late.
The Life Stuff Nobody Talks About
Most of us chasing sub-4 are not pros.
We have jobs. Kids. Spouses. Deadlines. Groceries.
I remember weeks juggling:
- 5 a.m. runs
- Full workdays
- Evening family time
There were days I’d finish an 8 km run exhausted… then immediately switch into toddler-chasing mode. Honestly, sometimes that felt harder than intervals.
Marathon training with a time goal is like adding a part-time job to your life.
There’s also the guilt.
“Am I being selfish running this much?”
“Should I be doing something else right now?”
Fatigue doesn’t just come from miles. It comes from life stacking on top of miles.
That’s part of why sub-4 is tough.
The Fear of the Wall
I was low-key terrified of 30–35 km.
Like, irrationally so.
I had this image of suddenly cramping, shuffling, walking it in while watching 3:59 drift away on the clock.
That fear haunted my long runs.
And then there was the internet.
I spent way too many hours reading:
- “Is 1:54 half good enough for sub-4?”
- “Should I run 4 or 5 days per week?”
- “Long runs at goal pace or slow?”
One blog says slow long runs only.
Another says practice marathon pace late in long runs.
One guy swears by 3 days a week.
Another says you need 6.
It drove me crazy.
Eventually I realized: it’s personal.
Principles matter. But execution varies.
At some point, you have to pick a plan and trust it.
The Half-to-Marathon Trap
Here’s the rule everyone quotes:
Marathon time ≈ 2 × half-marathon time + 15–25 minutes.
It’s not perfect, but it’s useful.
When I started, my half PR was 1:54 (114 minutes).
Double that = 3:48.
Add 15–25 minutes → 4:03 to 4:13.
Translation?
On paper, I wasn’t sub-4 yet.
That stung.
It meant sub-4 was possible — but only if I improved and executed well.
I saw plenty of stories of 1:50 half runners finishing marathons in 4:05–4:10 because something went wrong.
So I stopped treating sub-4 like a wish.
I treated it like a project.
Everything had to line up:
Training.
Pacing.
Fueling.
Weather.
Luck.
Tough… But Not Mythical
Sub-4 is hard.
But it’s not elite.
It’s kind of a sweet spot goal for everyday runners who are willing to work.
It won’t happen by accident.
But it’s not magic either.
I started repeating this to myself:
“Sub-4 isn’t a lottery win. It’s earned.”
That changed my mindset.
Instead of fearing the goal, I focused on stacking days.
Do the run.
Eat right.
Recover.
Repeat.
Breaking 4 hours isn’t mythical.
It’s what happens when training, pacing, and fueling all line up on the same day.
Science – What Happens to Your Body in a Marathon?
I’m a bit of a nerd about this stuff.
Understanding what’s happening under the hood made the suffering feel… logical.
Less personal.
Let’s break it down.
- Energy Systems & The Wall
The marathon is basically a fuel management game.
Your body runs primarily on:
- Carbohydrates (stored as glycogen)
- Fat
Early in the race, you’re burning a mix — but glycogen does a lot of the heavy lifting because it’s high-octane fuel.
The problem?
Glycogen storage is limited.
Even if you carbo-load well, most people have roughly 90 minutes to 2 hours worth of glycogen at marathon effort.
After that, things start shifting.
Around 30 km, glycogen gets low.
Your body leans more on fat.
Fat is abundant. You’ve got tens of thousands of calories sitting there.
But fat burns slower.
It’s like paper vs logs in a fire.
Paper (glycogen) burns hot and fast.
Logs (fat) burn steady but slower.
As glycogen drops, pace drops.
That’s part of the wall.
The other part? Your brain.
Your brain runs heavily on glucose.
When blood sugar dips, your brain panics a little.
Fatigue hits. Negative thoughts flood in. You feel dizzy, heavy, emotionally weird.
Your brain is basically saying:
“Slow down. We’re low on fuel.”
That’s why gels matter.
That’s why sports drink matters.
During long runs, I practiced taking gels so my gut could handle it and so I could delay glycogen depletion.
Long runs also teach your body to burn fat more efficiently. Over time, your muscles adapt — enzyme changes, mitochondrial density increases — so you spare glycogen better.
Those 2–3 hour long runs weren’t just mental toughness.
They were metabolic training.
- VO₂max & Lactate Threshold
VO₂max is your engine size.
It’s the maximum oxygen your body can use per minute.
Measured in ml/kg/min.
Bigger engine = more potential.
But in a marathon, you’re not redlining the engine.
You’re cruising at a percentage of it.
That’s where lactate threshold comes in.
Lactate threshold is the effort level where lactate starts accumulating faster than you can clear it.
For most runners, that’s roughly the fastest pace you could hold for about an hour.
For amateurs, that might align with 10K pace.
For elites, closer to half marathon pace.
If you run above threshold, fatigue compounds quickly.
Marathon pace needs to sit comfortably below that threshold.
Ideally it feels like a 6–7 out of 10. Not 9.
The higher your lactate threshold relative to marathon pace, the more sustainable 9:09 per mile becomes.
That’s why I did tempo runs.
20–40 minutes at threshold effort.
Sometimes broken into chunks.
Early on, 5:00/km tempo felt tough.
Months later, 5:00/km felt controlled.
That’s threshold moving upward.
Science shows that threshold training increases mitochondrial density and enzyme activity, allowing you to sustain higher percentages of VO₂max longer .
Well-trained marathoners can sustain 80%+ of VO₂max for long periods .
Early in training, marathon pace felt close to my ceiling.
Later, it felt like something I could sit on.
That shift is everything.
- Running Economy & VO₂max Work
Running economy is basically how efficiently you use oxygen at a given pace.
Two runners with identical VO₂max can perform differently if one wastes less energy per stride.
Economy improves through:
- Lots of easy mileage
- Some faster running
I added interval sessions like 5 × 1 km at 10K pace.
They were hard.
Heart rate high. Breathing heavy.
That’s VO₂max territory.
High-intensity intervals have been shown to increase VO₂max significantly — one study (Helgerud et al.) found ~7% improvements after 8 weeks of interval training .
I didn’t overdo it. Injury risk is real.
But every other week in the mid-phase, those sessions made my engine feel bigger.
When I went back to marathon pace, it felt calmer.
Less strained.
More efficient.
VO₂max gains don’t endlessly translate to marathon performance — there are diminishing returns.
But if you start with room to grow, improving VO₂max helps.
And faster running subtly cleans up form.
After a cycle of 1K repeats, my marathon pace stride felt smoother.
Less muscling it.
More flowing.
And when you’re trying to hold 9:09 per mile for four hours, smooth matters.
A lot.
- Cardiac Drift and Heat
Cardiac drift messed with my head the first time I really paid attention to it.
I’d head out for a long run, settle into what felt like an easy rhythm. Say 6:10–6:20 per km. Heart rate around 140 bpm. Breathing calm. Feels sustainable.
Two hours later? Same pace. Heart rate 155.
Nothing changed externally. But internally, everything had.
That’s cardiac drift.
Here’s what’s going on under the hood.
When you run for a long time, especially in heat:
- You sweat → fluid loss → blood volume drops slightly
- Blood gets redirected to your skin → your body tries to cool itself
- Stroke volume (blood pumped per beat) decreases
If stroke volume drops, the heart compensates. It beats faster to deliver the same oxygen.
So heart rate rises, even if pace stays identical.
I saw this constantly on 2+ hour runs in Bali. The humidity there is no joke. Even at dawn it can feel like running inside a wet towel.
I remember watching my heart rate creep up and thinking, “Why am I working harder at the same pace?”
Turns out I was.
There’s research showing dehydration exaggerates this drift. One cycling study found that dehydrated athletes experienced roughly a ~10% increase in heart rate over time, compared to about ~5% in well-hydrated athletes .
That lined up with what I saw.
If I skipped drinking? HR climbed faster.
If I sipped consistently? Drift still happened — but it was less dramatic.
Here’s the big lesson for the marathon:
Even if your pace stays steady, your body is working harder late in the race.
That’s why 5:41/km at km 5 feels smooth…
But 5:41/km at km 35 feels like a grind.
Your heart is compensating. Glycogen is lower. Core temp is higher. Everything is under cumulative stress.
Training helps.
Over months, plasma volume expands. You handle dehydration better. Your cooling system becomes more efficient. Drift becomes less extreme.
I also deliberately did some long runs in the heat. Not because I enjoy suffering. But because acclimation matters. By race day — which ended up warmer than ideal — I wasn’t shocked by the stress.
Cardiac drift stopped being scary.
It became something to manage.
- Hydration & Dehydration Realities
Hydration advice used to be extreme.
“Drink before you’re thirsty.”
“Never lose weight in a race.”
“Clear urine at all times.”
But modern research has softened that.
Moderate dehydration — around 2–3% body weight loss — generally does not significantly impair performance in endurance events .
So if a 70 kg runner finishes 2% lighter (around 68.6 kg), that’s normal.
That was a relief to me.
Because on long humid runs, I’d finish 1–2 kg lighter and think, “Did I just sabotage myself?”
Turns out… not necessarily.
Most marathoners finish slightly dehydrated. That’s typical.
The real danger isn’t mild dehydration.
It’s overhydration.
Some runners panic about the wall and start chugging water at every opportunity. If you dilute sodium too much, you risk hyponatremia — dangerously low sodium levels.
There are documented cases of runners actually gaining weight during a marathon because they drank excessively.
That’s not toughness. That’s risky.
I shifted my approach to:
Drink to thirst.
Sip consistently.
Don’t force it.
On long runs, I’d carry a bottle and sip when my mouth felt dry or when sweat was pouring. I didn’t try to replace every drop.
There’s also interesting data from ultramarathons showing that many top finishers end up around ~2.5% down in body weight, and that weight loss didn’t strongly correlate with slower finish times .
That reinforced the idea that being slightly “behind” on fluids is normal in long races.
I learned my own dehydration signals:
- Dry lips
- Elevated heart rate
- Mild headache after
- Slight irritability
If I felt that creeping in, I’d increase intake slightly.
Electrolytes mattered too.
I sweat heavily. My hat gets those white salt lines. So I used sports drink or electrolyte tablets, especially in heat. Plain water alone didn’t cut it for long sessions.
My typical long-run hydration looked like this:
- Start well hydrated (clear urine, but not bloated)
- Drink roughly 400–800 ml per hour in heat
- Less in cooler weather
- Accept finishing slightly lighter
Post-run, I’d drink to thirst and eat something salty.
On race day, I drank small amounts at most aid stations. A few sips every ~5 km. No guzzling. No panic chugging early.
Result?
No bathroom stops.
No bloating.
No severe dehydration.
Just steady management.
- Training Adaptations Over 8 Months
Here’s the cool part.
You don’t feel big changes week to week.
But over 8 months? You become a different athlete.
Early Phase (Months 1–2)
The first changes were cardiovascular.
My resting heart rate dropped.
Easy pace felt easier.
That’s stroke volume increasing. The heart pumping more blood per beat. Plasma volume expanding.
Endurance training literally enlarges the heart’s capacity in a healthy way.
At the same time, capillary density in muscles increases .
More tiny blood vessels = better oxygen delivery.
Think of it like adding extra lanes to a highway.
Middle Phase (Months 3–5)
This is when mitochondrial adaptations ramped up.
Mitochondria are the little power plants inside muscle cells. More mitochondria = better aerobic energy production .
With consistent long runs and tempo work, my muscles became better at oxidizing fat and sparing glycogen.
I didn’t feel this overnight.
But one day I’d notice:
“Hey… 15 km in and I still feel okay.”
Earlier in training, 15 km would have flattened me.
That’s adaptation happening quietly.
Lactate Threshold Shift
Early on, 5:15/km felt tough quickly.
By month five or six, I could hold 5:00/km for a 30-minute tempo and finish tired but controlled.
That’s threshold moving.
Objectively, my threshold pace likely improved from around ~5:15/km down closer to ~4:45–5:00/km.
And that meant my goal marathon pace (~5:41/km) sat more comfortably below threshold.
Exactly where you want it.
VO₂max & Economy
Interval sessions nudged VO₂max upward.
I didn’t lab test, but based on performance and heart rate response, I’d estimate maybe ~10% improvement over the full cycle.
More importantly, my running economy improved.
Month 1: 6:00/km felt like work.
Month 7: 6:00/km felt relaxed.
Same pace. Lower heart rate. Less effort.
Part of that was aerobic development.
Part of it was weight loss.
Part of it was simply repetition.
Movement became automatic.
Musculoskeletal Adaptation
Tendons, ligaments, bones — they adapt slower.
That’s why gradual mileage build matters.
Early on, a 16 km long run wrecked me. Knees stiff. Ankles sore. Everything cranky.
Later, 16 km was routine.
The distance didn’t shrink.
My body got tougher.
Training increases bone density slightly and strengthens connective tissue.
By race day, my legs felt armored compared to month one.
Not invincible.
But durable.
Neuromuscular Efficiency
This one’s subtle.
After months of repetition, my stride became automatic.
I could hold pace without micromanaging form.
Arms relaxed. Shoulders loose. Cadence consistent.
Less wasted motion.
Even as a mid-pack runner, that efficiency matters. Every bit of saved energy adds up over 42.2 km.
Looking back, the biggest lesson was this:
Adaptation is delayed.
The work you do today pays off 6–8 weeks later.
When a workout went poorly, I’d remind myself:
“This is building something in the background.”
Marathon training is patience disguised as running.
Eight months didn’t just make me fitter.
It made me durable.
And that’s what sub-4 really requires.
The 8-Month Training Plan (Phase by Phase)
Alright. Here’s how I actually structured it.
Not sexy. Not magical. Just months of showing up.
When I started, I could run maybe 30 minutes continuously without feeling like I needed to lie down afterward. Eight months later, I was standing on a marathon start line believing sub-4 was realistic.
Here’s how that happened.
Months 1–2 — Base Building & Habit Formation
The first two months were boring.
And that’s exactly why they worked.
I ran 3 to 4 times per week. Almost everything was easy. Like genuinely easy. No “sort of tempo.” No hero efforts. Just conversational pace.
Typical week looked like:
- 5 km easy
- 5 km easy
- 8 km easy
- 10–12 km long run
Weekly mileage started around 20 km and crept toward 30 km by the end of Month 2.
The long run increased slowly. About 1–2 km per week. And every third week, I backed off. For example:
10 km → 12 km → 8 km
14 km → 16 km → 12 km
Those down weeks probably saved me.
At this stage, pace meant nothing. Easy meant I could talk in full sentences. For me, that was around 6:30–7:00 per km. Way slower than marathon goal pace. And that’s fine.
You build endurance with time on your feet. Not ego.
I also added strength work twice a week. Nothing fancy. Squats. Lunges. Planks. Calf raises. About 20 minutes each session.
At 106 kg, I wasn’t pretending my joints didn’t need reinforcement. Heavier runners need durability. Period.
I also did light stretching or yoga once a week. Think prehab. The boring stuff that keeps you running.
Now, confession.
In Month 2, I got impatient. Jumped from a 12 km long run straight to 18 km. Because I felt “good.”
Around 15 km, my calf tightened like someone pulled a cable inside my leg. I limped home and ended up with a minor strain. Lost about 10 days.
That was 100% my fault.
Too much, too soon.
That little setback taught me something important: better slightly undertrained than injured.
By the end of Month 2, I could run about an hour without stopping. That felt huge. I wasn’t fast. But I was consistent.
And consistency is the real foundation.
Months 3–4 — Introducing Marathon-Specific Work
Now things got interesting.
Mileage hovered around 25–35 km per week. Still 4 days of running.
The big addition? Tempo runs.
Once a week, I’d do something like:
6 km total, with 3 km in the middle at “comfortably hard.”
Early on, that tempo was around 5:15–5:20 per km. Hard enough that I couldn’t chat. But not all-out.
These runs were uncomfortable. Not dramatic. Just steady discomfort.
After a few weeks, I extended tempo segments to 20–25 minutes continuous.
I dreaded them a little.
But finishing them? That felt powerful.
Meanwhile, the long run grew.
By the end of Month 4, I ran 18 km for the first time in my life.
I remember finishing that and thinking, “Okay… this is real now.”
Long runs stayed slow. I followed the guideline of about 60–90 seconds per mile slower than goal marathon pace.
So if goal pace was 5:41/km (~9:09/mile), long runs were around 6:15–6:30/km. Sometimes slower on hills.
This is where people mess up.
Running long runs too fast just beats you up. My job wasn’t to prove fitness. It was to build endurance and practice fueling.
I also added a midweek medium-long run of 10–12 km. That helped bridge the gap between short weekday runs and long weekends.
Near the end of Month 4, I did tune-up efforts.
A 10K race — under 50 minutes. A PR.
Then a self-supported half marathon time trial — about 1:52. Also a PR.
Those weren’t perfect races. But they gave me data.
Using the rule of thumb (2 × half + 15–25 minutes), 1:52 suggested I was hovering near sub-4 territory — if everything lined up.
That “if” mattered.
But I finally believed it was possible.
Months 5–6 — Heavy Training Phase (The Grind)
This was the meat.
Mileage climbed into 35–45 km per week. Occasionally close to 50 km on bigger weeks.
Mostly 4 days running. Sometimes a short 5th recovery jog if I felt good.
Three pillars defined this phase.
- Weekly Tempo Runs
Tempos became longer and more specific.
Examples:
- 2×4 km slightly faster than goal marathon pace (around 5:20/km)
- Continuous 6–8 km at threshold
- 8 km at marathon pace late in a 14 km run
That last one stands out.
Running 8 km at 5:35–5:40/km and feeling in control was a huge mental win.
Hard, yes. But manageable.
By this stage, I knew that “comfortably hard” zone well. I almost respected it. It felt like honest work.
- Interval Workouts (VO₂max Tune-Ups)
About every 10 days, I’d swap tempo for intervals.
5×1 km at 5K–10K pace.
Or 3×1600m at 10K pace.
These hurt.
Breathing heavy. Heart rate high. Legs burning.
But after surviving 5 × 1k repeats, marathon pace feels gentle by comparison.
Intervals made me feel athletic again. Marathon training can feel like endless grinding. Speed sessions reminded me I still had gears.
I always protected recovery around these sessions. Easy day before. Easy day after.
At 34 and 106 kg, I wasn’t playing games with injury risk.
- The Long Run Gets Real
Month 5: broke 20 km.
Month 6: mid-20s.
Then 28 km.
That 28 km run humbled me.
First 20 km? Smooth.
After 22? Fatigue crept in.
At 25 km? Legs heavy. Form sloppy.
I took an extra gel and dragged myself to 28 km.
Then walked.
On paper, it looked messy.
In reality, it was one of the most important runs of the cycle.
I learned:
- Gels every 50 minutes wasn’t enough for me
- I needed closer to every 40–45 minutes
- I probably started slightly too fast
- Fatigue management matters
That run taught me respect for the final 14 km of a marathon.
They are not a formality.
This phase changed my lifestyle.
Friday nights became carb dinners and early sleep.
Saturday mornings were 3-hour runs.
Foam rolling became routine. Light cycling or swims on rest days. Sleep was prioritized.
I cleaned up my diet. Ate more protein. More vegetables. Less junk.
I rewarded myself too. Brunch after long runs. New socks. Small things to keep morale up.
It was grindy.
I was often tired. Often hungry.
But something shifted.
Workouts that scared me in Month 3 were just… part of life by Month 6.
That’s progression.
You don’t suddenly feel like a marathoner.
One day you just realize:
You’ve been living like one for months.
Months 7–8 — Peak, Taper, and Race Prep
Month 7 was the peak. This was where everything topped out.
My biggest week was around 55 km (34 miles). Nothing crazy compared to elites. But for me? That was real volume. I felt it.
And then came the 30 km long run.
That was the dress rehearsal.
I ran it at the same time of day as the race. Woke up early. Ate the same breakfast I planned for race morning. Wore the exact shoes, socks, shorts, even the shirt I planned to race in. You learn real fast how fabric feels after 3 hours. Chafing is not theoretical.
The first 20–22 km were smooth. Controlled. Familiar territory.
The last 5 km? Slow shuffle. Heavy legs. Mind bargaining.
But I didn’t hit a dramatic wall.
When my watch beeped 30.0 km, I stopped it and just stood there. Sweaty. Tired. Kind of wrecked. But something shifted.
Before that run, part of me still wondered, “Can I even finish 42.2?”
After that run, it became, “Okay. I will finish. Now how well can I execute?”
That’s a different mindset.
During peak weeks, I added some marathon-pace work into long runs.
One workout I’ll never forget: 24 km total, last 6 km at goal pace (~5:40–5:45/km).
Running that pace on tired legs was hard. Not heroic. Just controlled discomfort.
But hitting those splits late in a long run gave me confidence. It taught me what marathon pace actually feels like at the back end of fatigue.
Another workout was 3 × 5 km slightly slower than marathon pace inside a 26 km run.
That one humbled me.
I nailed the first two segments. The third drifted slower. Legs fading. Focus slipping.
But that was good. It showed me where the edge was.
Not everyone believes in marathon-pace segments in long runs. Some coaches avoid it. But as a first-timer, I needed that exposure. I needed to know the feeling.
Then came the taper.
Three weeks out, I cut mileage to about 75% of peak.
Two weeks out, around 50%.
Final week, maybe 30%.
Still ran 4 days per week. Just shorter and easier.
The first few days of taper? I felt worse.
Heavy. Sluggish. Doubting everything.
That’s normal. Your body is repairing.
Then about 7–10 days before race day, I felt something different.
A little pop in the legs.
Easy runs felt almost too easy. Like I had been dragging around a backpack for months and someone finally took it off.
That’s when you start trusting the process.
Two weeks out, I did a controlled 21 km run. Not a race. More like a dress rehearsal.
I ran it about 15 sec/km slower than marathon pace and included 10 km continuous at goal pace in the middle.
It wasn’t all-out. It was controlled.
After that, no more big efforts.
My last “workout” was 10 days out: 3 × 1 km at marathon pace with long recoveries. Just enough to feel rhythm.
It was over almost instantly. And I was left hungry to race.
Final week? Three short jogs. 5 km. 6 km. 3 km shakeout the day before.
That’s it.
The rest was mental.
I slightly reduced caffeine so race-day coffee would hit harder. Ate more carbs — about 70% of intake in the final 3 days. Rice. Pasta. Bread. Bananas. Nothing exotic.
I didn’t massively increase calories. I just shifted macros. More carbs. Slightly less fat.
By race morning, I felt slightly bloated.
That’s fuel.
Taper madness is real, by the way.
I became obsessed with the weather forecast. Checking it multiple times a day. Hoping for clouds. Bargaining with the sky.
I laid out my race kit days early. Triple-checked laces. Trimmed toenails like I was performing surgery.
I even got a haircut two days before the race thinking maybe less hair = cooler head.
Did it help? Probably not. But it made me feel in control.
All that nervous energy just means you care.
By the final 48 hours, worry turned into quiet confidence.
The hay was in the barn.
Nothing left to gain. Only to execute.
Coach’s Notebook — Patterns in Sub-4 First-Timers
After going through this myself — and coaching others — I’ve seen patterns.
Sub-4 doesn’t happen by accident. But it also doesn’t require genius.
It requires avoiding predictable mistakes.
Here’s what I’ve seen.
Mistake #1: Marathon Pace Too Early, Too Often
This one is common.
People want to prove they can run 9:09/mile in training. So they turn long runs into time trials. Or they stack marathon pace miles every week from Month 2.
Marathon pace is tricky. It’s not sprinting. But it’s not easy either.
For beginners, it becomes this gray zone. Too hard to recover from easily. Too easy to build top-end speed.
A coach once told me:
“Make your hard days hard. Make your easy days easy.”
Marathon pace can live in the middle. That’s dangerous if overused.
I kept most long runs easy early on. Only introduced marathon-pace segments late.
I had a friend who ran goal pace in nearly every long run from the start.
By week 8, he was exhausted. By week 12, injured. He had to taper early. Missed sub-4.
Lesson: build general fitness first. Specific pace later.
Mistake #2: All or Nothing Training
Some runners run everything too slow.
Others run everything too fast.
Both are wrong.
If you only jog slowly, you don’t develop the ability to sustain faster paces.
If you hammer every run, you never recover.
In previous cycles, I was the “everything hard” guy. I thought suffering equaled progress.
This time, I truly kept easy runs easy.
And guess what? My tempo and interval days improved because I had energy.
The balance matters.
Hard days hard. Easy days easy.
Sub-4 runners often say the same thing: they learned to slow down on easy days.
Mistake #3: Skipping Tempo Work
Long slow distance builds base.
Track intervals build speed.
But the marathon lives near lactate threshold.
If you never train near that zone, marathon pace feels foreign.
I’ve seen runners with big mileage but no tempo work struggle to hold pace in the back half.
Tempo runs were huge for me.
They weren’t glamorous. But they raised my ceiling.
Mistake #4: Ignoring Strength & Mobility
When time gets tight, strength work gets cut first.
Bad move.
Over months, little weaknesses become injuries.
I’ve dealt with IT band pain before when I ignored glute work.
This cycle, I stayed consistent with basic strength.
Nothing fancy. Just consistent.
The difference showed up in Month 5 and 6 when mileage peaked and I wasn’t falling apart.
Marathon training is stacking bricks. If one brick is weak — tight hamstrings, weak hips — the whole wall tilts.
Mistake #5: Improper Fueling
You cannot wing nutrition.
I’ve heard runners say they don’t fuel in training to “toughen up.”
That’s not toughness. That’s poor preparation.
Others never test race gels and find out at mile 20 that their stomach hates them.
I practiced gel timing until it was automatic. Every 45 minutes. Water every ~15.
On race day, fueling started early. Not when I felt low.
Sub-4 runners typically have a fueling plan.
Those who blow up often don’t.
Mistake #6: Poor Recovery Hygiene
Training is stress.
Adaptation happens during recovery.
Not sleeping enough. Not hydrating. Ignoring pain. Cramming extra workouts.
I once tried to squeeze in intervals during a high-mileage week when I was already tired.
Ended with a knee tweak. Lost more time than if I had just rested.
The runners who succeed listen to early warning signs.
They back off when needed.
They prioritize sleep.
Sleep might be the cheapest performance enhancer there is.
When I started going to bed 30–60 minutes earlier consistently, I felt it immediately.
A rested body adapts.
A tired one breaks.
Sub-4 isn’t about heroic workouts.
It’s about avoiding predictable mistakes for eight straight months.
That’s not sexy.
But it works.
Successful Patterns (What Works)
After going through it myself — and watching other regular runners chase the same sub-4 goal — some patterns just kept showing up.
Not flashy stuff. Not “secret workouts.” Just habits.
Here’s what actually worked.
- Consistency and Gradual Progress
This is boring. And it’s everything.
The runners who break 4:00 usually aren’t the ones who post insane 70 km weeks and then disappear for 10 days.
They’re the ones who show up.
Week after week.
I made a decision early on: I’d rather run 40 km per week for 10 straight weeks than bounce between 60 km one week and 0 km the next because I’m wrecked or injured.
That steady accumulation matters.
You don’t feel it day to day. But stack 30+ weeks together and suddenly you’ve got 700–800 km in your legs. I did the math near the end of the cycle and realized that’s roughly what I’d built up.
None of those kilometers were magical.
But together? They changed me.
I loosely followed the 10% idea. Increase a little. Hold. Let the body catch up. Increase again.
No dramatic leaps. No ego jumps.
And by race day, I didn’t feel like I had one monster workout in the bank.
I felt like I had months of quiet work behind me.
That’s different.
- Embracing Easy Runs
I know I keep repeating this. But it’s because it matters that much.
The people who break 4:00 usually do a surprising amount of slow running.
Like… genuinely slow.
For me, goal pace was around 5:40/km.
Easy pace was often 6:30–7:00/km.
Sometimes slower in Bali heat.
Early on, my ego hated that.
I’d think, “If I can run 5:40 in a race, why am I jogging at 6:45?”
But I started noticing something.
When I kept easy runs truly easy:
- My heart rate stayed low
- My legs recovered
- I didn’t dread going out the next day
- I could actually attack tempo workouts
Easy runs became almost meditative.
No watch obsession. No pressure. Just time on feet.
And mentally, that kept me sane. I didn’t burn out.
The runners who try to “win” their easy runs often arrive at race day tired.
The ones who protect their easy days show up fresh.
I wanted to arrive at the start line hungry — not exhausted.
- Regular Threshold / Tempo Work
I rarely hear of someone breaking 4:00 who never did tempo work.
Lots of slow miles alone usually isn’t enough.
The marathon sits just under lactate threshold. If you never train near that zone, race pace feels foreign.
Tempo runs were uncomfortable. Not dramatic. Just steady discomfort.
20–40 minutes at that “comfortably hard” effort.
I’d finish them tired but controlled.
And over months, I could feel marathon pace becoming less threatening.
I saw this pattern over and over in forums too.
“Tempo runs made marathon pace feel sustainable.”
That line kept popping up.
It’s not sexy training. But it works.
- Practiced Fueling & Hydration
The successful first-timers treat long runs like rehearsals.
Not just distance rehearsal — fueling rehearsal.
By race day, I knew:
- Breakfast: ~300 kcal carb-heavy meal 2 hours before
- One caffeine gel 15 min pre-start
- One gel every 45 minutes
- Small sips of water regularly
- Alternate water and sports drink at aid stations
None of that was guesswork. It came from messing it up in training.
I had long runs where I took gels too far apart and felt that slow fade.
I had days where I didn’t eat enough the night before and felt flat.
Those lessons hurt in training — but they didn’t ruin race day.
The runners who hit sub-4 usually say something like:
“Fueling went smoothly.”
The ones who miss often say:
“I tried something new…” or
“I forgot to take my gel until I felt low…”
That’s usually too late.
Nothing new on race day. Ever.
- Listening to the Body (Flexibility)
Plans are helpful.
Blind obedience is not.
The runners who break 4:00 tend to adjust intelligently.
I had to.
When I tweaked my knee, I replaced a run with swimming. Skipped an interval session. Backed off mileage.
It stressed me out. I felt like I was losing fitness.
I wasn’t.
I was protecting it.
A friend training for the same race sprained his ankle playing soccer. He switched to cycling for a week instead of stubbornly limping through runs.
He ran 3:58.
Training smart beats training stubborn.
There’s a difference between pushing through discomfort and pushing into injury.
Sub-4 runners usually learn that difference.
- Mental Preparation and Realistic Pacing
The physical plan matters.
But the mental plan matters just as much.
I visualized race day constantly.
Not the finish photo.
The middle.
The grind.
The moment at 32 km when everything feels heavier.
I practiced patience in training. I deliberately started some long runs slower than I wanted.
Because I knew race adrenaline would try to hijack me.
My pacing plan was simple:
- First 5K slightly slower than goal pace
- Settle into rhythm until 32K
- Reassess and give what’s left
I told myself repeatedly: the marathon rewards restraint.
In race reports from runners who break 4:00, I often see:
“Started conservative.”
“Felt strong at 30K.”
“Was able to push in the final 5K.”
In reports from those who miss it?
“Felt amazing at 10K.”
“Hit the wall hard.”
“Second half was a struggle.”
Big positive splits are common in failed sub-4 attempts.
The successful ones often run even splits or slight negative splits.
That’s not accidental.
That’s discipline.
The Big Picture
Sub-4 doesn’t usually come from one heroic week.
It comes from months of controlled, consistent training.
There’s a saying I love:
“The marathon isn’t won in a day. But it can be lost in a day.”
One reckless long run.
One injury from ego.
One blown pacing strategy.
Those can undo months of work.
The successful patterns aren’t dramatic.
They’re steady.
Show up.
Run easy when it’s easy.
Work hard when it’s time.
Fuel properly.
Sleep.
Adjust when needed.
Respect the distance.
That’s not glamorous.
But it’s how regular people break 4 hours.
Community Voices — What Real Runners Say About Sub-4
I don’t think I would’ve survived those eight months without the internet.
Seriously.
Reddit threads at midnight. Random Strava race reports. Forum posts from people I’ll never meet. I’d read them like bedtime stories. Some calmed me down. Some scared me. Some lit a fire under me.
Here are the themes that kept popping up.
- “Is a 1:54 Half Good Enough?”
I saw this question everywhere.
And honestly… I asked it myself in different forms.
The common answer from experienced runners was always something like:
“Possible. But tight.”
A lot of coaches and seasoned runners pointed out that sub-4 tends to go more smoothly if you’re closer to a 1:50 half (or faster) .
Not a strict rule. But a cushion.
Because a marathon is not just two halves glued together. It’s exponentially harder if endurance or fueling slips even slightly.
When someone posted:
“I run a 52-minute 10K and a 1:54 half. Can I go sub-4?”
The replies were usually:
“You’re right on the edge. Get a little faster, or race it perfectly.”
That word — perfectly — stuck with me.
It meant no pacing mistakes. No fueling errors. No heat meltdown.
That’s when I decided I didn’t just want to scrape by with a 1:54 fitness level. I wanted my half fitness in the high 1:40s to give myself breathing room.
That gave me confidence.
- Advice for Heavier Runners (Like Me)
At 106 kg, I was not floating down the road.
I found threads from other “Clydesdale” runners — guys and women over 200 lbs chasing marathon goals.
The tone was always the same:
Patience.
Heavier runners deal with higher impact forces. Slower paces. More stress per stride.
And that’s okay.
A lot of them said:
“Don’t obsess over speed early. Build the distance first. Speed will follow.”
That resonated.
There were also warnings about crash dieting.
Several people said they tried slashing calories while marathon training and ended up exhausted, injured, or constantly sick.
That scared me straight.
Instead of trying to drop 10–15 kg aggressively, I fueled training properly. Over 8 months, I lost about 6–7 kg naturally.
No crazy dieting. Just consistent running and better food choices.
Heavier runners also emphasized:
- Cushioned shoes (I bought a maximal pair for long runs)
- Strength training
- Extra attention to recovery
Hearing from 200+ lb runners who broke sub-4 — or simply finished strong — was huge for me.
They weren’t unicorns.
They were disciplined.
- 4 Days vs 5 Days vs 6 Days
Another hot topic.
“Is 4 days per week enough?”
The consensus I saw: yes. If structured well.
Plenty of people hit sub-4 on 4-day plans.
Some added a 5th easy day to gently boost mileage. But the advice was clear: don’t add volume if your body isn’t handling it.
One runner wrote:
“I ran 3 days and cycled twice. 3:58.”
That stuck with me.
Because I’m not built for 6 days a week year-round. And I didn’t want to pretend I was.
I mostly ran 4 days. Occasionally 5 if I felt great.
The pattern I noticed? The successful runners were consistent — not necessarily high-frequency.
That reassured me on weeks when life limited me to 4 runs.
- Nutrition & Carb-Loading Confusion
Oh man. The carb debates.
“Do I need to carb load before every long run?”
Short answer from the community: no.
Eat enough carbs to fuel the work. But don’t treat every 20 km run like Boston.
I’d have a solid carb-heavy dinner before long runs. Rice, potatoes, maybe a dessert if I burned a lot of calories.
But I wasn’t doing 3-day carb loads every weekend.
Save that for race week.
There were also threads about “fat adaptation.”
Some people experimented with low-carb or fasted long runs to improve fat burning.
I tried a couple shorter low-fuel morning runs.
Honestly? I didn’t love it.
I felt flat. Risk of bonking felt higher. For me, the tradeoff didn’t seem worth it.
The general community message that made sense to me was:
Don’t overcomplicate it.
Eat quality food.
Fuel your workouts.
Practice race nutrition in training.
That’s what I did.
- Celebrating Milestones
This was my favorite part of the online world.
Someone would post:
“Just ran 32 km for the first time. Didn’t walk!”
And the comments would explode with encouragement.
When I did my first 30 km, I posted about it. The replies felt like a virtual high-five from strangers.
Hitting 20 miles (32 km) in training is almost a rite of passage.
It changes your belief system.
Another common milestone post:
“New half PR during marathon training!”
Those little wins keep momentum alive.
And then there are the finish-line posts.
“I did it. 3:59:30.”
I remember one runner describing how they ugly-cried at the finish.
That image stayed in my head during hard workouts.
Not the time itself.
The release.
The months behind it.
- The Debates (Because Runners Love Debates)
You can’t hang around running forums without seeing disagreements.
Long Run Pace
Some say:
“All long runs slow.”
Others:
“Include marathon pace segments.”
I landed in the middle.
Mostly slow long runs. But a few marathon-pace finishes late in the cycle.
That seemed to align with a lot of experienced voices.
5 Runs vs 4
Same debate as before.
More isn’t always better.
Quality > quantity.
GPS vs Feel
Another interesting one.
Some runners said:
“Trust your watch.”
Others warned:
“GPS lies in cities and tunnels.”
I saw advice like:
“Learn what marathon effort feels like.”
So I practiced that.
Occasionally I’d cover my watch and run by feel. Then check afterward.
On race day, my watch glitched in a tunnel.
Because I had practiced by effort, I didn’t panic.
Walk Breaks vs Continuous Running
Some runners swear by structured walk breaks, even for sub-4.
Others say continuous running is necessary.
From what I saw, most sub-4 race reports didn’t rely on planned walk breaks — but a few did it successfully with tight discipline.
I aimed to run continuously.
But I gave myself permission to take quick controlled resets at aid stations if needed.
The key theme from the community wasn’t “never walk.”
It was “don’t mentally check out.”
Reading all of this made training feel less lonely.
You realize you’re not the only one worrying about half times, carb intake, or whether 4 days is enough.
There’s this quiet army of everyday runners chasing the same clock.
We train mostly alone.
But we don’t train alone.
That helped more than I expected.
Skeptic’s Corner — When Sub-4 Might Not Be the First Target
Let me be honest.
Sub-4 is not automatic.
And it’s not mandatory.
Not everyone hits it on their first marathon. That doesn’t mean the cycle was wasted. It doesn’t mean you failed. It just means the marathon did what the marathon does — it exposed the gap between current fitness and ambition.
When I started this, I was 106 kg. I had maybe a year or two of casual running behind me. Eight months to go from that to sub-4?
Aggressive.
I knew that.
I told myself early on: if tune-up races stall… if injuries pile up… if the data says no… I’ll pivot.
Maybe 4:15. Maybe just finish strong.
That wasn’t weakness. That was reality.
When Sub-4 Might Be a Stretch
There are variables we don’t control:
- Starting fitness
- Body weight
- Age
- Genetics
- Time available to train
- Injury history
I saw plenty of first-timers in their 40s and 50s say, “You know what? I just want to finish strong.”
And that’s smart.
If your half marathon time is 2:05 or 2:10, aiming for sub-4 (essentially two sub-2 halves back-to-back) is a huge jump. Not impossible. But it’s a steep climb in one cycle.
Sometimes targeting 4:20 or 4:10 first is wiser.
I read stories of runners who went 4:30 in their first marathon. Then a year later? 3:58.
Foundation first. Speed second.
That long-term thinking matters.
Injury Changes the Conversation
If you lose 4–6 weeks to injury, the goal needs to shift.
I read about a woman on track for sub-4 who developed plantar fasciitis two months out. She cut back dramatically. Race day became about finishing healthy.
She ran 4:20. Was proud.
Next marathon? 3:55.
That stuck with me.
Flexibility isn’t weakness.
It’s maturity.
Pacing Reality Check
Let’s talk pacing honestly.
In theory: even splits or slight negative split is ideal.
In reality? Many first-timers slow down in the second half even with good pacing.
It’s just… uncharted territory for the body.
My plan was even splits.
What happened? I went through halfway around 1:59:30 and finished just under 4 hours.
Slight positive split.
Totally fine.
What you want to avoid is the catastrophic split.
Not 2–3 minutes slower in the second half.
More like 10–20 minutes slower with a long stretch of walking.
That’s the wheels coming off.
Some coaches suggest aiming for a slightly conservative first half — like 1:58 for a 4:00 goal.
Banking time is risky.
If you run 1:55 in the first half thinking you’re clever… you may pay for it brutally.
I leaned conservative.
And I’m glad I did.
The “Ego Workout” Incident
Let me tell you where ego almost derailed everything.
About 7 weeks out, I had a strong week. Longest midweek run nailed. Tempo felt smooth. I felt invincible.
Instead of sticking to the plan, I decided to “level up.”
I inserted 6 × 1 km faster than 10K pace inside a 15 km run. Completely unnecessary.
By rep 4, I felt a sharp pain on the outside of my knee.
IT band.
I stopped. Limped home. Angry at myself.
Two weeks of reduced training.
That was pure ego.
The marathon rewards smart training. Not reckless training.
There’s a phrase I love:
“Don’t try to win training.”
Your medal is on race day.
If I had kept pushing through that pain, I might have lost the race entirely.
That moment changed me.
From then on, if something felt off, I backed off.
Sub-4 doesn’t reward heroics in workouts.
It rewards restraint.
Caffeine — The Little Edge
Let’s talk about the legal cheat code.
Caffeine.
It’s one of the few performance aids that actually works. It can reduce perceived effort, improve alertness, and slightly enhance endurance.
We’re not talking miracles.
Maybe a few percent.
But sometimes a few percent is the difference between 4:02 and 3:59.
My routine:
- Coffee ~2.5 hours pre-race
- Two caffeinated gels (25–30 mg each) saved for the second half
I tested this in training.
One long run, I took a caffeine gel at the 2-hour mark. Within 10–15 minutes, my mood lifted. Pace felt easier.
Placebo? Maybe partly.
But perception matters in a marathon.
Caffeine won’t fix bad pacing.
It won’t fix under-fueling.
It’s a small discount coupon. You still have to pay the full marathon bill.
If you’ve done everything right, it helps.
If you haven’t, it won’t save you.
And of course — test it first. Some people get stomach issues or jitters.
Nothing new on race day.
Final Thought from the Skeptic’s Corner
Be ambitious.
But be honest.
Sub-4 is a great goal. But it’s not the only measure of a successful first marathon.
If it happens — amazing.
If it doesn’t — you’re still someone who ran 42.2 km. That’s not small.
Sometimes the smartest runners are the ones who adjust.
Finish healthy. Finish proud.
Then decide what you want next.
The marathon isn’t going anywhere.
And neither is your potential.
FAQ
Q: Should I run 4 or 5 times a week to break 4 hours?
For most first-timers chasing sub-4, four days is enough. That’s what I did. Nothing fancy. Three weekday runs — usually two easy, one a bit longer or tempo — and then the long run on the weekend.
That structure gave me breathing room. Recovery days matter more than people think.
Could you add a 5th run? Sure. A short, very easy jog. Shake the legs out. I did that occasionally when I felt good. But I didn’t force it.
Here’s the thing: that extra run might give you a tiny endurance bump. It also raises fatigue. And injury risk creeps up quietly.
If you’re working a job, juggling family, sleeping 6–7 hours some nights… four runs done well beats five done half-recovered.
Start with four. Earn the fifth.
And remember — slightly undertrained beats slightly injured every single time.