What Makes a Fake Run Look Real?

There's a difference between a fake run and a convincing fake run.

The first is a flat line on a map with a suspiciously round distance and a perfectly constant pace. The second looks like something a human actually did — messy, variable, real.

Dibma is built around making the second kind. Here's what actually matters.

Pace variation

Real runners don't hold a perfectly constant pace. They slow down slightly on uphills, speed up coming down, ease off when their lungs get heavy, and push a little harder when they see the end coming.

A generated FIT file that outputs exactly 5:30/km for every single kilometer is immediately suspicious to anyone who looks closely. Good generators introduce natural variation — maybe ±20–30 seconds per km around your average — in a way that correlates with the elevation profile.

Heart rate that follows the effort

Heart rate is the single biggest giveaway when it's wrong. Two red flags:

1. Flat heart rate — a straight line at 155bpm for 45 minutes doesn't happen in real life. Heart rate drifts up over the course of a run even at the same effort level, a phenomenon called cardiac drift.
2. Heart rate that doesn't match the pace — if the pace data shows a hard effort but the heart rate is 110bpm, something's off.

A realistic heart rate starts lower, climbs through the warmup, holds in your aerobic zone with small fluctuations, and drops sharply when the run ends.

A route that makes geographic sense

Drawing your route through a park, then through a building, then across a river with no bridge is a bad look. The route should follow paths, roads, and trails that actually exist.

Strava also has a segment system — many popular running routes have well-known segments with leaderboards. Running through areas where segments exist makes an activity feel like it was recorded in a real place.

The right distance for the time

A 5km run that took 18 minutes from someone with no history of fast running will raise eyebrows. Match your fake run to a pace that's plausible for you specifically, or plausible for the profile you're building.

Elevation that matches the terrain

This one is often overlooked. If you draw a route through hilly terrain but your activity shows zero elevation gain, it looks wrong. Dibma pulls real elevation data from the route you draw, so the elevation profile matches the actual terrain.

Start and end at a logical place

Runs typically start and end at home, a gym, a park entrance, or a well-known starting point. A run that starts in the middle of nowhere and ends in a different suburb for no apparent reason draws more scrutiny than one that begins and ends at the same point.

None of this matters if you're just logging a missed run for your own records. But if the goal is a fully convincing activity, the details add up quickly.

The checklist is short: real-looking route, variable pace, proper heart rate curve, matching elevation. Get those four right and the activity looks indistinguishable from one recorded on a real watch.

— Dunn