Trips
A trip log that fills itself in
You get in, you drive, you switch off. The trip is recorded, split, drawn on a map and filed in your history, without anyone asking you to press anything.
Included
What a trip log is actually for
A trip log serves three purposes. Claiming mileage first: tax authorities want dates, distances and reasons, and nobody enjoys reconstructing those in April from memory. Finding a route again, second: the back road taken last summer, the car park found at the last minute, the station where charging was cheap.
Understanding how the car is really used, third. A Tesla's odometer says how many miles it has covered. It does not say when, or where to, or how many times you made that same six-mile round trip that costs, added up, more than the annual holiday.
Splitting happens on our servers, not in the page
A trip has no start button. iCar receives a stream of positions and decides for itself where one begins and ends: a trip closes after fifteen minutes stopped, or fifteen minutes without data, or a jump of more than two miles between consecutive points. It resumes once the car has covered a hundred metres above three miles per hour.
That calculation runs server side, deliberately. A web page is reloaded, hidden and closed constantly: it cannot hold reliable state across a four-hour journey. The server does not lose the thread.
Two ways to record, and one has gaps
Without a subscription, position comes from the car's browser. It works well, with one limit that is not ours: a browser only reports location while it is on screen. Leave iCar to open Waze or a radio, and recording stops. We show those gaps as they are, and never draw a straight line between two distant points: an invented trip would be worse than an incomplete one.
With a subscription and a linked Tesla account, the car itself reports its position, continuously, whether iCar is on screen or not. The trip is then whole, from departure to arrival.
What you can do with it
Each trip opens on its map, with distance, duration and segments. From the car screen or from your phone: it is the same history, and it follows the account.
One button emails the trip as a GPX attachment, the format every mapping app reads. Not a summary along the lines of "2.5 miles in 20 minutes", which says nothing the screen did not already show: the full track, usable elsewhere.
What is stored, and what is not
Trip recording is the only place in iCar where a position is kept, and it has its own switch in account settings. Turned off, nothing is written: the server rechecks that setting on every batch and refuses the points, rather than trusting what the page claims.
A location history is the most intimate data a product like this can hold. It is never written to our technical logs, never shared, and every read is filtered by the account asking for it.
Ready to try? The bookmark grid is free, with no time limit.
Create my account