Modern race timing,
reimagined.
A state-of-the-art platform for event organizers. From local 5Ks to international marathons, we deliver precision timing, athlete engagement, and an open hardware integration path.
Choose your scale
Our platform scales with your event, providing the right tools for every organizer.
The Basic Offer
Perfect for small organizers who want to run their own operations with minimal training.
- Mobile interface for manual timing
- Rented RTS hardware and chips
- Simplified race-day workflows
- Guided operator experience
Traditional Timing
Professional timing executed by RTS or a certified partner. Full on-site support for your race day.
- Full RTS-managed timing team
- On-site hardware and infrastructure
- Live results and leaderboard
- Race-day exception handling
Premium Managed
For larger event portfolios requiring deep automation, reporting, and full brand control.
- Advanced race-day controls
- Custom branding and domains
- Role-based team operations
- Automated results and communications
Hardware and Integrations
RTS hardware comes first, but the platform is designed as an integration layer across the main timing ecosystems. RTS ChipTime supports both proprietary RTS workflows and the major race timing hardware families used across the market.
Supported Hardware
- RTS timing boxes and the RTS bridge workflow
- MYLAPS hardware and MYLAPS decoder integrations
- IPICO hardware and IPICO reader integrations
- RACE RESULT decoders and host-feed integrations
- Impinj reader support for direct UHF timing deployments
- Zebra reader support for fixed-reader timing and checkpoint capture
- Multi-format reader emulation for testing, validation, and deployment prep
Unified Integration Layer
- One canonical ingest model for decoders, bridges, and direct reader connections
- Support for mixed hardware deployments within the same operational platform
- Unified live timing, rebuild, audit, and exception handling across hardware types
- Bridge applications, emulator tooling, and direct-reader support in the same workflow
One ingest model
Whatever the hardware path, the platform is normalizing reads into one operational timing model for live results, audit trails, rebuilds, and race-day exception handling.
Hardware Ecosystem
RTS Hardware
The RTS Reader
The RTS Reader is built for fast deployment, stable field operation, and clean integration into RTS ChipTime. It is designed for start, split, and finish deployments with a workflow that fits both managed and self-service events.
Territory Pricing
Select the pricing territory to switch the website between UK, EU, and US list pricing.
All prices shown are ex VAT.
Designed For The Field
Rugged reader workflow for temporary timing points, race-day setup, and live pass-through into the timing platform.
Live Platform Sync
Supports live read relay into RTS ChipTime for monitoring, rebuilds, audit visibility, and public result updates.
Typical Rental Use
Use RTS Readers at start, finish, and selected splits. Add more readers as course complexity increases, or move to a managed deployment where RTS handles the full timing layout and race-day operation.
Buy Your Own Reader
For organisers and partners building their own hardware fleet, RTS Readers are also available for direct purchase. Purchase pricing is quoted based on quantity, deployment model, and support requirements.
Software and Hardware
Software use is included when you buy single-use chips from RTS. Larger managed and enterprise hardware deployments are quoted against course layout, timing density, and event duration.
Chip Pricing
We can run online registration against the organiser's own merchant account with Stripe, PayPal, and SumUp.
API Backbone
Production-grade engine and scalable API for AI-built race apps
Your team can use AI to build any custom UI, portal, or workflow. RTS ChipTime provides the production-grade ingest, timing logic, live results, and messaging engine, plus a realistic replay sandbox development environment, so you ship faster without rebuilding race-critical infrastructure.
Live Results API
Serve official and provisional results to apps, websites, media partners, and on-site screens in real time.
Messaging Channels
Trigger SMS, WhatsApp, email, and custom in-app push notifications from split milestones, cutoffs, and race-day rules.
GDPR Controls
Consent flags, preference checks, and suppression controls are enforced so messaging pipelines remain GDPR-ready.
Goal Funnels
Define engagement funnels with goals like app opens, live tracking opt-ins, and result shares, then optimize from conversion metrics.
Replay Sandbox
Test AI-generated interfaces against realistic replay traffic over HTTP or TCP emulation before race day, then promote to production with the same API contracts.
AI-Ready API Client
Drop the RTS API client into Claude or Codex so the model understands available endpoints and quickly pulls the right race data into your generated UI flows.
ops-terminal
$ git clone https://github.com/rtschiptime/ops-template.git
$ cd ops-template && git checkout production
$ git pull --ff-only origin production
Already up to date.
$ npm run live-mobile-messaging -- --event city-classic-2026
[messaging] worker started (event=city-classic-2026, channels=whatsapp,sms,custom-app)
[split] bib 2481 | race=HM | split=30K | elapsed=01:42:18 | rank=17
[gdpr] consent_ok athlete=2481 | channel=custom-app | policy=eu-gdpr
[push] template=split_alert | athlete=2481 | provider=custom-app | queue=accepted
[funnel] goal=live_tracking_opt_in | athlete=2481 | stage=opened_to_tracking
$ curl -sS "https://api.rtschiptime.com/v1/events/city-classic-2026/live/results?race=10K"
-H "Authorization: Bearer rts_live_demo_xxxxxxxxx"
{ "event":"city-classic-2026", "race":"10K", "leader":"A. Ndlovu", "status":"live" }
$ curl -sS -X POST "https://api.rtschiptime.com/v1/events/city-classic-2026/messages/push"
-H "Authorization: Bearer rts_live_demo_xxxxxxxxx"
-H "Content-Type: application/json"
-d '{"channel":"custom-app","goal":"live_tracking_opt_in","template":"split_alert","trigger":"30K_passed"}'
{ "queued": 8421, "provider":"custom-app", "delivery":"accepted" }
AI Build Mode
Vibe code your UI, plug into the RTS engine
prompt> Build a race director dashboard with live leader card, split alerts, and push controls for event city-classic-2026.
ai-setup: attach RTS API client in Claude/Codex and load event-scoped token
generated.sh: npm run replay:city-classic:loop -- --once --event city-classic-2026
generated.jsx: useEffect(() => fetch("https://api.rtschiptime.com/v1/events/city-classic-2026/live/results?race=10K", { headers: { Authorization: "Bearer rts_live_demo_xxxxxxxxx" } }))
generated.jsx: POST /v1/events/city-classic-2026/messages/push {"channel":"custom-app","template":"split_alert","trigger":"30K_passed"}
runtime: 200 OK | leaders synced in 280ms | 8,421 notifications queued
Keep the UI fully yours. Keep the timing engine, ingest reliability, and compliance controls production-safe on RTS.
RaceOps Intelligence
Custom race timing control with real-time issue response
Our custom race timing software continuously highlights configuration gaps and live timing anomalies, including missing start states, unexpected chip reads, unpublished leaders, and checkpoint drift.
The system then suggests operational fixes for race control and can execute approved updates directly through the API, so teams can correct timing logic without leaving their workflow.
- Highlights config and real-time race timing issues as they happen.
- Suggests safe, context-aware corrections before applying them.
- Performs approved changes through API endpoints with audit visibility.
Telegram
RTS RaceOps Agent
