No. Timing runs entirely on the device — every time is stamped against the phone's own clock and stored locally. Live results and publishing need a connection, and the app syncs whatever it recorded as soon as one is available. Plenty of races get timed in a field with no bars and uploaded from the parking lot.
The full timing session is written to the device continuously. Reopen the app and the race resumes with the clock in the right place and every recorded time intact, because the clock is anchored to a real timestamp rather than a counter that resets.
Impulse is the button that captures the time. Post stages a bib beforehand, so when that runner crosses, Impulse costs a single tap instead of several keystrokes — the most accurate way to time a finish. Impulse with nothing typed banks a bare time you can match to a bib afterward.
Yes, and it's a supported way to work. Type bibs as they finish and the order is correct immediately. Names go in afterward — in the app, or from a laptop on the web editor while someone else keeps timing.
Yes. Time the finish on one phone and a checkpoint on another, or run a second phone as a backup on the line. The times merge into one result, and the merge page shows you where the devices disagree rather than quietly picking one.
Gun time runs from the front of the race; chip (or net) time runs from when that runner's own wave actually started. In a mass start they're identical. With waves they differ, and RaceTraceTiming shows both and ranks on net time.
Yes, and this is the important one. Times are stored as absolute timestamps rather than elapsed durations, so correcting the gun re-derives every result automatically. You don't re-enter anything.
Share the race code and anyone can open the results page in a browser. While the race runs they see finishers and checkpoint splits appear live, and a link opened before the gun comes alive on its own when the race starts.
Anything with named legs. Triathlon and duathlon are the common cases, but the legs are yours to define, so aquabike, swim-run, or a three-stage adventure race all work. Transitions can be timed as their own segments or folded into the next leg.
A race is unlisted until you publish it. Unlisted races are reachable only by their code and never appear in the public archive. Publishing is an explicit action, and you can unpublish at any time.
Something not answered here? Email support@racetracetiming.com.