Olympia T-Shirt
Strava Electrolyte Fueling for Long Runs: 2026 Workflow
Most runners fuel long runs by guessing: a salt tab every 45 minutes because a running forum said so, or a sports drink because it's what's in the cooler at the aid station. That's not a plan, it's a habit. Pull your pace, duration, and average temperature straight from Strava, run the numbers through a basic sweat-rate calculation, and you build a fueling schedule that matches the run you're actually doing instead of a generic chart pinned to a gym wall.
- Strava electrolyte fueling long runs starts with your Moving Time and Average Temp fields, not a flat 500mg-per-hour rule.
- Sweat rate runs 0.5 to 2.5 liters per hour depending on pace and heat, per published exercise physiology data.
- Sodium loss tracks at 500 to 2,000 mg per liter of sweat lost, so your dosing should scale with your Strava splits.
- Cwench Hydration Electrolyte Mix and NOCCO Electrolyte RTD cover two different delivery formats for runs over 90 minutes.
Why this matters
A generic "one electrolyte tab every 45 minutes" plan ignores the two variables that actually drive sodium loss: how hard you're working and how hot it is. Strava already logs both. Your Moving Time, distance splits, elevation gain, and (if your device reports it) average temperature sit in every activity you've recorded in 2026.
The problem isn't a lack of data. It's that nobody connects the Strava numbers to a fueling decision. Runners either overdose on sodium and get GI distress at mile 10, or underdose and cramp at mile 16. Both are fixable with a five-minute calculation before the run, not during it.
Before you start
- A Strava account with at least 3-4 logged long runs (90+ minutes) so you have pace and duration data to work from, not a single outlier run.
- A bathroom scale for pre-run and post-run body weight, which is the best proxy for sweat loss you have without a lab.
- The gotcha: Strava's temperature field pulls from the nearest weather station, not your actual heat load. On a shaded trail run at 68°F, you can still sweat like it's 80°F if humidity is high or you're pushing pace. Treat Strava's temp reading as a starting point, not gospel — cross-check it against how soaked your shirt actually was.
Pull your long run data from Strava
- Open the Strava app or web dashboard and go to your Training Log.
- Filter for runs tagged Long Run or sort by Moving Time over 90 minutes.
- For each qualifying run, record three fields: Moving Time, Distance, and Average Temp (visible in the activity's weather overlay if your device or phone GPS captured it).
- Note your Average Pace per mile from the same activity screen — effort level correlates with sweat rate more than distance alone does.
Expected result: a short list of 3-5 long runs with time, distance, pace, and temperature side by side. That's your raw data set for the next step.
Calculate your sweat rate and sodium loss
- Weigh yourself naked, before the run and again immediately after, before drinking anything post-run.
- Subtract post-run weight from pre-run weight. Each pound lost equals roughly 16 ounces (about 0.47 liters) of sweat.
- Divide that fluid loss by your Strava Moving Time in hours to get liters lost per hour — your sweat rate.
- Cross-reference your sweat rate against the published range: most runners lose 0.5 to 2.5 liters per hour, with the high end reserved for hot, humid conditions or faster paces.
- Multiply your hourly sweat rate by a sodium concentration of 500 to 2,000 mg per liter (published sweat-sodium ranges from exercise physiology literature) to estimate hourly sodium loss.
Expected result: a personal sodium-loss number in mg per hour, not a borrowed number from a supplement label. If your Strava data shows an 80-minute run at a 78°F average temp and you lost 1.5 lbs, you're near 1 liter of sweat per hour — meaning 500-2,000 mg of sodium to replace, depending on how salty a sweater you are.
Build your electrolyte fueling schedule
- Take your hourly sodium-loss estimate and divide it into 15-20 minute intervals matching your typical fueling stops.
- Match that per-interval number against product labels: a best electrolyte supplement for workouts breakdown helps you compare sodium content per serving without guessing from marketing copy.
- Set a repeating phone timer matching your interval so the plan runs itself mid-race instead of relying on memory at mile 12.
- Log the plan you actually followed in your Strava activity description after the run, so next long run you're refining a real data point instead of starting from zero.
Expected result: a fueling schedule tied to a number you calculated, not a number printed on a label for a runner with a different sweat rate than yours.
Load your run with the right products
Most long-run fueling comes down to two categories: an electrolyte source you sip steadily, and a carb source you eat on a schedule. Machine Fuel from Tiger Fitness covers the carb side of that split. For solid food between electrolyte sips, an Outright Peanut Butter Bar travels in a running vest without refrigeration.
Cwench Hydration Electrolyte Mix fits runners prepping bottles for a full training block; NOCCO Electrolyte RTD fits runners who want a grab-and-go can with zero prep.
Powder vs ready-to-drink
| Format | Best for | Upside | Downside |
|---|---|---|---|
| Electrolyte powder mix | Runners dialing in a custom per-bottle dose | You control concentration per bottle | Requires mixing and a clean shaker before every run |
| Ready-to-drink can | Runners who fuel pre- and post-run at home or in the car | Zero prep, consistent serving | Heavier to carry mid-run than powder in a flask |
Adjust the workflow for hot-weather long runs
When Strava's average temp reads above 75°F, the whole schedule shifts. Sweat rate climbs toward the top of the 0.5-2.5 liter per hour range, and sodium loss climbs with it.
- Re-run the sweat-rate calculation using only your hot-weather runs from Strava, not your full 2026 training log average.
- Shorten your fueling interval from 20 minutes to 15 minutes on days the temp field reads above 75°F.
- Take a pre-run electrolyte serving 20-30 minutes before starting rather than waiting for the first mid-run interval.
Expected result: a heat-adjusted schedule that doesn't leave you playing catch-up once you're already behind on sodium at mile 8.
Troubleshooting
- Cramping despite following the schedule: your pre-run body weight measurement may be off. Re-weigh at the same time of day, same clothing (none), for three consecutive long runs before trusting the number.
- GI upset mid-run: you're likely front-loading too much in one interval. Spread the same total across more, smaller intervals instead of cutting total intake.
- Strava's Average Temp doesn't match how hot you felt: that's the gotcha from earlier. Nearest-station data lags real conditions on shaded trails and in urban heat islands. Trust your post-run weight loss over the temp field when the two disagree.
- You forgot to weigh in before drinking post-run: set a phone reminder tied to the end of the activity so weighing happens before the first sip of water.
- Numbers swing wildly run to run: average across at least 3-4 long runs. One outlier (illness, unusually hot day, heavy pre-run meal) skews a single data point hard.
Customize your workflow
Once the Strava-to-sodium workflow is running, expand it. Cross-check your product against an electrolyte supplements ranked by sodium content comparison to see how your current pick stacks up. If you're building a full training-cycle plan rather than a single-run schedule, a supplement stack for endurance runners covers what to layer in around electrolytes across a 2026 block.
“Three weigh-ins averaged beats one weigh-in trusted — a single long run will lie to you about your sweat rate.”
FAQ
What's the best way to use Strava for electrolyte fueling on long runs?
Pull Moving Time, Average Temp, and pace from your logged long runs, then calculate sweat rate from pre and post-run body weight. That personal number, not a generic chart, drives your sodium dosing schedule for 2026 training.
Is Strava's temperature data accurate enough for fueling decisions?
It's directional, not exact. Strava pulls from the nearest weather station, so shaded routes and high-humidity days can run hotter than the recorded temp suggests. Cross-check against your actual sweat loss.
How much sodium do I need per hour on a long run?
Sodium loss ranges 500 to 2,000 mg per liter of sweat, and sweat rate itself ranges 0.5 to 2.5 liters per hour depending on pace and heat. Calculate your own sweat rate first, then apply that sodium range to your number.
Should I use a powder mix or a ready-to-drink electrolyte for long runs?
A mix like Cwench Hydration Electrolyte Mix suits runners prepping bottles ahead of a training block. A ready-to-drink option like NOCCO Electrolyte RTD suits runners who want zero prep before heading out the door.
How often should I recalculate my sweat rate?
Recalculate every few weeks, or whenever conditions shift meaningfully. A new season, a new race location, or a jump in weekly mileage all change sweat rate enough to matter.
Can I use this same workflow for marathon race day?
Yes, with one adjustment: build the schedule from your hottest, longest training runs rather than your average conditions. Race-day pace usually pushes sweat rate toward the higher end of your personal range.
What if my Strava data shows inconsistent sweat rates between runs?
Average across at least three to four long runs before trusting a single figure. One unusually hot day or an off day with illness will skew a single-run calculation badly.
Do I need a GPS watch, or does phone GPS work for this?
Phone GPS logged through Strava captures Moving Time, distance, and pace, which is all the workflow requires. A dedicated watch adds finer temperature and heart rate data but isn't necessary.
One last thing
The step most runners skip is the boring one: weighing naked, same time of day, for three straight long runs before trusting any sweat-rate number. A single measurement swings enough with clothing, hydration timing, and meal timing that it isn't worth building a plan on. Three data points averaged gets you a number you can train around for the rest of 2026.


Leave a comment