At RIBBAN, we don't just build fast websites – we're building fast runners too. We've set an audacious goal: completing the Copenhagen Marathon 2026 in under 3 hours. This isn't just about crossing a finish line; it's about pushing boundaries, both in code and on the pavement.

Why the Copenhagen Marathon?

Copenhagen holds a special place in Scandinavian running culture. The flat, fast course winds through the Danish capital's historic streets, past architectural marvels, with crowds that rival Stockholm's energy. Plus, the May weather is perfect for chasing PRs. But most importantly, it represents a challenge that mirrors our approach to web development: ambitious, measurable, and rewarding.

The Sub-3 Hour Challenge

Breaking the 3-hour barrier means maintaining a pace of 4:15 per kilometer for 42.195 kilometers. It's a goal that only 2% of marathon runners ever achieve. For context, that's:

Running 21.1 km in 1:29:30 (twice!)
Maintaining a speed of 14.1 km/h for nearly 3 hours
Burning approximately 2,600 calories
Taking roughly 30,000 steps

Our Training Philosophy

Just as we approach web development with systematic planning and iterative improvement, our marathon training follows proven methodologies:

The 80/20 Rule

80% easy runs (conversational pace)
20% high-intensity work (intervals, tempo runs)
Recovery is when adaptation happens

Progressive Overload

Weekly mileage increases of no more than 10%
Scheduled deload weeks every fourth week
Listen to the body, not just the Garmin

Tech Stack for Training

Being a tech company, we're naturally leveraging technology to optimize our training:

const trainingStack = {
  devices: ['Garmin Forerunner 965', 'Polar H10 Heart Rate Monitor'],
  apps: ['Strava', 'TrainingPeaks', 'Whoop'],
  nutrition: ['Maurten gels', 'Tailwind Endurance Fuel'],
  recovery: ['Theragun', 'Normatec boots', 'Hyperice X'],
  analytics: ['HRV tracking', 'Running power metrics', 'VO2max estimation']
};

Current Training Status

As of February 2025, we're in the base-building phase:

Team Stats

Andreas: Current PR 3:24, averaging 55km/week
Marcus: Current PR 3:31, averaging 50km/week
Emma: Current PR 3:42, averaging 45km/week

Weekly Structure

Monday: Recovery run (8-10km easy)
Tuesday: Track intervals (8x1000m @ 3:55 pace)
Wednesday: Easy run (10-12km)
Thursday: Tempo run (10km @ 4:10 pace)
Friday: Rest or yoga
Saturday: Long run (25-35km @ 4:40 pace)
Sunday: Recovery run or cross-training

The Data-Driven Approach

We're tracking everything, creating our own training dashboard:

Key Metrics We Monitor

Running Economy: Measuring efficiency at race pace
Lactate Threshold: The pace we can sustain without accumulating lactate
Weekly Load: Balancing stress and recovery using Training Stress Score (TSS)
Sleep Quality: Aiming for 8+ hours, tracking with Whoop
HRV Trends: Morning measurements guide training intensity

Nutrition and Fueling Strategy

Sub-3 requires perfect fueling:

Daily Nutrition

Carbohydrates: 5-7g per kg body weight
Protein: 1.6-2.2g per kg for recovery
Hydration: 35-40ml per kg + training losses

Race Day Plan

Breakfast: Oatmeal + banana 3 hours before
Pre-race: 500ml electrolyte drink
During: 60-90g carbs/hour via gels
Pacing: Even splits with 10-second buffer per km

The Mind Game

Physical preparation is only half the battle. Mental strategies we're developing:

Visualization: Weekly sessions imagining race scenarios
Mantras: Personal power phrases for tough moments
Segmentation: Breaking 42km into manageable chunks
Process Focus: Concentrating on form, not the finish line

Building Team Spirit

This journey is bringing our team closer:

Tuesday Track Sessions: Suffering together builds bonds
Saturday Long Runs: 2+ hours of conversation and connection
Monthly Time Trials: Friendly competition pushing everyone
Recovery Brunches: Celebrating the work with good food

Lessons for Business

Marathon training is teaching us valuable business lessons:

Consistency Beats Intensity

Just like sustainable growth, consistent training trumps sporadic heroic efforts.

Process Over Outcomes

Focus on daily execution, and results follow naturally.

Recovery is Productive

In running and coding, rest prevents burnout and enables peak performance.

Data Drives Decisions

Metrics guide training just as analytics guide our development choices.

What's Next?

With 15 months until race day, we're building systematically:

Q1 2025: Base Building

Establish consistent 50-60km weeks
Strengthen supporting muscles
Dial in nutrition strategies

Q2 2025: Speed Development

Introduce structured speedwork
First half-marathon race simulation
Refine fueling protocols

Q3 2025: Marathon Specific

Peak weekly mileage (80-90km)
Long runs with race-pace segments
Full dress rehearsal races

Q4 2025: Taper and Peak

Strategic volume reduction
Maintain intensity, reduce volume
Mental preparation intensifies

Q1 2026: Final Preparation

Last build cycle
Copenhagen Marathon: May 11, 2026

Join Our Journey

Follow our progress on Strava where we're documenting every kilometer. We'll be sharing training tips, nutrition experiments, and the inevitable ups and downs of marathon preparation.

Who knows? Maybe we'll see you at the start line in Copenhagen. After all, if we can optimize database queries and shave milliseconds off load times, surely we can find those extra seconds per kilometer on the road.

Beyond the Finish Line

This marathon represents more than a time goal. It's about proving that the same dedication we bring to client projects can transform our personal lives. It's about showing that a team that codes together can also conquer physical challenges together.

Whether we break 3 hours or not, we're already winning by taking on this challenge. And just like in our development work, we'll iterate, improve, and come back stronger if we fall short.

Want to follow our journey or need a tech team that goes the extra mile (literally)? Reach out to us – we'd love to hear about your own ambitious goals, whether they're measured in kilometers or kilobytes.

RIBBAN Runs Copenhagen: Our Journey to Sub-3 Hours in 2026