The Runome journal

How to compare two runs on the same route

A useful comparison starts with a question and a fair baseline. Here is how to read two runs together without letting one number decide the answer.

Moving time versus elapsed time: which pace are you comparing?

Before comparing two pace numbers, check the clocks behind them. Removing a pause changes the calculation even when the route stays the same.

How to review an interval workout beyond average pace

A session average mixes several different jobs. Separate the repetitions from the easy running before deciding what happened.

Why is my VO₂max dropping when I am running faster?

Your finish time is an observation. A watch or app VO₂max value is an estimate. When they move in different directions, review the evidence behind each before changing your training.

Average running pace: why adding your split paces can be wrong

Two correct split paces can produce an incorrect average. The missing question is how much distance each number represents.

Running progress in percentages: what does 10% better mean?

A percentage needs a starting value and a named measure. Without both, a promising improvement can be surprisingly hard to interpret.

Is your running pace becoming more consistent?

A faster average is one kind of progress. A more controlled pace is another. Equal-distance splits help you see the difference.

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.

What a spike in your running pace graph can mean

A dramatic point on a chart is a reason to investigate. Start by checking how much time and distance it represents.

How to review your first month of recorded runs

Your first review should make the history easier to use. Check completeness, establish a baseline and choose one question for the next month.

Manual run entries: what can and cannot be analyzed?

A manually entered distance and time can preserve a useful training record. They cannot recreate a route, a split pattern or a measured heart-rate trace.

Choose a fair baseline for comparing easy runs

The most useful comparison is the one that matches your question. Choose the baseline before looking for the biggest improvement.

Why whole-run averages can disagree with segment efficiency

A ratio calculated from two averages is not generally the same as the average of two ratios.

Choosing comparable halves for a decoupling calculation

The calculation is short. Choosing the two intervals deserves more attention.

A negative decoupling result: what to check first

A negative number means the speed-to-heart-rate ratio increased under this convention. It is a starting point for reviewing the run.

Calculate running heart-rate cost: a worked example

Heart-rate cost expresses recorded heart rate relative to running speed. The calculation is simple; choosing comparable inputs is the important part.

Aerobic efficiency in meters per heartbeat

Meters per heartbeat gives a physical unit to one running-efficiency ratio. Keep that unit attached to the number when comparing results.

Choose steady segments for a running-efficiency comparison

A whole-run average blends everything in the outing. Select a segment that matches the question, and keep the selection rule consistent.

Heart-rate drift versus aerobic decoupling

Heart rate can rise while speed stays steady, or speed can fall while heart rate stays steady. Drift and decoupling describe different parts of that relationship.

Why warm-up minutes can change a drift calculation

Changing the analysis window changes the question. A lower drift result after removing early minutes is not a change in the recorded run.

A better efficiency score or better sensor coverage?

An efficiency value can change because the recording changed. Compare the amount and location of measured data before comparing the score.

One great run or a real trend? How to read changes over time

Training happens across weeks. A useful trend keeps individual runs visible and makes its comparison window clear.

An eight-week running log with a zero-distance week

Zero is a real value. A missing record is an unresolved question.

Put a planned long run inside a complete weekly total

The same long-run distance can account for a very different share of the week.

Taper arithmetic: compare the same days

A lower total can represent a planned reduction—or simply a week that is not finished.

A running streak and a weekly total tell different stories

A streak counts consecutive days. A weekly total counts accumulated running. Neither replaces the other.

Calendar-week versus rolling-week running totals

Two correct totals can disagree because their date windows differ. Read the start and end dates before looking for a missing run.

How missing workouts affect your training-load history

A model only sees the activities available to it. Before explaining a changed training trend, check whether the history changed.

More distance or more intensity: what changed in your week?

Weekly distance is useful, but it does not describe every demand in the week. Keep the total and the session structure side by side.

Why a modeled fitness score can fall during a rest week

A training model changes as recent inputs age. Its label should not be confused with a direct fitness test.

Runome Marathon Shape: an eight-week volume example

Marathon preparation has a history. Read sustained weekly distance and the longest outing together before focusing on a target pace.

Your longest run and weekly distance: read them together

A single long outing and a sustained weekly total describe different features of a history. Looking at both exposes what either one leaves out.

Why rounded race splits can miss your finish time

A few fractions of a second per split can become a visible difference at the finish.

Running distance in 400-metre laps

Count the complete laps first, then keep the remaining distance visible.

Convert running pace to speed and treadmill settings

A pace value tells you time per distance. A treadmill usually asks for distance per hour. Convert the units before choosing a setting.

Calculate a 5K pace target and check your splits

Turn a 5K finish target into a pace and a set of cumulative times. The arithmetic describes the target; it does not establish that the target fits your preparation.

A 50-minute 10K: pace, checkpoints and early-split arithmetic

A ten-kilometer target gives each early split a measurable relationship to the remaining distance. Calculate that relationship before interpreting the overall average.

Sub-two-hour half marathon: exact pace and useful checkpoints

A half marathon includes a partial final kilometer. Keep the full distance in the calculation, especially when your target sits close to a time boundary.

Sub-four-hour marathon: pace, splits and the final kilometers

Forty kilometers is not the finish. Use the complete 42.195 km distance and keep the final section on any marathon pace sheet.

How sensitive is a race prediction to its input?

A precise-looking prediction can be sensitive to a small change in the input. Check what the model knows before giving the final seconds too much weight.

Why is my heart rate higher at the same running pace?

The same pace does not always mean the same effort. A higher reading can reflect conditions, recent training or the recording itself; one run cannot tell you which.

Why GPS pace jumps: sampling, distance and false precision

A precise-looking number can still come from an uncertain measurement. Understanding scale makes a running chart easier to read.

What changes when you update your maximum heart rate?

Changing a setting can change the label attached to an old run. It does not change the heart rate that was recorded.

Heart-rate reserve versus percentage of maximum heart rate

Seventy percent of maximum heart rate and seventy percent of heart-rate reserve are different calculations. The percentage needs its method attached.

Why Zone 2 boundaries differ between running apps

“Zone 2” is a label within a zone system. To compare it meaningfully, compare the system and its inputs first.

Cadence lock and heart-rate spikes: how to check your running data

A surprising heart-rate trace can affect several downstream metrics. First check the recording; avoid assigning a physiological explanation from its shape alone.

Apple Watch to Runome through Apple Health: follow the data

Apple Watch data reaches Runome through Apple Health. Check each stage separately so a missing metric does not turn into a guessing exercise.

A workout imported, but a metric is missing: what to check

An imported activity can be valid without containing every kind of measurement. Identify the missing input before assuming the whole import failed.

GPX versus FIT: what a running file can actually contain

A file extension tells you the format. You still need to inspect which records and measurements are inside the particular file.

Best running app: choose the right fit for your training

The best running app is the one that helps you make a better next decision. Start with your running, your data and the questions you want answered.

Keep private details out of your running share card

A useful running post does not need to show every detail of the activity.

Square, portrait or story: choose your running-card dimensions

Changing the canvas shape changes the crop, even when the photograph and running statistics stay the same.

Camera pulse measurements versus a recorded heart-rate stream

Runome can use camera pulse measurements alongside a reconstructed heart-rate curve. The points are measurements; the values between them are estimates.

Choose the right running metrics for a share card

A good running card answers one question quickly. Choose the story first, then include only the measurements needed to support it.

Prepare a recorded run for a 3D route video

A route video depends on the route that was recorded. Start with the track and its gaps, then choose the presentation and overlay values.

Race a previous run with Runome Ghost Challenge

A previous run can provide a concrete reference for another outing. Choose a suitable route and understand the comparison before treating its progress display as a verdict.

Runome Free or Club: choose by the running task

Begin with the task you want to complete. Free and Club differ by specific capabilities, not by whether a run matters enough to analyze.

What to review when an adaptive running plan changes

An adaptive plan needs an accurate view of your running and schedule. When its next steps change, inspect those inputs before interpreting the change.

The best running analysis starts where pace ends

Most apps can report pace. Runome examines what the effort cost, whether it held together and whether the evidence is strong enough to trust.

Faster is not always more efficient

Running economy, heart-rate cost and why pace alone can misrepresent progress.

The second half of a run tells the truth

Aerobic decoupling, cardiac drift and what changes when durability begins to fade.

Training load is a timeline, not a weekly total

How Runome connects TRIMP, fitness, fatigue and form instead of simply counting kilometres.

A race prediction should know when not to predict

Why Runome considers effort quality, recency, distance relevance and confidence before showing an estimate.

Sometimes the most accurate metric is no metric

How Runome handles missing streams, sensor errors and insufficient evidence instead of inventing precision.