MileClerk

Field results

Every statement MileClerk makes about how well it records drives traces to this page. If a figure is not here, we have not measured it, and we will not claim it.

What this dataset is

Read this before the figures. A rate without its denominator is not a measurement.

Real drives over one mile
Not yet published
Drivers
Not yet published
Phone models
Not yet published
Period covered
Not yet published
Engine version
Not yet published
App build
Not yet published
Generated
Not yet published

There are no measured results yet

No drive has been recorded, replayed and tallied, so there is nothing here to show. This page is live and empty on purpose: it exists before the numbers do, so that the numbers cannot appear anywhere else first.

Measuring how well MileClerk records drives takes real journeys in real cars, and road time cannot be hurried. When the first tally is published it will appear here, marked provisional, with its counts, the phones it was measured on, and every drive that was missed.

Every drive we missed

Misses are listed, never hidden. A capture rate published without them would not be a result. Each cause is an enumerated value chosen by our test team from a fixed list — there is no free-text field here, so a miss cannot carry a street, a place or a time.

No misses have been recorded. With no drives tallied yet, that is an empty list rather than a perfect score.

What these results do not show

There are no results here yet. When there are, the first of them will come from one driver, one car and one phone model over a few days of driving in the United Kingdom, and will be marked provisional until they cover at least 500 qualifying drives across at least five phone models. A provisional figure describes those drives and nothing wider.

Notes

No results published yet. The recording library is empty: the recorder build reaches the operator's phone on 27 November 2026 and the first field tally follows it.

How these figures are produced

  • Real drives are recorded on a real phone, and what actually happened on each one is written down at the time.
  • Those recordings are replayed through the same detector that runs on the phone. The same recording always gives the same trips.
  • The tally compares the detector's trips against the notes of what really happened. It is produced by our test team, not by whoever wrote the detector.
  • This page renders that tally directly from the published file. It cannot show a figure the file does not contain, and the build fails if it tries.

MileClerk keeps a record of your drives. It is not tax advice, and nothing here is a promise that any record will be accepted by a tax authority or an employer.