You already have a cycling computer that cost more than most people's watches. It talks to your power meter, it knows your FTP, and it has years of your training history sitting behind it. So when you start running twice a week, a reasonable question follows: do you really need another screen — this one strapped to your wrist?
Sometimes yes, sometimes no, and the deciding factor is not the one the watch industry wants you to focus on. It is not about which model has the most metrics. It is about whether your running data and your cycling data end up in the same place, telling you one coherent story about your training.
Get that right and the watch is one of the better purchases you will make as a dual-sport athlete. Get it wrong and you will spend $700 to own two apps that do not talk to each other.
The one-ecosystem principle
Start here, because it simplifies every decision that follows: if you already own a cycling setup from Garmin or COROS, the strong default is to test the matching watch ecosystem first, not start a second data silo.
The reason is training load. Every platform — Garmin Connect, COROS's app, Wahoo's — builds its picture of your fitness and fatigue from the activities it can see. When your rides land on one platform and your runs on another, each one sees half an athlete. Garmin thinks you are fresher than you are because it never saw Tuesday's run. Your recovery guidance, load tracking, and status estimates all degrade, because they are computed from incomplete data.
Keep everything in one house and the estimates have a better chance of seeing the whole week. Your Edge records the ride, your Forerunner records the run, and Garmin Connect can process both. COROS can do the same with DURA and APEX. Apple has no matching bike computer, while Wahoo has no matching watch, so those owners need a neutral training platform if they want one combined calendar.
This is why "which watch is best" is the wrong first question. The better sequence is: which platform already owns my useful history, which sensors and workouts must the watch support, and where will both sports be reviewed? Garmin leads the recommendations for an Edge owner; it is not automatically the right answer for everyone else.
What actually matters in a multisport watch
Watch marketing is a firehose of features. For a cyclist adding running, the list of things that matter is short.
GPS accuracy. Pace is running's power meter, and pace comes from GPS. Modern multiband GPS — which all four watches below have — is dramatically better than the previous generation, especially under trees and among buildings. This is the one hardware spec worth caring about.
Wrist heart rate, with realistic expectations. Optical wrist HR has improved enormously and is now fine for steady running. It still lags and stumbles during hard intervals and it reads poorly on the bike, where vibration and grip ruin the signal. You own a chest strap already; it pairs with every watch here. Use it for anything hard.
Training load in one place. Covered above, but it bears repeating because it is the actual reason to buy the watch: one number that reflects both sports.
Battery you can verify for the exact model. Manufacturers publish different figures for smartwatch mode, satellite mode, music, display behaviour and case size, so one headline number is misleading. Garmin rates the Forerunner 970 up to 15 days in smartwatch mode and 21 hours in all-systems multiband mode. COROS quotes 41 or 65 hours for APEX 4 endurance satellite mode by size. Apple quotes up to 42 hours of normal use and 72 hours in Low Power Mode for Ultra 3. Treat all of those as controlled claims, not promises for your settings.
Maps, if you ride and run in new places. Full offline mapping used to be a flagship-only feature. It no longer is, and if you travel — training camps, work trips, holidays where you sneak runs in — it is worth having.
That is the list. Running power, lactate threshold estimates, race predictors and readiness scores are all interesting, none essential, and most need a pinch of salt anyway.
The four watches worth your money
Not a review of everything on the market — the market does not need another one of those. These are the four that make sense for a cyclist adding running, and why.
| Watch | Best fit | Cycling ecosystem | Battery claim to compare | Main trade-off |
|---|---|---|---|---|
| Garmin Forerunner 970 | Edge owner adding serious running | Garmin Connect / Edge | Up to 15 days smartwatch; 21 hours all-systems multiband | Premium price for a running-first watch |
| Garmin Fenix 8 | Rider who also needs rugged outdoor breadth | Garmin Connect / Edge | Varies by case size, AMOLED/Solar and mode | Heavier and often more watch than run/ride alone needs |
| COROS APEX 4 | COROS DURA owner or mountain-focused runner | COROS / DURA | 41 hours (42 mm) or 65 hours (46 mm) endurance satellite mode | Different headline battery mode from Garmin/Apple figures |
| Apple Watch Ultra 3 | iPhone-first athlete who values smartwatch features | Apple Health; no Apple bike head unit | Up to 42 hours normal use; 72 hours Low Power Mode | More frequent charging and a less cycling-native ecosystem |
These are manufacturer claims under different test modes, not a like-for-like battery test. Check the exact size, display setting, current price and return policy in your region.
Garmin Forerunner 970 — the best fit for an Edge owner who is adding running. It records cycling, supports compatible power sensors, includes maps and keeps rides and runs inside Garmin Connect. Garmin quotes up to 15 days in smartwatch mode and up to 21 hours in all-systems multiband satellite mode; music, display use and connected sensors reduce that. It is the cleanest use-case fit here, not a claim that it beats every watch in independent accuracy testing.
Garmin Fenix 8 — the rugged outdoor alternative. It adds a tougher, dive-rated build and a broader outdoor brief while retaining Garmin mapping, cycling profiles and sensor support. Battery varies materially by AMOLED versus Solar and by case size, so compare the exact variant rather than borrowing a headline from another Fenix. For running and cycling alone, the Forerunner is usually the cleaner buy; Fenix makes sense when the build and wider outdoor feature set are part of the job.
COROS APEX 4 — the natural DURA pairing. It combines titanium and sapphire construction with offline landscape/topographic maps, turn-by-turn guidance and COROS training/recovery tools. COROS quotes up to 41 hours for the 42 mm and 65 hours for the 46 mm model in its endurance satellite mode. Its strongest argument is no longer simply price: it is the joined-up DURA/APEX/COROS platform. A Wahoo owner can also choose it, but should do so because the watch fits—not because Wahoo data becomes natively COROS data.
Apple Watch Ultra 3 — for the Apple household. It pairs with compatible Bluetooth cycling sensors, can display power/cadence and supports FTP-based power zones. Apple quotes up to 42 hours of normal use or 72 hours in Low Power Mode, well short of the longest Garmin/COROS modes but no longer a nightly-charge-only proposition. Choose it when iPhone integration and smartwatch functions matter as much as the sports platform; connect Apple Health and the Workout App explicitly if TrainingPeaks is your combined calendar.
Do you need a bike computer AND a watch?
The question every cyclist asks at this point, so here is a straight answer.
If you race, or train with structure on the bike: yes, keep both. A head unit on the bars is simply the better tool for cycling. Big glanceable data fields mid-effort, proper routing you can follow at 40kph, clean pairing with power meters and shifting, and no craning at your wrist while riding on someone's wheel. The watch handles running, sleep, and everyday load tracking; the Edge or Bolt handles the bike. They are not redundant — they are a division of labour, and if they share an ecosystem the data merges anyway.
If you are casual about both sports: no. A Forerunner or Apex on your wrist will record your rides perfectly well — speed, heart rate, even power if you have a meter. Riders who never look at data mid-ride and just want everything logged can sell the head unit. Most readers of this site are not that rider, but plenty of their partners are.
A phone can record an occasional run perfectly adequately, so do not buy a watch merely to satisfy the gear checklist. The limitations are practical: pace is less glanceable, all-day/sleep context is absent, and the file may land outside the platform that owns the rest of your training. Test the phone workflow first if you run casually.
The running numbers worth watching
A watch will hand you fifteen running metrics. Three deserve your attention.
Pace — but treat it like power, not like a verdict. Your easy runs should be properly easy, and new runners off the bike are almost universally shocked by how slow that is. The watch's job on easy days is to hold you back.
Cadence. Steps per minute, useful as an individual baseline rather than a universal score. A systematic review found that increasing step rate generally shortens step length and changes several hip, knee and ankle loading variables, but evidence for injury and performance outcomes was insufficient. If video, pain or a clinician suggests overstriding, trial a modest increase from your normal cadence at the same pace; do not force 180 because a watch or podcast treats it as a law.
Heart rate, with the chest strap for anything hard. HR is how you keep easy runs easy when ego says otherwise, and how your platform computes load across both sports. If you haven't set your heart rate zones yet, do that before your first run — the zones your watch auto-generates from age-based formulas are usually wrong.
Ground contact time, vertical oscillation and the rest of the running-dynamics suite can describe how your gait changes, but a watch does not diagnose an injury from them. Start with pace, effort, heart rate and consistency; use form metrics when a specific question or qualified gait review makes them actionable.
Make everything land in one dashboard
Whatever you buy, connect the relevant platform deliberately rather than assuming every app talks in both directions. TrainingPeaks documents completed-activity connections for Garmin Connect, COROS and Wahoo. Apple requires the Apple Health and Apple Watch Workout App connections inside TrainingPeaks. Check the permissions and send a short test workout before trusting the calendar.
This is the piece that lets one calendar account for two sports. A hard run on Tuesday is load your Thursday intervals inherit — the weekly schedule article covers how to sequence the two sports — and a system that sees both gives you a better record than two disconnected apps. Its load and recovery scores remain modelled estimates, so use them with how you feel and what the session actually demanded.
The watch industry sells screens. What you are actually buying is the pipe that connects your running to everything you already know about your cycling. Pick the watch that keeps the pipe short — same ecosystem as your head unit, synced to one dashboard — and the hardware choice mostly takes care of itself.