Direct answer
Why do COROS Running Fitness and Base Fitness move differently?
Do not read COROS Base Fitness as a performance result. It summarizes training load; Running Fitness estimates running ability from eligible runs. The two can move differently without a contradiction. Check which score changed, whether recent runs qualified and whether a test recalibrated your zones. Inspect the runs before deciding a flat or lower score means you should train harder.
If your COROS scores seem to disagree, check which question each one answers. Base Fitness tracks accumulated load. Running Fitness estimates running ability. A busy week or a fitness test can move them differently.
Base Fitness measures load, not a race result
COROS describes Base Fitness as a weighted 42-day rolling average of Training Load. Training Load uses duration and intensity from heart-rate-recorded activities. Load Impact covers seven days, while Intensity Trend relates shorter-term load to longer-term load. These are load-history views, not interchangeable scores of running performance.
Running Fitness is a separate running-specific estimate. Current COROS support describes it through changes in the pace-HR relationship in outdoor runs, with Endurance, Threshold, Speed and Sprint components. The vendor says a qualifying run can change a component after one session. That simplified explanation is not a complete algorithm or a diagnosis of why a score changed.
Why Base Fitness can rise while Running Fitness stays flat
Imagine you have a busy week of cycling and running. Base Fitness can reflect the extra work while Running Fitness still needs eligible running evidence. Check the qualifying runs before treating an unchanged estimate as a problem.
For first availability, current support describes a continuous outdoor Run or Track Run of at least 25 minutes meeting its documented heart-rate-reserve threshold. The threshold is resting HR plus 65% of HR reserve, not 65% of maximum HR. Ongoing eligibility describes at least one qualifying 25-minute run in 90 days. Interruptions or inconsistent recordings can interfere.
These are requirements for a vendor calculation, not instructions to add hard work. Consult the current official requirements for your device when reviewing an activity already completed. A missing update does not prove that the session had no training value.
More work, unchanged estimate
Here's a sample week. You record two runs and several long bike rides, so your recorded training load is higher than last week. Only one run has complete, continuous eligible data, and Running Fitness stays unchanged. A familiar workout feels comfortable, but you have no recent comparable race.
You did more work, and the running estimate stayed flat. Both can be true. The sample does not tell you whether cycling helped or why COROS valued an easy run differently. Read the load change and running result separately.
When a fitness test changes the scale
COROS's September 2026 test guidance says a completed Running Fitness Test can update threshold pace, threshold HR, maximum HR, zones, Running Fitness and race estimates. It also documents a possible Base Fitness discontinuity after zone recalibration. Later activities may receive different Training Load values under the changed zones.
If the number jumps after a test, check your settings before deciding your fitness changed. Keep these details together so you can see what the recalibration actually affected:
- Test date and which results were actually returned:
- Old and new threshold pace, HR and zone boundaries:
- Base Fitness and Running Fitness dates:
- Pauses, recording uncertainties and conditions:
- Later raw duration, pace and HR observations:
You might record a run with similar duration and heart rate after the zones change, yet see a different modeled load. COROS documents that possibility. It does not guarantee a particular change or say every older activity was recalculated.
An incomplete test is different from a lower result. Use COROS's current instructions or support to check unmet requirements and inconsistent data. You do not need to repeat a challenging test or change settings just to restore a preferred number.
Keep the original run measurements
Keep the original distance, duration, timing basis and available HR observations. Note the date of a change in measuring rules before comparing a long chart. For a familiar task, record route, effort and conditions separately from the modeled score.
COROS recommends understanding your personal seasonal pattern rather than targeting somebody else's Base Fitness number. No numerical band here guarantees safe training or diagnoses overtraining. A load estimate should not be turned into an instruction without the wider context of your plan and circumstances.
Where does Yigri fit in?
Yigri compares runs with your personal baseline and summarizes the week. Start with COROS Training Hub, then look at a Yigri example if you want another explanation beside your runs. Check which activity fields transfer before expecting the COROS scores to appear in another app. The guides below cover hills, heart rate and taper weeks. hills guide same-pace HR guide taper guide examples
Methodology and limits
Written by Yigri. Sources reviewed on 6 October 2026. Workout examples use sample numbers; links to the source material follow.
- Available metrics and eligible activities vary by device, software and account settings.
- A score change does not tell you its cause or whether you should train harder.
