Help
What the app does, how it talks to your watch, and which models it supports.
What does UltraPacerBG do?
It builds a pace for every kilometre of your course from that kilometre's gradient, so the target time stays reachable on the climbs and on the descents alike. During the race the watch field shows two numbers: how far ahead of or behind the plan you are, and how long is left to the next checkpoint — to its cut-off, if it has one. Before the start there is a printable checkpoint card. After the finish you upload the recording from your watch — “How it went” — and get an analysis: where you gained and lost against the plan, and what to change next time. You can upload several runs against one plan.
How does the plan reach the watch?
- 1Download the watch field and put it on your watch.
- 2Pick a race — or upload your own GPX — and set a target time. Most races already have their checkpoints and cut-offs.
- 3Start an activity — the field shows a code; enter it on the site, once.
- 4On the course page press “Active for the watch” — that is the plan the watch carries. Without an active course the watch is connected but has nothing to pull; the site reminds you with a note.
After that the watch keeps itself current. Change the course or the target time and it picks up the new plan — no re-installing, no new code. Connecting and the state of the connection live on the Watch page.
Why is the plan worked out on the site and not on the watch?
The plan is worked out here rather than on the watch, because the watch can't see the profile of the whole course — only the next point ahead. That's also why you connect only once: the code tells the site which watch it is, not which plan. Which plan it carries — your active one — is decided here, at any moment.
Every plan carries a revision number, shown both on the site and on the watch. It exists so you can check at a glance that what you're carrying to the start is exactly what you planned, and not an older version of it.
Does it work on anything other than a Garmin?
The watch field runs on Garmin watches with Connect IQ. Courses, plans and cut-offs are built here on the site and readable on any device. Without a Garmin the plan is still yours: the checkpoint card prints or lives on your phone — when you reach each checkpoint and how much margin you have to its cut-off.
Supported watches
68 modelsIf your model is on the list, the field will show up in the Connect IQ Store on your phone.
Enduro
- Enduro™
- Enduro™ 3
epix
- epix™ (Gen 2) / quatix® 7 Sapphire
- epix™ Pro (Gen 2) 42mm
- epix™ Pro (Gen 2) 47mm / quatix® 7 Pro
- epix™ Pro (Gen 2) 51mm / D2™ Mach 1 Pro / tactix® 7 – AMOLED Edition
fenix
- fēnix® 5 Plus
- fēnix® 5S Plus
- fēnix® 5X Plus
- fēnix® 6 / 6 Solar / 6 Dual Power
- fēnix® 6 Pro / 6 Sapphire / 6 Pro Solar / 6 Pro Dual Power / quatix® 6
- fēnix® 6S / 6S Solar / 6S Dual Power
- fēnix® 6S Pro / 6S Sapphire / 6S Pro Solar / 6S Pro Dual Power
- fēnix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power
- fēnix® 7 / quatix® 7
- fēnix® 7 Pro
- fēnix® 7 Pro - Solar Edition (no Wi-Fi)
- fēnix® 7S
- fēnix® 7S Pro
- fēnix® 7X / tactix® 7 / quatix® 7X Solar / Enduro™ 2
- fēnix® 7X Pro
- fēnix® 7X Pro - Solar Edition (no Wi-Fi)
- fēnix® 8 43mm
- fēnix® 8 47mm / 51mm / tactix® 8 47mm / 51mm / quatix® 8 47mm / 51mm
- fēnix® 8 Pro 47mm / 51mm / MicroLED / quatix® 8 Pro 47mm / 51mm
- fēnix® 8 Solar 47mm
- fēnix® 8 Solar 51mm / tactix® 8 Solar 51mm
- fēnix® 9 43mm
- fēnix® 9 47mm / 51mm
- fēnix® 9 Pro 43mm
- fēnix® 9 Pro 47mm
- fēnix® 9 Pro 51mm
- fēnix® 9 Pro Solar 47mm
- fēnix® 9 Pro Solar 51mm
Forerunner
- Forerunner® 55
- Forerunner® 70
- Forerunner® 165
- Forerunner® 165 Music
- Forerunner® 170
- Forerunner® 170 Music
- Forerunner® 245
- Forerunner® 245 Music
- Forerunner® 255
- Forerunner® 255 Music
- Forerunner® 255s
- Forerunner® 255s Music
- Forerunner® 265
- Forerunner® 265s
- Forerunner® 570 42mm
- Forerunner® 570 47mm
- Forerunner® 645 Music
- Forerunner® 745
- Forerunner® 945
- Forerunner® 945 LTE
- Forerunner® 955 / Solar
- Forerunner® 965
- Forerunner® 970
Instinct
- Instinct® 2 / Solar / Dual Power / dēzl Edition
- Instinct® 2S / Solar / Dual Power
- Instinct® 2X Solar
- Instinct® 3 AMOLED 45mm
- Instinct® 3 AMOLED 50mm
- Instinct® 3 Solar 45mm / 50mm
- Instinct® Crossover
- Instinct® Crossover AMOLED
- Instinct® E 40mm
- Instinct® E 45mm
Venu
- Venu® 3
Didn't find the answer?
Write to us — a question, a mistake in a race's data, or an idea. We reply personally.
How the plan is worked out — and how it learns from you
- 1The course: the GPX gives the gradient of every stretch. Each stretch gets a “cost” — how much effort it takes against the flat: steep climbs cost more, gentle descents less, and steep descents slow you again, the more carefully you go down.
- 2The target: the time you chose is shared out over the stretches by their cost — so every kilometre has its own pace, and they add up to exactly your time. Rests at the checkpoints and technical sections are taken out separately.
- 3Your answers: the gradient at which you start hiking and how you descend tune the cost of climbs and descents. Your maximum pace shows where the plan asks for more than you can do.
- 4Your runs: every uploaded recording (“How it went”) is compared with the plan. From all your runs the site works out how much more or less time climbs and descents take you against the flat — and your next plans are worked out with that. Carefully at first (one run counts for half), more with every run. The factors are shown on every plan.
- 5Everyone together: once there are enough runs from enough people, the model is tuned for everybody too — for anyone with no runs of their own yet. So every uploaded run makes the plans more precise for others as well.
- 6Course technicality: if runners are slower on the flat and downhill than the gradient explains, the course gets a rating from “Easy terrain” to “Extremely technical” — once there are runs from at least two people. The plan then gives you more time on the most technical sections (at most +50%) without changing your target.
The maths in detail
- A gradient above 8% (or whatever you chose) is planned as a fast hike, not a run. If you run it, you will be ahead of the plan there. The times include the rests planned at the checkpoints.
- Pace by gradient is calculated with Minetti (2002) — the energy cost of running relative to the flat. Climbs follow the curve as published. Descents have their benefit capped: the model on its own claims a steep descent is run at twice flat speed, which does not hold on mountain terrain.
- The plan carries fatigue — the final kilometre is that much slower than the first at the same gradient. It grows with the length of the race and is measured in accumulated effort rather than kilometres. The total does not change: the start gets faster so the end can be slower.
Sources and inspiration
- RunPowerModel — The idea of rating technicality — after RunPowerModel's “Trail Score” (Markus Holler). The maths is our own.
- Minetti et al. (2002) — The energy cost of running and walking on slopes — the curve the pace is worked out from. “Energy cost of walking and running at extreme uphill and downhill slopes”, Journal of Applied Physiology.
Support
If you have finished a race on a plan made here, you can stand a coffee — it goes on the server, the domain and the database, nothing else. It unlocks nothing and removes nothing: everything here is the same for everybody.