How to run the Norwegian Method without a lactate meter

Why the meter matters (and why it doesn't)

Blood-lactate testing answers one question: at what pace does your body's production of lactate equal your body's clearance of it? That crossover is what coaches mean by “lactate threshold.” Run under it and you can continue almost indefinitely. Run over it and the clock is ticking — your blood lactate is climbing, fatigue accumulating, performance decaying.

The Norwegian Method trains almost exclusively around this one number. The Golden Zone (2.3–3.0 mmol/L) sits right at the crossover: high enough to drive the adaptations of threshold training, low enough that you can repeat the stimulus two or three times a week. If your threshold pace is wrong, your sessions miss the zone — you either don't get the adaptation, or you accumulate fatigue faster than you can recover.

So yes, the meter matters. And a lab test from a qualified sports lab — taken once every 6–12 months — is the gold standard. But the methodology doesn't need a lab to work. It needs a threshold-pace estimate that is close enough that the session lands within the right physiological band. In the rest of this post I'll walk through the three ways to get that estimate without a meter, how accurate each one is, and how they stack.

Method 1: Race results + VDOT tables (~2–4 seconds per kilometer)

The most reliable proxy for lactate threshold is race performance. If you've raced a 5K, 10K, half, or marathon in the last 6–10 weeks, Jack Daniels' VDOT tables give you a threshold pace that is, for most runners, within 2–4 seconds per kilometer of a lab-measured value.

The logic: race performance at distances from 5K to marathon is dominated by the same physiological variable that determines threshold pace — maximal lactate steady state. A runner who races 5K in 20:00 has a predictable threshold pace (around 4:25/km). Race at 18:00 and it's around 3:55/km. These relationships are stable across runners, validated across decades of data.

How to use it:plug your most recent race result into any VDOT calculator (there are a dozen free ones online, including one inside Threshold). The threshold pace it outputs is your starting point. It will be slightly off — maybe the runner is “high VDOT” at short distances but fades in the marathon, or vice versa. But “slightly off” here means 2–4 seconds per kilometer in either direction, which is inside the width of the Golden Zone.

What if you haven't raced? A time trial works the same way. 5 kilometers flat out, honest effort, timed. Threshold takes this input during onboarding and produces the same estimate.

What race results don't tell you

They don't account for training state. If you're coming back from injury and your 5 K PR was set two years ago, VDOT will over-estimate your current threshold. Conversely, if you've been running consistently for six months without racing, you're probably faster than your last result suggests. This is where the second and third methods kick in.

Method 2: Heart-rate drift during steady effort (~3–5 bpm)

A lactate-threshold pace, held steady, produces a predictable heart-rate pattern: a rapid rise for the first 5 minutes, then a stable plateau, then a slow drift upward over the next 20 minutes as cardiac drift accumulates. The inflection point between “rising” and “stable” is what coaches call the aerobic / anaerobic threshold.

The test:20 minutes continuous at the pace you think is threshold — hard but controlled, conversational only in short bursts. If your heart rate is stable between minutes 10 and 20, you're at or just below threshold. If it's climbing steadily, you're over. Adjust by 5–10 seconds per kilometer in the correcting direction and retest in 2 weeks.

This method is accurate to roughly ±3–5 bpm in heart rate, which translates to roughly ±5 seconds per kilometer in pace — slightly less precise than the race-result method but useful as a cross-check. It's particularly good for runners who race rarely.

Important:heart-rate drift is confounded by dehydration, heat, poor sleep, caffeine, and lingering fatigue from yesterday's session. Run the test on a rested, hydrated, moderate-temperature day or discard the result.

Method 3: Session-level perceived effort (~5–8 seconds per kilometer)

Every time you complete a threshold session, you generate data. Did you finish feeling controlled, like you could have run one more rep? Or did the last rep drop off pace noticeably? Was your heart rate in the expected range for your estimated threshold? Did the session feel disproportionately hard?

Taken individually, none of these signals is precise. Taken over 4–6 sessions and combined with a Bayesian update, they meaningfully refine the initial VDOT estimate.

The rule of thumb used in Threshold:

• RPE consistently 6–7 across a threshold session, heart rate at expected level, final rep on pace → threshold estimate is correct. Do nothing.
• RPE consistently 8+, last rep 5+ seconds off pace, heart rate climbing beyond expected → threshold pace is too fast. Slow the next session's target pace by 3–5 seconds per kilometer.
• RPE consistently 5 or below, heart rate below expected, felt comfortable → threshold pace is too slow. Speed up the next session's target pace by 3–5 seconds per kilometer.

This is imprecise but self-correcting. After 4–6 sessions the estimate converges on a pace that actually matches your physiology, regardless of whether your VDOT number was off at the start.

How the three methods stack

None of these methods replaces a lab test. Stacked together, they approximate one:

1. Start with VDOT from your most recent race or time trial. Set initial threshold pace.
2. Run a 20-minute steady-state test in the first week. Check heart-rate drift. Adjust if needed.
3. Log RPE + heart rate after every threshold session for the first 4–6 weeks. Let the pace self-correct.

By the end of the first 4-week block, your threshold pace estimate will typically be within 2–3 seconds per kilometer of what a lab would measure. Inside the width of the Golden Zone. Good enough that the methodology works as designed.

What Threshold does automatically

Every Threshold plan runs this stack under the hood:

• Onboarding asks for your recent race results (or a time trial) and computes the initial VDOT-based threshold pace.
• Apple Health syncs heart-rate data from your watch. Threshold reads it to validate the estimate.
• After each threshold session you're asked for a quick RPE rating (optional but recommended). That rating feeds a Bayesian update that sharpens the pace estimate.
• Every 4 weeks, the plan is redesigned around the updated threshold pace. New paces propagate to every session in the next block.

You don't see the Bayesian math. You see your paces get slightly better-fitted to your physiology, block by block, until they stop moving. That's convergence.

When you should actually get a lactate test

Three scenarios where paying for a lab test pays back:

• You've stopped improving despite consistent training for 6+ months. Something may be systematically off in your estimate.
• You're training for a high-stakes A-race (Boston qualifier, sub-3 marathon, etc.) and want to remove uncertainty in the final 8 weeks.
• You have unusual physiology (low or high lactate response, known muscle-fiber-type asymmetry, asthma, anemia). These cases deviate more from VDOT predictions.

Expect to pay $150–350 for a single-session test at a sports lab. Useful once or twice a year at most.

The bottom line

The Norwegian Method is portable. It works without a meter, without a Norwegian coach in the room, and without a track club. What it requires is honest pacing, controlled intensity, and a willingness to let the estimate self-correct over the first few weeks. Every runner doing Norwegian Singles on Reddit is training this way — and many of them are producing PRs that the “aggressive progression” running apps couldn't.

If you want the stack set up for you, Threshold handles it. If you want to do it yourself, the three methods above are the playbook.