Timing

made simple

Professional Timing Made Simple

You want to time multiple things at once without losing track of what belongs to who, or missing what's actually happening because you're fighting with your timing tool.

Most stopwatches are built for the simplest case: one timer, start/stop/reset. The native stopwatch on your smartphone works fine for timing a single thing. But real timing is messier.

You're tracking different people, recording various types of splits, dealing with things happening simultaneously. The gap between basic phone stopwatches and expensive enterprise timing systems leaves most people stuck with tools that don't fit how timing actually works.

This is a stopwatch app designed for that reality. It runs multiple independent timers, works offline, keeps your data local, and gets out of your way so you can focus on what's happening instead of wrestling with your timing tool.

What it
actually
does

Core function

Multiple Independent Timers

Run as many stopwatches as you need simultaneously
Copy a running timer to start timing someone else mid-race
Each timer keeps its own splits and history
Name your timers so you know which is which
Group related timers together for easy management

organization

Organization That Makes Sense

Name your timers with runner names, event types, or whatever makes sense for your situation
Group related timers together by event, team, session, or any way that helps you stay organized
Archive old sessions to keep current ones clean and focused
Search through your timing history when you need to reference past data

Timing

Timing Features You'll Actually Use

Record splits during races without stopping the main timer
Add lap markers for track events to keep track of distance and pacing
Note events and measurements as they happen
Add timestamps for specific moments you want to remember
Review timing patterns and trends from your sessions

Advanced

Advanced Group Management

Set up timing groups for different scenarios - parallel starts for races, sequential handoffs for relays, or independent timing for general use
The app understands different timing contexts and provides relevant tools for each
Bulk operations for starting, stopping, or managing multiple timers at once

Built for
real conditions

Works offline

Your data lives on your device, not in the cloud. Whether there's no internet, or no cell service, it will continue to work just as it always does.

Battery Conscious

Designed to not drain your phone during long meets or training sessions. The app has been used for 5+ hour events without noticeable battery impact beyond normal usage.

Actually reliable

Your timing data isn't tied to keeping a browser window open or staying in the app. The underlying timing mechanism ensures accuracy regardless of what else you do with your device.

Responsive interface

Works on phones, tablets, laptops. Touch or mouse. Portrait or landscape. The interface adapts to your device and how you're using it.

Privacy by design

No accounts required, no personal data collection. Everything happens on your device. Your timing data never leaves your browser. I track feature usage to see what's getting used versus what is ignored, but that's all anonymous.

This might help if...

You want to time multiple things while staying present for what's happening.

Track & Field and Cross Country

Coaches timing multiple runners, recording splits at different distances, tracking training progress over time.

Research and Data Collection

Precise timing for experiments, observations, or any situation where you need accurate time measurements for multiple subjects or processes.

Work and Manufacturing

Teams tracking completion rates, process timing, quality control intervals, or any workplace timing needs.

General Multi-Timing

Anyone juggling multiple processes where precise timing matters - cooking multiple dishes, study sessions, project work, or any situation where you need more than one timer running.

Free to use

Your data stays yours. No subscriptions, no accounts, no data sent to servers.

For more details about how and why this works the way it does, .