Runome Recorder
Record outdoor runs with location, elapsed and moving time, distance, live pace and route data.
RECORDING & IMPORTS
Bring your running history.
Connect Apple Health, Garmin, Polar or Suunto. Bring your activities into one history, or record your next run with Runome.
Record, add
or connect.
Available fields vary by device and workout. Runome calculates stream-dependent metrics only when the required evidence is present.
Apple Health
Connect Apple Health to import authorized running workouts and available workout data, including Apple Watch activities.
Garmin Connect
Connect Garmin through Data Sync for incremental activity imports, historical backfill and available FIT stream enrichment.
Suunto
Connect Suunto through Data Sync for activity and route imports, ongoing synchronization and historical backfill.
Polar Flow
Connect Polar through Data Sync for exercise imports and the available heart-rate, cadence and elevation streams.
Samsung Health
Import Samsung Health and Health Connect workouts through compatible connections.
Manual activity
Add a completed run when no connected source is available. Manual records enter the same activity history but only support metrics backed by the fields supplied.
One run.
No duplicate history.
Every imported activity passes through the same validation, provenance and data-quality checks before analysis.
- 01
Normalize
Provider fields are converted into common units for time, distance, pace, heart rate, cadence, elevation, power, temperature and GPS.
- 02
Validate
Runome checks required fields, numeric ranges, timestamps, sport type and stream quality before accepting the record.
- 03
Deduplicate
Provider IDs, timing, duration, distance similarity and a stable fingerprint help merge the same workout arriving from multiple sources.
- 04
Preserve
The user sees one canonical activity while Runome retains every source relationship and selects the best available stream coverage.
- 05
Analyze
New or changed runs enter the versioned compute pipeline for classification, per-run metrics, trends and coaching.
The source changes.
The evidence can too.
A connected brand does not guarantee every metric on every workout. Sensor permissions, device model, recording settings and stream quality all matter.
Location quality matters
GPS drift and low-quality altitude samples can affect route, grade and climbing analysis. Unreliable elevation can be omitted.
Streams unlock depth
Recovery, TRIMP, HR drift, decoupling, economy and VO₂max estimation require usable heart-rate evidence and correct profile settings.
Not every watch sends it
Cadence and stride evidence contribute only when enough valid samples are available. Their absence does not become an estimate.
Consent firstRecording, manual activity creation, provider connection, import and analytics stay disabled until the runner grants the current health-data purposes in Runome. Consent can later be withdrawn from Data Sync.
Get more from your running history
Start with the question you want your data to answer.
APPLE WATCH DATA
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.
IMPORT TROUBLESHOOTINGA 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.
ACTIVITY FILESGPX 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.
RUNNING DATAMoving 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.