Sweat Rate Calculator: Two Numbers on a Bathroom Scale Will Tell You More Than Any Hydration App

Why this Sweat Rate Calculator and Two Numbers on a Bathroom Scale Will Tell You More Than Any Hydration App will. Most triathletes hydrate by feel, or by whatever a bottle-per-hour rule of thumb they picked up years ago. Feel is a bad instrument for this. Thirst lags actual fluid deficit, and by the time it shows up, the workout is already compromised. The fix isn't a smarter app or a fancier bottle — it's two weigh-ins and a little arithmetic.

The Math Behind It

Sweat rate testing runs on one physiological shortcut: a kilogram of body weight lost during exercise is, for practical purposes, a liter of fluid lost. Everything else in the formula just accounts for what moved in and out around that number.

Sweat loss = (pre-workout weight − post-workout weight) + fluid consumed − urine output

Divide that total by the workout's duration in hours, and the result is sweat rate — the number that should actually be driving a fluid strategy, instead of a generic "16 oz per hour" heuristic that has nothing to do with the specific athlete, sport, or conditions.

Here's the arithmetic laid out so it's checkable, not asserted. An athlete weighs 165.0 lb before a 90-minute ride and 163.2 lb after, having drunk 24 oz of fluid and not urinated mid-ride.

• Weight lost: 165.0 − 163.2 = 1.8 lb → 1.8 × 0.45359237 = 0.8165 kg

• Fluid consumed: 24 oz × 0.0295735 = 0.7098 L

• Urine output: 0 L

• Total sweat loss: 0.8165 + 0.7098 − 0 = 1.5263 L

• Duration: 90 minutes = 1.5 hours

• Sweat rate: 1.5263 ÷ 1.5 = 1.02 L/hr

  
  

That's a real number, tied to that specific athlete, on that specific bike ride, in those specific conditions — not a number borrowed from a magazine article about someone else's physiology.

Why Bike and Run Need Separate Tests

Sweat rate isn't a fixed personal constant. It's driven by heat production, airflow, and how long the cardiovascular system has already been under load — three things that look completely different between the bike and the run leg of a triathlon.

Airflow at cycling speed provides real evaporative cooling that simply isn't there on the run. Add in whatever cardiovascular drift has already accumulated by the time an athlete starts running off the bike, and a single blended sweat number stops meaning much for either discipline. Testing bike and run separately, and treating brick sessions as a pacing rehearsal rather than a sweat-rate data point, is what keeps the resulting fluid targets usable on race day.

The Ceiling Nobody Talks About

Heavy sweaters — anyone testing above roughly 1.2 L/hr — run into a second problem that a spreadsheet formula won't solve on its own: the human gut can only absorb about 27–34 oz (0.8–1.0 L) of fluid per hour, regardless of how much is going out. Past that point, drinking more doesn't close the gap — it just sits in the stomach.

The realistic strategy for a heavy sweater isn't full replacement. It's drinking at the gut's ceiling, starting the session already well hydrated, front-loading sodium, and accepting a managed deficit that stays under the 2% body-weight threshold where performance actually starts to slip.

What the Scale Can't Tell You

Sweat loss during a single session is only half the picture. Two athletes can post an identical in-session number and still be dealing with completely different problems — one started the workout well hydrated, the other started already depleted. A pre-workout urine color check (the simple pale-to-dark scale most athletes have seen at a doctor's office) catches that distinction. Dark urine walking into a session that otherwise looks fine on paper points at a day-to-day hydration habit to fix, not an in-workout fluid strategy. That's a different problem with a different solution, and it's the one variable on the scale-based math that can't answer it.

Salt residue left on skin or kit after a sweaty session is a second useful, low-tech signal — a rough field proxy for sweat sodium concentration. Heavy crusting suggests a "salty sweater" profile worth taking seriously, particularly for anyone logging long training days or Half/Full Distance racing where the exposure window to a sodium deficit stretches out for hours.

Post-Workout Rehydration Isn't 1:1

Replacing exactly what was lost after a workout still leaves a net deficit, because urine output continues as the body rehydrates and reabsorbs fluid. Established rehydration research points to replacing roughly 125–150% of whatever deficit remains post-workout, over the following four to six hours, with sodium included — not just plain water. Skipping this step is a common reason athletes show up to back-to-back training days or stage-style events already running behind.

Turning One Test Into a Race-Day Number

A sweat rate measured over a 60–90 minute session is a reasonable starting estimate for race day, but it isn't guaranteed to hold flat across a multi-hour Half or Full Distance bike or run leg. Conditions shift across the day, pacing changes, and cardiovascular drift compounds over time in ways a short test can't fully capture. The wider the gap between test duration and expected race-day duration, the more that projection should be treated as a first estimate to validate with at least one longer training session — not a locked-in number.

Test It

The Sweat Rate Calculator runs this entire process — discipline-specific testing, the gut-absorption ceiling, urine color context, salt crust signal, post-workout rehydration target, and race-day projection — off two weigh-ins and a few optional details. It takes less time than the workout that generated the data.

Fluid is only one side of the equation on race day. Sweat carries sodium out with it, and a fluid plan built without a matching fueling strategy tends to fall apart in the back half of a long race — the Fueling Calculator covers that other half.

FAQ

How often should I retest my sweat rate? Once per season, per discipline, per weather condition is the baseline. Heat, humidity, altitude, and fitness level all shift sweat rate, so a number from a cool spring training block won't hold in July.

Is drinking more always the safer choice? No. Finishing a workout heavier than it started means more fluid went in than sweated out. Chronic overdrinking dilutes blood sodium — hyponatremia — which carries more risk in long-course racing than mild dehydration does. More isn't automatically safer; matched-to-losses is the target.

Do I need lab testing to know my sweat sodium concentration? Not necessarily. Visible salt crusting after a session is a reasonable field proxy. For athletes who show heavy crusting consistently, especially those training for Half or Full Distance events, a professional sweat-sodium test provides more precise numbers than the field proxy can.

What if my test session was much shorter than my race? The calculator flags that gap directly and adjusts its confidence accordingly. A 60-minute test extrapolated out to a 9-hour Full Distance bike leg is a starting point, not a guarantee — validate it with a longer training session before race day.

Structured hydration data belongs inside a structured training plan, not a standalone spreadsheet. Every Andiamo²® plan builds heat tolerance and race-day hydration work directly into the schedule, alongside email coach support and a free run gait video analysis — find the plan built around your race.

Not ready to commit to a full plan yet? Grab the Splash Class below — drop in your email and get a free twelve-week swim and strength plan, a low-stakes way to see how Andiamo²® coaching actually fits into a real training week before spending anything.

If your sweat rate is coming back above 3.5 L/hr, your test session ran under 30 minutes, or you're finishing sessions heavier than you started, the math gets noisy enough that a second set of eyes helps — send a coach your numbers and get a straight read on what they mean.

Thanks for reading.

Follow on FaceBook!