Skip to main content

Analytics

Every run you log feeds one place: your Analytics dashboard. It turns raw splits into a clear picture of whether you're getting faster, fitter, and more efficient — the questions a training plan is supposed to answer.

Open it at løbeapp.dk/analytics.

[[SCREENSHOT OF THE ANALYTICS DASHBOARD WITH THE OVERVIEW TAB]]

How to read it​

Two controls sit at the top of every tab:

  • Date range — quick presets (Last 4 weeks, Last 12 weeks, Last 6 months, Last 12 months) or a custom from–to range. Your choice is saved in the URL, so you can bookmark or share a view.
  • View tabs — Overview, Interval analysis, and Long run.

Everything is grouped by calendar week, and most metrics compare your Actual runs against the Forecast from your programme — so you always see performance against the plan, not in a vacuum.

:::tip Lower pace is better Pace is shown in min/km, so a lower value means faster — on the pace charts, a line that drops is an improvement. :::

Overview tab​

The big-picture health check of your training block.

KPIs​

A row of headline numbers for the selected range:

KPIWhat it tells you
Total KMVolume logged in the window — the biggest driver of endurance
Avg paceAverage speed across all runs (min/km)
Pace per HRSpeed earned per heartbeat — your efficiency in one number
Avg HRAverage heart rate
Avg RPEAverage perceived effort (1–10)
Interval spreadHow even your interval reps were, with a rating

Charts​

  • Distance per week — actual kilometres (bars) against your planned volume (line). Look for gradual build; big jumps invite injury, flat weeks mean you're holding volume to sharpen quality.
  • Pace development — actual vs forecast pace over time. Actual below forecast? You're running ahead of plan.
  • Performance efficiency — your Pace per HR plus a 3-week trend line. A rising trend means you're producing more speed for the same effort — the clearest sign real fitness is building.
  • Heart rate over time — average HR alongside pace-per-HR. Falling HR at a held pace is a strong positive signal.
  • RPE over time — how hard the weeks felt. Effort creeping up while pace stalls can be an early flag for fatigue.

[[SCREENSHOT OF THE OVERVIEW CHARTS]]

Interval analysis tab​

Zooms into your interval (speed) sessions, rep by rep. Built for sessions logged as Intervals, using the segments you mark as reps.

  • Pace per interval per week (heatmap) — every rep as a coloured cell. Greener = faster. Read down a column to see a rep improve across weeks.
  • Heart rate per interval per week (heatmap) — the same grid for heart rate.
  • Interval fatigue curve — one line per week across the reps in a set. A flat line means you held pace from first rep to last; a line that sags means you faded. Pacing discipline shows here first.
  • Pace vs HR (per interval) — each rep plotted as pace against heart rate; bubbles grow with rep number. Points drifting right and up late in a set show accumulating fatigue.
  • Interval spread per week — the gap (in seconds) between your fastest and slowest rep. Lower is better; we rate it Excellent (≤6s), Good (≤10s), OK (≤15s), or Needs Work (>15s).

[[SCREENSHOT OF THE INTERVAL ANALYSIS TAB]]

:::tip Why even reps matter Negative-split, evenly-paced intervals train your body to hold a target speed under fatigue — the exact skill a race demands. A tight spread is often a better fitness signal than a single fast rep. :::

Long run tab​

Your endurance engine, week over week. Built from sessions logged as Long runs.

  • LR distance per week — actual vs forecast distance (bars) with average heart rate (line). The backbone of aerobic development.
  • Long-run pace over time — actual vs forecast pace. Faster long runs at the same effort mean your endurance is improving.
  • Long-run load — average HR and RPE together, so you can see how demanding each long run really was.
  • Progressive finish — full-run pace vs your finish pace, plus an acceleration line (how much you sped up by the end). A strong, faster finish shows you still had gas in the tank — the hallmark of a well-judged long run.
  • Long-run efficiency — pace-per-HR over your long runs. A climbing line means you're getting more economical over distance.

[[SCREENSHOT OF THE LONG RUN TAB]]

How the metrics are calculated​

A few definitions so the numbers are unambiguous:

  • Weeks are ISO calendar weeks, derived from each run's date.
  • Pace = total time ÷ total distance, in seconds per kilometre.
  • Pace per HR = pace ÷ heart rate — lower is better (more distance per heartbeat). The efficiency trend is the rolling average of this over the three most recent weeks.
  • Interval spread = fastest rep − slowest rep, in seconds, for your latest interval session. Reps are the segments labelled as such in a session.
  • Progressive finish / acceleration compares the first and last splits of a long run.
  • Comparisons against Forecast use the planned sessions from your active programme.

Only your own non-deleted runs are counted, and only within the date range you pick.

:::note Garbage in, garbage out The analytics are only as good as your logging. Log heart rate and mark your interval reps and long runs with the right session type, and these charts become genuinely useful coaching feedback. See Logging a run manually. :::