RevDash
OBD-II dashboard & trip replay
Every drive recorded. Every parameter replayable.
RevDash turns a plug-in ELM327 adapter into a live dashboard on your Android phone — then keeps each trip so you can replay it on a map and see exactly what the engine was doing, second by second. Nothing leaves the phone until you ask it to.
Free for 20 trips a month. No card to look around.
How it works
An adapter, a phone, and a browser.
There is no box to fit, no subscription hardware and no tracker wired into the loom. The parts are an adapter you can buy anywhere and a phone you already own.
Plug in the adapter
Any ELM327-compatible Bluetooth adapter, Classic or BLE. RevDash binds it to a vehicle profile and remembers the protocol, so every connection after the first is one tap.
Drive
Live gauges keep polling with the screen off. Every reading — plus GPS, if you granted location — goes into a trip stored on the phone.
Replay it anywhere
Sign in and tap Upload. Open the trip in any browser: the route on a map, coloured by whichever parameter you want to look at, with the charts locked to it.
In the car
A dashboard that explains itself.
Most OBD apps fail in the car park with a spinner and no reason. RevDash tells “couldn’t reach the adapter” apart from “adapter fine, no ECU answering” — and says which one it hit.
-
Live gaugesRPM, speed, coolant, throttle, load, battery voltage, and whatever else in Mode 01 your ECU actually answers.
-
VAG extras over Mode 22Oil temperature, charge pressure actual and specified, torque, lambda, timing, rail pressure and wastegate, when a VW, Audi, SEAT or Škoda answers.
-
A dash you arrangeAdd, remove, drag and resize tiles. Each vehicle profile keeps its own layout — and its own adapter.
-
Check-engine, done carefullyStored, pending and permanent codes with freeze frame and generic SAE titles — and a clear that asks before it does anything.
-
Estimated gearDerived from RPM and speed, so it works on a manual as well as an automatic.
Android 8.0 or later. Needs an ELM327 adapter and a car that speaks generic OBD-II.
In the browser
The drive, not a summary of it.
A trip log is a wall of numbers. The replay puts those numbers back where they happened, so a reading you noticed becomes a corner you remember.
The route on a real map
Your drive drawn over a greyscale basemap — served from the same machine as the page, not from a tile vendor.
Colour it by anything
Speed, coolant, boost, load — pick a parameter and the route is coloured by it, with a legend and its real range.
Charts locked to the map
Scrub the trip and the marker follows. Brush a range on a chart and every chart zooms to it together.
Play it back
1×, 4×, 16× or 60×, so a commute takes a minute and a track session takes as long as it needs.
Every value, downloadable
Full-resolution CSV of the whole trip, whenever you want it. It is your data and it leaves in a format anything can open.
Works without a basemap
No map installed, or a drive with no GPS fix? The trip still opens, the charts still draw, and the page says why.
Privacy
The map doesn’t phone home.
Almost every trip replay draws your route on somebody else’s tiles. That hands a company you have never dealt with a list of the roads you drive, the times you drive them, and the address you set off from — because a tile request is a request like any other, and it carries where you are looking.
RevDash serves its own map. The libraries, the fonts and the basemap all come from the same server as the page, so opening a trip makes no third-party request at all.
-
Nothing uploads on its ownRecording is local. Trips leave the phone only after you sign in and tap Upload.
-
No GPS permission, no GPS columnsLocation is optional. Without it you still get every reading the ECU gave you — just no route.
-
Share links are capabilities, and they expireA link carries a 256-bit token, stored only as a hash, and it stops working on its own. A wrong token is indistinguishable from a missing one.
-
Delete means deleteClose the account and the sessions die at once, the address is freed, and the stored telemetry is swept rather than quietly kept.
-
No ads, everThere is no ad network in the app and none on this page. The paid tier is the business model.
Pricing
Free to use. Pro when you outgrow it.
The app itself is free and works with no account at all. An account only matters when you want trips off the phone.
Free
No card required
- The whole app: gauges, codes, charts, layouts, CSV export
- 20 trips a month uploaded and replayable
- 30 days of trip history
- Full-resolution CSV download
Pro
Everything in FreePricing announced at launch
- Unlimited trips — no monthly cap
- Kept indefinitely — nothing ages out at 30 days
- Share a drive by link — expiring, and it shows the drive without naming the car
- Supports a product with no ads and no data sales
Upgrade from inside your account, so the subscription attaches to the right one.
Honest limits
What RevDash doesn’t do.
Generic OBD-II is a narrow window into the car — mostly powertrain, and only what the ECU volunteers. Anyone promising more than this over a cheap adapter is selling something.
- It does not read ABS, airbag or body modules. Generic OBD-II does not expose them.
- It does not write to the ECU or run actuator tests. It reads, and it clears codes when you confirm.
- It is not a shop scan tool, and it is not affiliated with any vehicle manufacturer.
- It is not Torque, and it uses no Torque branding or plugins.
- There is no iPhone app. ELM327 adapters are Bluetooth Classic or BLE, and the app is Android only.
Questions
Before you buy an adapter.
Which adapter should I get?
Any ELM327-compatible Bluetooth adapter, Classic or BLE. There is no approved-hardware list and nothing to unlock — RevDash binds whichever adapter you pair to a vehicle profile and remembers its protocol. Wi-Fi adapters are not supported.
Will it work on my car?
If the car speaks generic OBD-II on the powertrain — broadly, petrol from 2001 and diesel from 2004 in the EU, and 1996 onward in the US — you will get the standard Mode 01 readings. Which ones depends entirely on what your ECU answers, and RevDash shows you the ones it actually got rather than inventing the rest. VW, Audi, SEAT and Škoda additionally answer Mode 22, which is where oil temperature and charge pressure come from.
Do I need an account?
Not for the app. Gauges, codes, charts, layouts and CSV export all work with no account and no network. An account only exists so trips can leave the phone and be replayed in a browser.
What actually gets uploaded?
The trip: the OBD readings you recorded and, if you granted location, the GPS columns alongside them. It happens when you sign in and tap Upload, not in the background and not on its own. Telemetry goes straight to storage and is never readable by anyone holding just your trip list.
Can I get my data out?
Yes — full-resolution CSV, every value, from the replay page, on the free tier as well as Pro. The trip log on the phone is a CSV too. Nothing here is a format you need RevDash to read.
What happens when I hit the free limit?
Uploads for that month stop at 20 trips and the app tells you so. Recording carries on regardless — the cap is on what goes to the cloud, never on what your phone will capture. Trips older than 30 days age out of the free tier.
Is my route sent to a map provider?
No. The basemap is served from the same machine as the rest of the page, which is why coverage is a deployment decision rather than infinite. Opening a trip makes no third-party request of any kind — no script, no font, no tile.
Find out what your car has been doing.
Plug in an adapter, drive, and look at the whole thing afterwards.