Every cyclist has stared at a local hill and thought some version of:
“Could I… just keep doing this until Everest happens?”

That thought is how Everesting is born.
One hill.
One activity. Repeat until you’ve climbed 8,848 meters.
No shortcuts.
No segments stitched together.
Just you, gravity, and increasingly questionable life choices.

Everesting is simple in theory and brutal in practice.
And planning it turns out to be way more annoying than it should be.

So I built this Everesting Climb Finder.

The Problem

Before you destroy your legs and soul, you need answers:

• How much elevation does this climb actually give you?
• How many repeats are we talking about — 20 or 200?
• What’s the total distance once descents are counted?
• Is the gradient “hard but doable” or “I will regret this on lap 7”?

Strava has the raw ingredients, but it doesn’t answer the Everesting question.
It gives you numbers.
You still have to do the mental gymnastics (which, after a few rides, is already a scarce resource).

The Fix: Everesting Climb Finder

I wanted a tool that takes a climb and immediately answers the only question that matters:

“Is this hill a terrible idea… or a manageable terrible idea?”

The Everesting Climb Finder connects to Strava, pulls real segment data, and does the math for you. No spreadsheets. No guesswork. No lying to yourself.

Pick a climb. Get the truth.

Under the Hood (aka: Tech, but Only the Useful Parts)

This is a modern web app, built to be fast, boring in the good ways, and pleasant to use on a phone — because that’s where we all stare at stats after rides.

• React + Vite – fast dev loop, zero patience wasted.
• Tailwind CSS – clean, dark UI that doesn’t burn your eyes at 5am.
• Leaflet / React-Leaflet – interactive maps that don’t feel like 2009. Openstreetmap are great.
• Recharts – elevation profiles, because numbers alone lie.
• Vitest – because math bugs at 3am are not character-building.

No overengineering.
No frameworks for the sake of frameworks.

The Important Bits

Strava Integration

OAuth (=this ‘dance’ we must act on), clean and simple.
The app pulls real Strava segment data, which means the elevation gain is what your legs will actually experience — not optimistic estimates.

The Everesting Math

At the core is a small but ruthless calculator. It doesn’t care about your dreams.

It answers:

• How many repeats to hit 8,848m? There is a calculator just for that.
• Total distance including descents (this adds up fast).
• Rough time estimates based on climb and descent speeds.

The logic is intentionally simple and transparent:

export function calculateRepeats(elevationGain, targetElevation = 8848) {
  if (elevationGain <= 0) return Infinity
  return Math.ceil(targetElevation / elevationGain)
}

export function calculateTotalDistance(segmentDistance, repeats) {
  return (segmentDistance * 2 * repeats) / 1000
}

No dark magic — Just basic arithmetic and consequences.

Interactive Discovery

Search a location.
Click a segment. Instantly see its Everesting Card:

• Repeats required
• Total distance
• Gradient
• Elevation profile

This is where fantasy meets reality.

Elevation Profiles That Actually Matter 📈

A climb that looks “fine” on average can hide a nasty kick at the top. That kick becomes legendary on repeat 40.

Seeing the profile early saves future you from learning this the hard way.

Structure That Won’t Collapse Later

The codebase is boring in the best sense:

src/
├── components/
├── context/
├── hooks/
├── pages/
└── services/

Easy to extend. Easy to delete things later when they turn out to be dumb ideas. Both are important.

What’s Next (After Recovery)

There’s plenty of room to grow:

• Weather and wind direction (because headwinds are personal)
• Leaderboards per climb
• 3D terrain views for extra intimidation

But even in its current form, this tool already answers the hardest Everesting question honestly.

Not “Can I do it?”
But “Do I really want to? Yes! So where…”

Built with ☕, code, and far too many hours on bikes.