ROUTE CONTEXT
How to read your splits after a hilly run
A slow kilometer can be the one where the road climbs. Read the route beside the split table before judging how evenly you ran.
Keep the route in the picture
A split table describes time over distance. It does not explain terrain. Add the route direction and elevation profile to your review so each split has a physical location. A loop run clockwise is not necessarily comparable with the same loop run counterclockwise: the climbs and descents arrive in a different order.
Separate a measurement from an explanation. “Kilometer three took 40 seconds longer” is a measurement. “The climb explains every second” is a hypothesis that also depends on surface, stops, conditions and how the runner approached that section.
An out-and-back example
Imagine a two-kilometer outing with one kilometer uphill and one kilometer back down. This is a reading example, not a suggested training session.
| Section | Time | Net elevation change |
|---|---|---|
| Outward kilometer | 6:00 | +60 m |
| Return kilometer | 5:00 | −60 m |
| Total | 11:00 | 0 m net |
The total averages 5:30 per kilometer. Net elevation change is zero, yet the route was not flat. Likewise, an overall average cannot show how the effort was distributed. Keep total ascent distinct from the difference between the starting and finishing elevation.
Compare like-for-like sections
For a repeat visit, match the outward kilometer with the outward kilometer. Compare recorded duration and any reliable heart-rate data, then inspect the trace for pauses or route deviations. If the next activity turns back 100 meters earlier, use the genuinely shared section rather than comparing its whole first lap.
A grade-adjusted estimate is a model, not a new observed finish time. Unless a specific algorithm and its inputs are available, avoid applying a universal seconds-per-meter correction. The raw split and elevation remain useful even when no adjustment is shown.
Write a route-aware conclusion
In Runome, read the available route, splits and activity charts together. A practical note might say: “The climb was similar; the return was quicker, with one fewer stop.” That is more informative for the next comparison than calling the whole run stronger because the average improved.
For steady-effort comparisons, choose sections that answer that narrower question. The guide to selecting steady segments explains the selection problem, while pace consistency shows what an equal-distance split pattern can reveal.