How to measure your 0-60 time accurately with a phone

First: where you are allowed to do this

Accelerating as hard as your car will go is not a public-road activity. It is illegal in most places, and the failure modes involve other people. Before anything technical:

• A legal drag strip. Test-and-tune nights are cheap and the surface is prepared for exactly this.
• A closed circuit or track day. Many run open pit-lane sessions.
• Private property, with the owner's permission, and enough clear run-off to stop calmly.

You need more room than you think. Getting to 60 mph is only half of it — you then have to slow down again, without drama, with margin. Plan the stopping distance before the launch, not during it.

Setting the phone up

Mount it, do not hold it

A phone sliding across a passenger seat is measuring its own journey, not the car's. Any movement relative to the car shows up in the accelerometer as acceleration that never happened. A cheap vent or windscreen mount removes an entire category of error.

A good timing app should not care which way the phone is facing — needing a specific orientation is a limitation of the app, not a law of physics. But it does need to stay put.

Give the GPS time

The first satellite fix after opening an app is the slowest and the worst. Go outside, away from buildings and dense tree cover, and give it 30 to 60 seconds before you expect a solid signal. Underground car parks, tunnels and tall city streets are the worst possible starting points.

If your app shows a GPS readiness indicator, wait for it. Arming on a marginal signal is how you get a time that looks precise to three decimal places and is quietly wrong.

Reduce what else the phone is doing

Timing is real-time work. A phone that is thermally throttled, on 3% battery, or busy uploading photos has less to give. Plug it in, close what you do not need, and if it has been sitting in direct sun on a hot day, let it cool first.

Record the conditions, every single time

This is the step people skip, and it is the one that makes the data worth keeping. The same car on the same day can produce meaningfully different times depending on:

If your app records weather and elevation automatically, that is one less thing to forget. If it also computes a corrected time for standard conditions, that is what lets you compare a run from a cold January morning against one from an August afternoon without fooling yourself.

The run itself

1. Come to a complete stop. Not rolling slowly. Fully stopped. The clock has to start from a known zero.
2. Wait for the app to arm. If it refuses, that is the app protecting your data, not malfunctioning.
3. Do not creep. Easing forward before the real launch is the single most common way to invalidate a run. A good app detects it and throws the run away.
4. Launch the way you actually drive. If you are measuring the car, be consistent. If you are practising launches, that is a different exercise — do not mix the two in the same dataset.
5. Hold it past the target. Lifting exactly at 60 makes the last fraction ambiguous. Carry on a moment longer, then slow down normally.
6. Let things cool between runs. Back-to-back pulls heat the intake, the brakes and often the tyres. Three rushed runs are worth less than three spaced ones.

How many runs, and which number to keep

Three valid runs is the minimum, five is better. One run tells you almost nothing: a single good or bad launch moves a 0-60 by more than most bolt-on modifications ever will.

The interesting output is not your best time. It is the spread between your runs. Three runs within a tenth of each other means your procedure is sound and the number means something. Three runs spread across half a second means you are measuring your right foot, and no conclusion about the car survives that.

Quote your best if you like — everyone does. But keep the spread next to it, because that is the part that tells you whether to believe the best.

Why your time is slower than the brochure

This is the question behind most of the frustration, so here it is plainly. Published figures and your figures are not measuring the same thing.

• Rollout. Many published US figures use the drag-strip convention of starting the clock about one foot into the run, after the car is already moving. It typically removes a couple of tenths from a 0-60. Most phone apps, including this one, measure from a true standstill — a stricter, slower, more honest start.
• A prepared surface. Test venues have grip that a normal road does not.
• A professional launch. Someone whose job is extracting the best possible start, with as many attempts as it takes, on a car they are not paying to repair.
• Optimal conditions. Low elevation, favourable temperature, minimal fuel, one occupant, nothing in the boot.
• Your car has lived. Tyres wear, fluids age, the clutch is not new.

None of this means your number is wrong. It means the two numbers answer different questions. Yours answers what does my car do, as it is, with me driving — which is the more useful question, and the only one you can improve.

Five mistakes that quietly ruin the data

1. Comparing runs from different days without recording conditions. The most common one by a distance.
2. Always running the same direction on a road with a gradient. You may be measuring the hill.
3. Judging a modification on one run before and one run after. That is not a comparison, it is a coincidence.
4. Letting the phone move. Pockets and seats add motion that was never the car's.
5. Keeping the runs that felt bad. A false start or a run with a poor GPS fix belongs in the bin, not in the average.

Disclosure: this article is published by the developer of Drag Race & 0-60 Performance Timer. The procedure above works with any competent timing tool; nothing here is specific to this app except where stated. No affiliate links.