Which race formats does DB Timer support?
Use a single-loop race for one finish crossing, fixed laps for a set lap count, or timed laps for the most full laps within a time limit. Multiple races and named heats can have independent starts, with standings calculated for each race.
Is DB Timer available on the App Store?
DB Timer is preparing for club beta testing. Public App Store availability, pricing, and a release date have not been announced. See tester information for installation details.
Which devices can run it?
The current app targets iPhone and iPad running iOS or iPadOS 18.1 or later. Test the device you intend to use before race day.
Can races start at different times?
Yes. Races and heats have independent starts. The Timer screen routes a unique bib to its race, so runners from different active races can share the lap line. Use unique bibs across the event for the simplest entry workflow.
How are timed races scored?
Each full lap recorded at or before that race’s cutoff counts. More laps place higher. With equal lap totals, the runner who completed their last counted lap in less elapsed time places higher. Men’s and women’s places are calculated for each race.
What happens when an entry is late?
The app records the time when you submit the bib. Entries after the timed-race cutoff are saved for review and excluded from standings. An operator can accept a crossing using its observed time within the race window or reject it, with a reason and an audit record.
Can I correct a missed or duplicate lap?
Yes. Entering the same bib within 60 seconds asks for confirmation. Use Corrections for an earlier missed crossing so its observed time is preserved. Undo Last on the Timer screen follows the latest operator action across races.
Does timing need an internet connection?
Race timing and local storage work offline. Internet access may be needed to install the beta, send feedback, or share a file through an online service. Rehearse offline operation before an event.
Do multiple phones share one live race?
Each installation keeps its own race data. DB Timer currently has no shared live meet or automatic synchronization between timers’ phones. Coordinate a primary timer and an independent backup log.
Can I export results?
Yes. CSV export includes participant details, counted lap totals, elapsed time, and overall and gender places. Pending cutoff entries need review before they can affect results. Canonical backups preserve the stored timing history and audit information.
Does the first pass at the start count as a lap?
Enter a bib after the runner completes a full lap. Entering everyone as they leave the start would credit an extra lap. Start the race clock with the group’s actual start.
How does DB Timer protect race data?
Starts and accepted crossings are saved locally before success feedback. The app includes backup, recovery, and audited correction tools. Keep a separate line log during beta tests and review the privacy policy for data handling.
No matching questions. Try a different term or contact support.