Does coasting downhill count as moving time on a bike ride?

The short answer

Coasting downhill counts fully toward moving time, in any app that works out moving time from GPS speed or position rather than from pedaling itself. A bike freewheeling down a slope is still moving, often faster than it was while being pedaled on the flat a minute earlier, so nothing about the way moving time gets calculated has a reason to treat that stretch any differently from a stretch where the legs were doing the work.

What moving time is actually built to notice

Moving time is elapsed time with the stopped stretches taken out, and an app decides what counts as stopped one of two ways: watching GPS speed and treating anything below a small threshold as stationary, or waiting for you to tap a pause button yourself. Whichever method is doing the deciding, the test underneath it is the same: are you covering distance right now, not what is making that happen.

A GPS receiver has no way to see a pedal, a chain, or a leg — it only ever sees a sequence of positions and the time between them. Coasting and pedaling produce exactly the same kind of input to that calculation: a phone moving from one point to the next, a little further along than it was a second ago. There is nothing in a plain record of position and time that reveals which one produced it.

Why pedaling was never the thing being measured

A dedicated cycling computer paired with a separate cadence sensor could, in principle, use whether the pedals are turning as its own signal — but that is a different piece of hardware answering a different question, strapped to the crank rather than sitting in a pocket. A phone tracking a ride with GPS was never wired to the drivetrain to begin with. Position is the only thing its receiver was ever in a position to measure, so position, and how it changes over time, is the only thing moving time can be built from.

Where an automatic threshold can actually get this wrong

A fast coast sits nowhere near the low-speed threshold an app uses to guess that you have stopped, so it is never the case that matters here. The real edge case runs the other way: creeping down a steep, technical section with both brakes feathered, barely faster than a walk, can land close enough to that threshold that an automatic detector misreads a few seconds of it as a stop, the same way it can misread someone walking very slowly over rough ground on foot. That says something about the limits of guessing from speed alone — it does not change whether the time should have counted. It was still covering ground the whole way down.

What TrailCam does

TrailCam has no automatic stop-detection guessing at your speed — recording pauses only when you tap to pause it, and paused time is the only time kept out of moving time. A fast coast down a hill and a slow, brake-feathered crawl down a technical one both count toward moving time exactly the same way pedaling does, because nothing except that pause button removes a stretch from the total. Route recording keeps running in the background the rest of the way, screen on or off. TrailCam is free to download.

Things that trip people up

• Assuming an app is somehow crediting you for coasting, as if it were rewarding less effort — it is not tracking effort at all, only distance covered, and a coast covers just as much of that as pedaling does.
• Expecting a fast descent to show up as a gap in the data because the legs stopped moving — the phone was never watching the legs, so nothing about a coast looks different to it from any other stretch of forward motion.
• Worrying that a long freewheeling descent will count for less toward a ride's total moving time — it counts for exactly as much as any other stretch covering the same ground in the same time, downhill or flat.
• Confusing this with automatic stop-detection misreading a genuinely slow, brake-feathered crawl down a technical section — that is a real edge case, but it is about very slow speed sitting near a threshold, not about coasting as such.