How do I upload a FIT or GPX file to the RunFast 200?
Updated
On the RunFast 200 screen at runfast.tech/app/#/r200, or in the RunFast app, choose one FIT or GPX file from your watch, up to 10 MB. RunFast checks it at once: Counted, Checking (a person looks at it), or refused with the exact reason. The track is deleted after the check. Uploads are open from 16 December to 23:59 GMT on 3 January.
Runs you record on a watch can count toward the RunFast 200 without Strava. Upload the file, and RunFast checks it automatically.
Upload a file
- Join the RunFast 200 first. See joining the RunFast 200.
- Open the RunFast 200:
- On the web: runfast.tech/app/#/r200, or Open on the RunFast 200 banner on Runs. Under Upload a FIT or GPX file, tap Choose a file.
- In the RunFast app: the RunFast 200 screen, then Upload a FIT or GPX file.
- Pick one
.fitor.gpxfile, up to 10 MB. FIT is best: it’s what Garmin, COROS and most watches save.
You see the answer straight away:
| Answer | What it means |
|---|---|
| Counted | It counts, with its distance. |
| Checking | “We’re checking this one. It counts once it’s approved.” A person looks at it, and it counts once approved. |
| Counted once | “Counted once: it overlaps a longer one.” The longer run counts instead. |
| Refused | It doesn’t count. The reason says exactly why (below). |
Uploads are open from 00:00 GMT on 16 December until 23:59 GMT on 3 January, so late syncs still count. Up to 40 uploads a day.
What’s checked
- The dates: every point has a time, and the run started between 16 and 31 December, in GMT.
- Real movement: the times only go forward, nothing jumps faster than anyone can run, and the speed is believable for a run, on average and minute by minute.
- A real recording: a route planner’s export has perfectly even, steady times. It’s refused.
- Not twice: the same file, or the same run already counted from anyone’s file, is refused. A run that overlaps another of yours in time (Run live, an upload or Strava) counts once: the longer one counts, and the other says “Counted once: it overlaps a longer one.”
- Treadmill runs count, with no GPS needed, if the file has its distance and times. Only the distance its own records cover counts.
- The device: a FIT file’s maker and model are kept with the run, such as “Garmin Forerunner 265”.
Why a file was refused
| What you see | What to do |
|---|---|
| “Enter the RunFast 200 first.” | Join, then upload again. |
| “Uploads open when the challenge starts on 16 December.” | Upload from the 16th. |
| “Uploads closed at 23:59 GMT on 3 January.” | Uploads are over. |
| “That file is over 10 MB.” | Export it again from your device, or upload the FIT file instead of a GPX. |
| “That isn’t a FIT or GPX file we can read.” | Upload the original .fit or .gpx file from your device. |
| “Every point needs a time. This file has points without one.” | It’s a route, not a recording. Upload the file your device recorded. |
| “This activity started on 14 Dec, outside the challenge (16–31 December, GMT).” | Only runs that start in the window count. |
| “This activity starts in the future.” | Check your device’s date and time. |
| “This isn’t a run.” | The file says it’s another sport, or it’s too fast for a run. |
| “The times in this file go backwards.” | The file is damaged or edited. Upload the original. |
| “This file jumps 5 km in 30 s, faster than anyone can run.” | Upload the original recording. |
| “This is too fast for a run: 31 km/h on average while moving.” (or “for minutes at a time”) | It isn’t a run, or it was recorded on a bike or in a vehicle. |
| “This looks like a planned route, not a recorded run.” | Upload the file your device recorded, not a planner’s export. |
| “You’ve already uploaded this file.” | It counts already. |
| “This activity has already been counted.” | The same run is in the challenge from another file. |
| “An indoor run needs its distance and times.” | Export the treadmill run again, with its distance. |
| “This file is too short to count.” | Runs under 1 km don’t count. |
| “That’s a lot of uploads for one day. Try again tomorrow.” | Over 40 uploads in a day. |
The numbers and dates in a message are your file’s own.
Why a file is checking
A person looks at a file before it counts when it’s unusual but could be real: a little fast or very steady, a gap of more than 3 hours, over 30 hours long, a device distance that differs from its track by more than 10%, a start time in its header that differs from its first point, or a very long treadmill run. It counts as soon as it’s approved, and if it’s refused, the reason shows.
What’s kept
The run’s date, distance, moving time, sport, the source (an upload), the device, the result and its reason, and scrambled fingerprints of the file and its shape, so the same run can’t count twice. The fingerprints can’t be turned back into a route. The track itself is deleted once it’s checked. The check runs on Windline’s server, RunFast’s sister product, which counts the RunFast 200. See what RunFast keeps.
Every upload, and what it counted, shows under Your runs on the same screen. Uploading is on the web at runfast.tech/app/#/r200 now, and in the RunFast app on iPhone and Android from its next update, around 10 December.