Charge log
Every session, from plug-in to unplug, with the numbers that make cost comparisons honest.
- Start and end state of charge
- kWh added, price paid, idle fees
- Location, network and connector
In development Personal iOS journal · Not a Tesla product
RangeLendger keeps charging sessions, trips, efficiency and service history in one place on your phone. You write the entries. Nobody else gets a copy.
Design illustration of the journal layout. The iOS app is in private development — this is not a screenshot of a shipped build.
What it records
What did that road trip really cost? Is the pack behaving the same as last winter? When was the cabin filter changed? One journal, four kinds of entry, no screenshots from three other apps.
Every session, from plug-in to unplug, with the numbers that make cost comparisons honest.
Distance with the context that explains it, so a bad efficiency day has a reason attached.
Trends calculated from your own entries — not an estimate borrowed from someone else's fleet.
Maintenance that stays findable years later, instead of scattered across texts and receipts.
How it works
No sync queue, no onboarding funnel, no dashboard you have to log into. The whole loop takes about twenty seconds per entry.
Finish a charge, park after a trip, or leave the service centre, then add the entry in a few taps. The app opens to a form, not a sign-in screen.
RangeLendger does the arithmetic: Wh per mile, cost per mile, kWh per session, and how this winter compares to the last one you logged.
Entries live in the app's on-device store and travel with your normal encrypted device backup. Export a copy whenever you want one elsewhere.
If an official manufacturer owner API is ever wired in, it is opt-in, authorised on the manufacturer's own sign-in screen, scoped by you, and revocable there at any time.
Trust
A journal about where you drive, when you charge and what you spend is sensitive by definition. So the design starts from the assumption that the data never needs to leave your phone.
FAQ
No. RangeLendger is an independent personal project and is not affiliated with, endorsed by or sponsored by Tesla, Inc. Tesla, Model 3 and related marks belong to Tesla, Inc. and are used here only to describe the vehicle the journal was written for.
No. There is no remote command surface of any kind. RangeLendger cannot lock, unlock, precondition, honk, open a port or move a vehicle. It records entries you type in.
In the app's own on-device store on your iPhone, and in whatever encrypted device backup you already use. This website has no accounts, no database and no login, so there is nothing here to breach.
That is the point of a journal. The design goal is a plain, readable export you can open in a spreadsheet, so your history is never trapped in someone else's format — including this one.
/oauth/callback page for?It is the registered redirect target for a possible future authorisation-code sign-in with an official manufacturer owner API. Today it only reports whether an authorisation succeeded or failed. It stores nothing and holds no secrets — this is a static site with no backend.
Nowhere yet, and there is no waitlist or beta to sign up for. RangeLendger is in private development for one owner's car — a 2018 Model 3 Performance — and this site exists so the project has a real home, a real privacy policy and the developer endpoints a manufacturer review expects.
No growth targets, no telemetry pipeline, no data room. Just a careful record of what a single EV costs to run, and a public paper trail describing exactly what the app does and does not do with it.