What Your Strava Splits Reveal About Your Hydration

You finished your long run, uploaded to Strava, and scrolled through the splits. The first half looked strong. Then something happened around kilometre 14 — your pace faded, your legs felt heavy, and the last few kilometres were a grind.

You blamed fitness. You blamed the heat. You blamed that hill at mile 9.

But what if the real problem was hiding in your Strava data all along — and it was hydration?

The pattern most runners miss

Open your last three long runs on Strava and look at the split table. Not just the pace column — look at the trend.

If your splits tell a story that goes something like "steady, steady, steady… then gradually slower, then significantly slower," you're seeing what exercise physiologists call cardiac drift. And in most recreational runners doing long runs in warm conditions, the primary driver is dehydration.

Here's what happens physiologically. As you lose fluid through sweat, your blood volume decreases. Your heart has to pump faster to deliver the same amount of oxygen to your muscles. Your perceived effort rises even though your pace stays the same — until it doesn't, and your pace starts dropping too.

The Strava split table shows you the output. The heart rate graph shows you the cause.

How to read your Strava data for hydration signals

You don't need a lab. You need three things you already have: your Strava split times, your heart rate data (from your Apple Watch or Garmin), and about five minutes.

Step 1: Compare your first-half and second-half pace.

Pull up a long run — anything over 90 minutes. Calculate your average pace for the first half and the second half. A difference of more than 15–20 seconds per kilometre (or about 20–30 seconds per mile) that you didn't intend is worth investigating.

Step 2: Overlay the heart rate trend.

On Strava, tap into the heart rate analysis for the same run. Look at the trajectory. In a well-fueled, well-hydrated run, heart rate should rise gradually and then plateau as you settle into your effort. If it keeps climbing — especially in the second half while your pace is dropping or holding steady — that's cardiac drift.

A heart rate that rises more than 10–15 beats per minute over a constant-effort run is a strong signal that your body is compensating for reduced blood volume.

Step 3: Check the conditions.

Strava records temperature and weather conditions for your activity (pulled from local weather data). If that long run happened on a day above 25°C (77°F) with moderate humidity, the probability that your fade was dehydration-related goes up significantly.

Warm conditions can increase your sweat rate by 30–50% compared to cool weather. If you were drinking the same amount you drink on a 15°C morning run, you were almost certainly under-hydrating.

What the numbers actually mean

Let's put some real numbers on this.

Most endurance athletes lose between 0.5 and 1.5 litres of sweat per hour, depending on body size, intensity, heat, and humidity. Some athletes in hot conditions can exceed 2.5 litres per hour.

Every litre of sweat you lose without replacing reduces your blood plasma volume. Research shows that once you lose more than 2% of your body weight in fluid, your cardiovascular system starts working harder to maintain output. For a 70 kg runner, that's just 1.4 kg — roughly 1.4 litres.

On a two-hour long run at a moderate sweat rate of 1 litre per hour, you'd lose 2 litres total. If you drank 500 ml across the run, you'd finish with a 1.5-litre deficit — over 2% of your body weight. And your Strava splits would show it.

The frustrating part: most runners look at that fade and think "I need to run more long runs" or "I need to slow down my first half." Sometimes that's true. But often the cheapest, most immediate improvement is simply drinking more — and drinking the right things.

Why "drink when you're thirsty" fails on long runs

You've probably heard the advice: just drink to thirst. And for runs under an hour, that works fine. Your body's thirst mechanism is reasonably well calibrated for short efforts.

But during extended exercise — anything over 60–90 minutes — thirst lags behind actual fluid loss. By the time you feel thirsty, you may already be 1–2% dehydrated. In hot conditions, that lag gets worse because your body prioritises sending blood to the skin for cooling, which further reduces the volume available for your muscles.

This is why the American College of Sports Medicine recommends a planned hydration strategy for events over an hour: 400–800 ml per hour, adjusted for body weight, intensity, and conditions.

The key word there is "adjusted." And that's where generic advice falls short.

The personalisation problem

Here's the thing Strava can't tell you: how much you personally should be drinking.

Your split data shows you that something went wrong. It can even help you estimate when the wheels started coming off. But it can't tell you whether your sweat rate is 0.8 litres per hour or 1.6 litres per hour. It can't tell you how much sodium you're losing. And it can't tell you whether you need 500 ml per hour or 900 ml per hour to stay in the performance zone.

Two runners can do the same long run, at the same pace, on the same route, on the same day — and need completely different hydration plans. One might sweat heavily and lose a lot of sodium. The other might be a light sweater who needs far less. Their Strava data looks identical on the surface, but the intervention is completely different.

This is the gap between knowing you have a problem and knowing what to do about it.

How to turn Strava data into a hydration experiment

If your Strava splits are showing a consistent fade pattern, here's a simple protocol to test whether hydration is the cause.

Week 1 — Baseline. Do your normal long run with your normal hydration. Note your splits, heart rate drift, and how you felt.

Week 2 — Increase volume. Same route, same target pace. Increase your fluid intake by 200–300 ml per hour. Use an electrolyte drink rather than plain water. Note splits and heart rate drift.

Week 3 — Compare. If your second-half fade reduced and your heart rate drift was smaller, hydration was likely a significant factor. If nothing changed, the fade might be fitness, pacing, or fueling related.

This is useful but slow. You're spending three weeks on one variable, and you're still guessing at the right amount.

From data to decisions

Strava is excellent at showing you what happened. It records your route, your pace, your heart rate, your elevation, and your conditions. What it wasn't built to do is tell you what to change.

That's the gap Sweatr was designed to fill.

Sweatr connects to your Strava activity data and your wearable metrics from Apple Watch or Garmin. It uses your training history, your body data, and environmental conditions to calculate your personal sweat rate and build a hydration plan tailored to you — not to a generic range from a research paper.

Instead of spending three weekends running hydration experiments, Sweatr analyses your existing data and tells you: drink this much, at this interval, with this sodium concentration. And when conditions change — a hotter day, a faster pace, a longer run — the plan adjusts automatically.

Your Strava splits told you something was wrong. Sweatr tells you exactly what to do about it.

What to do this weekend

Before your next long run, pull up your last three on Strava. Look at the split pattern. Check the heart rate trajectory. Note the conditions.

If you see the fade — steady first half, gradually slower second half, heart rate climbing throughout — you've probably been running dehydrated without realising it. And the fix might be simpler than you think.

Start with more fluid, add electrolytes, and pay attention to whether the pattern changes. Or let Sweatr do the maths for you and take a personalised plan into your next session.

Your Strava data has been telling you something for months. It's time to listen.