My Runs
Your biomechanical profile and running form analysis.
Run Analysis
Run Analysis
BasicWe sync your Garmin runs and turn the usable ones into your running profile.
AdvancedWe analyse synced Garmin activities and uploaded FIT files, extracting cadence, GCT, vertical oscillation and stride length when those signals are available. To add more runs, upload FIT files or ZIP files that contain FIT files.
Non-running activities are skipped. The first sync can take longer; later syncs process only new activities.
Sync & analyse your Garmin activities to build your running profile.
No runs found
We need runs on flat terrain at easy pace (4:30-5:30 min/km) to generate accurate recommendations.
Connect your running data
Pick where your runs come from. You can add more later.
Garmin Connect™
The Garmin Connect™ app is your one-stop source for health and fitness data.
Link your account to sync and analyse your running data automatically.
Biomechanical Signature
Biomechanical Signature
What it shows
Your cleanest comparable running form by pace. We group fresh-window mechanics like GCT, cadence, vertical oscillation, stride length and derived metrics into pace brackets so you can see how your form changes from easy to fast running.
Why fresh windows
Running form is noisy: surges, pace changes, hills, warm-up, fatigue and sensor patches can all distort the signal. The fresh window filters toward the stable baseline for each run, and each bracket gets a confidence signal. If a run has a cleaner section than the automatic window, adjust and save it in Drift Inspector.
How to use it
Compare shoes, sessions and training blocks at the same pace to see which setup helps your mechanics. Use it to track whether form work, strength training or shoe changes make lift-off, contact time or loading more efficient, and which pace zones need attention.
Raw biomechanics across pace zones. Dot size = data confidence. Slide to explore each bracket – tap a card to expand.
Your running form score
Metric Title
Runner type
Fatigue Resilience Profile
Fatigue Resilience Profile
What it shows
Your run profile has two layers: your baseline running form, and how long you can keep that form when fatigue builds. Fatigue Resilience shows where GCT and HR drift stay low, and where they rise as pace, distance or effort increase.
Why it matters
Pace-coupled GCT drift is used as a mechanical efficiency proxy: when it rises late, your form is becoming less durable. HR drift shows the physiological side. Reading both together helps show whether the limiter is mechanical fade, heart-rate drift, or both moving at the same time.
How to use it
Filter by run type, confidence, date and shoe to compare fatigue resilience in different settings. For example, if one shoe shows higher ground-contact-time drift or HR drift under the same run type or pace band, it may be more taxing on your resilience; lower drift suggests it helps you hold mechanics or effort better.
This section shows how your form holds up as runs get harder
Your fatigue resilience score
GCT drift by pace
Select run type
Run type filter
BasicChoose which kind of run you want this fatigue and shoe view to focus on.
AdvancedThe selected use case changes the highlighted matrix cells and the LPI projection, so daily training, long runs, tempo efforts and race demands are not mixed together.
Fatigue by run type
Run evidence matrix
BasicEach cell shows the typical late-run change. Negative means a decrease; positive means an increase. Select a run in its tooltip to open Drift Inspector.
AdvancedThe rows match the score cards. Values are signed median changes across usable medium/high-confidence runs. Only the score treats decreases as zero fatigue.
Economy impact (LPI)
How Economy Impact works
BasicWe estimate whether fatigue makes your running load lighter or heavier.
AdvancedLPI is most stable in the 4:30-5:30 /km easy-pace window. For tempo, long runs and races, we combine your baseline LPI with your observed pace-coupled GCT fatigue to project how loading economy changes under that effort.
A negative shift means LPI is projected lower because pace-coupled GCT rose, so loading economy became less durable under fatigue. Flat or higher values mean the run held closer to its baseline.
Drift Inspector
Drift Inspector
What it shows
Pick a run, then use the fresh window as the stable baseline and the end/fatigue window as the later comparison.
What this updates
Drift Inspector recalculates pace-coupled GCT, HR drift, pace, samples and terrain as the windows move. Those metrics help tell whether the result is a real fatigue signal or an artifact of pacing, hills, warm-up, sensor noise or too few samples. Pace coupling removes the part of GCT or HR change expected from running faster or slower, then leaves the remaining drift.Saving windows updates the stored fresh window for that run. Those values feed the Biomechanical Signature and Fatigue Resilience Profile, and they also affect shoe recommendations and shoe efficiency wherever this run is included.
How to use it
Use the auto high-confidence placement as a starting point, then adjust the windows if you know a cleaner or more representative part of the run. Changing windows updates the drift metrics and confidence score. Save windows stores your manual placement and updates fresh/end pace, GCT, pace-coupled GCT drift, and HR drift including pace-coupled HR when available. Reset windows returns to auto or the last saved placement. Use the metric selectors to inspect raw GCT, cadence, vertical oscillation, stride length, LPI or raw HR from fresh to end.
Inspect individual runs – see pace, GCT & elevation streams with drift calculation windows.
Drift Inspector chart
Elevation profile
Route map
