Every figure, and how it is made.

Five kinds of day

Every day on the Record is one of these. A day is never left blank, and never filled with a zero it did not earn. The word for a day the car stays parked is the one a training log uses: a rest day.

• Driven day 38 on the record

  The car drove, and TezLab recorded every drive.

  How it is decided TezLab holds at least one drive for the day, and the drives add up to TezLab's own total for the day.

  What stands behind it The drives, TezLab's day total, a TezLab charge session, and a Tesla invoice on a day the car used a Supercharger.

• Rest day 3 on the record

  The car did not move.

  How it is decided TezLab recorded no drive. The battery read within three points when the car was last parked and when it next moved, no charge fell between, and where the odometer was read on both sides it read the same.

  What stands behind it Neither source has anything to record on a day the car stays put, so the quiet is the evidence, and the battery and the odometer have to agree. It is a day on the record with zero miles, never a gap.

• Charge-only day 2 on the record

  Before the drive record began, Tesla billed a charge.

  How it is decided The day is before TezLab's first drive, and a Tesla invoice shows a Supercharger session.

  What stands behind it A Supercharger takes a drive to reach, so the car was driven. How far is not known, so no miles are shown and the charging is not counted in the totals.

• Open day none yet

  The day is not over, so its figures are so far.

  How it is decided Today, or a day TezLab has not yet closed with its own total. The miles are the drives recorded so far.

  What stands behind it Efficiency, charging and idle loss arrive when the day closes. An open day is never averaged and never compared with whole days.

• No car record none yet

  The apps counted the day; the car's record has not arrived.

  How it is decided A day with income or an app's workload and nothing from the car yet.

  What stands behind it A gap, never a zero: no miles are printed until the car's own record covers the day.

On the calendar

• Driven, darker is more miles
• Driven, with income logged
• Rest day
• Charge-only day
• Open day, so far
• Not on the record: a gap, never a zero

Miles, by purpose

The purpose of a mile decides what it is counted against. So a mile is called a gig mile only when an app counted it, and a mile is placed in the apps’ hours only when the hours cover it. Three counts, each by who counted it, and a fourth for what is not known. Today 9 days on the Record had delivery work: the apps’ miles are in for 4 of them and the hours for 6.

• Counted by the appsThe apps’ own miles. Uber Eats adds each delivery’s distance. Instacart adds each batch’s route, from where the car was to the store and from the store to the customer. Two deliveries made together are each counted in full, so an app can count more than the road, and then the road is used.
• Driven in the apps’ hours, not counted by themThe car’s own miles from the first delivery’s start to the last one’s end, less the apps’ count: the way to the first pickup, between deliveries, back, a charge stop. Worked out from two measured figures, and never below zero.
• Outside the apps’ hoursThe rest of that day’s miles. No app counted them, and the Record does not say why: a drive for Paddock20 or PaddockGavin, an errand, a charge. It is never called personal and never called business.
• Not splitA gig day whose apps’ miles or hours were not given. Its miles are the car’s, some of them gig miles and some not, and the Record does not guess. No per-mile figure is printed for a count it does not have.

The hours are the ones the apps list, from the first delivery to the last. Where only one app’s hours were given on a day with two, the other app’s miles stay in “not split”. Money is divided only by the miles of the same lines, and a bonus is left out.

How a figure is marked

Every figure says where it comes from. The mark is beside it, so it can be checked and never has to be taken on trust.

• measuredFrom the car, a document or an app's own screen: a drive, a Tesla invoice, the delivery app's count.
• modeledWorked out from measured figures, and the page says how: energy for the miles, what was kept after it.
• statedThe owner's word, with no document behind it.
• photoA photograph from that day.
• so farThe day is still open: these are the drives recorded up to the last pull, and the day closes with TezLab’s own total.

Money, by its state

• paidThe cash is in.
• invoicedBilled, and not yet paid.
• pendingCredited by the platform; the cash is not yet confirmed in. A gig week's pay can still change until it closes.
• bookedAgreed and not yet earned. Never added to earned.

earned = paid + invoiced + pending. Booked work is shown beside it and is never part of it.

What is tracked

TezLab records every drive and charge. The Tesla Fleet API records only what Tesla bills, and the car’s state when it is already awake; it never wakes the car.

The arithmetic

Every figure that is worked out is worked out one of these ways, and nothing else.

Self-driving share

FSD miles ÷ miles drivenOver a week, a month or a year it is the total FSD miles over the total miles, so a long day counts for more than a short one.

Cost per mile

charging spend ÷ miles driven, now 13.1¢From Tesla’s invoices over the whole window, parked and idle energy included.

Energy for the miles

miles × cost per mileWorked out, not metered. Marked as such.

Made per mile the apps counted

money on the lines the app counted miles for ÷ those milesA bonus has no miles and is left out. Uber Eats and Instacart each count in their own way, and the figure is over the lines that have the count.

Made per mile in the hours

money on the lines with hours ÷ the car’s miles in those hoursEvery drive from the first delivery to the last, so it carries the way to the first pickup and the miles between deliveries.

Kept per mile

(money − energy for the miles) ÷ the car’s miles in the hoursWorked out. It is not profit: the car, its insurance and the owner’s time are not in it.

Made for each dollar of energy

money ÷ energy for the milesWorked out, at the measured cost per mile.

Efficiency in the hours

the energy the miles would take at the rated figure ÷ the energy they tookTezLab’s own ratio, each drive weighted by its energy, so a short wasteful drive does not count like a long one.

Overhead

the car’s miles in the hours − the apps’ count, never below zeroThe way to the first pickup, between deliveries, back, a charge stop.

Outside the hours

the car’s miles that day − the car’s miles in the hoursOnly on a day where the hours cover every line the apps list.

Made per hour

money ÷ hoursThe owner’s hours, else the delivery app’s active clock.

Work per driving hour

(delivery hours + brand hours done during drives) ÷ hours the car droveThe work is done during the drive, so the two overlap and the figure can pass 1.

Earned

paid + invoiced + pendingBooked is never added.

A window

the part of each drive inside the hours givenA drive that straddles the edge of a window counts for the minutes of it inside.

Calendar

weeks run Sunday to Saturday; seasons are meteorologicalWinter is December to February, spring March to May, summer June to August, fall September to November.

How each day is proved

Two sources feed the Record, and they are not alike. TezLab records every drive and charge. The Tesla Fleet API records only what Tesla bills. A day with a drive is known from TezLab; a Supercharger day is known from both; a day the car does not move is known from neither, because there is nothing to record. For that quiet to count, something independent has to agree with it.

• TezLab’s drives and its day totals. The drives for a day must add up to TezLab’s own total for the day.
• The battery. Between two drives the battery cannot rise unless a charge is on record, a charge must end where the next drive starts, and a parked car cannot lose more than idle drain explains.
• Tesla’s invoices. Each Supercharger invoice must have a TezLab charge session, and a drive on its day.
• The odometer. The car’s own odometer, read at the start of a day’s first drive and the end of its last, must equal the drives. It must not move between one day’s end and the next day’s start: if it did, a drive was never recorded.

Last checked October 4, 2026: 44 days since delivery, 38 driven, 3 rest, 2 charge-only, and 1 before either source existed.

Route logic

The Record never shows where the car goes. The map on Drive shows city to city and nothing finer, by four steps that run the same way every time.

1. A drive

   One trip each time the car moves, as TezLab records it.

2. A pair of cities

   The two cities at its ends, in no order: one city to another counts the same as the way back. A drive inside one city is counted apart.

3. A place check

   Only a city the Drive page already draws may appear. A drive that touches any other place is counted and left out, because a regular stop at neighborhood level is a home and work pattern.

4. A tally

   Trips and miles for each pair, most trips first and, among equals, the most recent first. A line on the map is as thick as its trips over the busiest pair’s.

An average on the corridor table is its miles over its trips. Coordinates, addresses, the time a drive began and the weekday are never computed or kept on a page.

How a number is made

1. 1

   Pull

   TezLab’s drives, charges and day totals; Tesla’s invoices; the car’s odometer.

2. 2

   Load

   Into the warehouse, refusing what cannot be true: an odometer that runs backwards, energy above the pack, a day total the drives do not support.

3. 3

   Reconcile

   Invoices against sessions, drives against totals, the battery chain, the odometer sum. Every day is classed and proved or named a gap.

4. 4

   Build

   The pages are written from that data and nothing else.

5. 5

   Gate

   Every page is checked before it ships: no address, no private coordinate, no private name, no dead link, and on the Record no clock time and no dollar figure the owner did not choose to publish. A failure stops the build.

6. 6

   Publish

   A published figure that changes later needs a dated correction, shown on its day.

What is never shown

• Where the car goes, where it sleeps, or when it leaves.
• An address, a coordinate, a store or restaurant, a drop-off street.
• A clock time. The Record carries durations only.
• A client’s name, or the owner’s legal name.
• A weekday pattern, a streak counter, or where it charges.