# Tripper GPS — GPS + motion ride logger

> GPS + motion ride logger (iPhone/iPad app by Koray Birand.)

- Source: https://appshunter.io/ios/app/tripper-gps/id6790212862 (this page in markdown: same URL + `.md`)
- Developer: [Koray Birand](https://appshunter.io/developer/1752915873)
- Category: Sports, Health & Fitness
- Price: Free
- Age rating: 4+
- Requires: iOS 26.0 · 13 MB
- Languages: American English
- Released: 2026-07-17
- Data updated: 2026-08-26
- User reviews in markdown: https://appshunter.io/ios/app/tripper-gps/id6790212862/reviews.md

## What is Tripper GPS?

Tripper turns your iPhone into a proper telemetry logger for motorcycles,
bicycles, and cars. Mount it, tap Start, and ride. Everything else is
recorded for you.

CALIBRATED TO YOUR BIKE, NOT YOUR PHONE

Most apps measure motion in the phone's frame, which is meaningless when the
phone is clamped to your bars at an angle. Tripper measures it in your
vehicle's frame. Tap Reset Angle once and the current orientation becomes
zero, so slope, lean, and g-force are read along the axes that actually
matter: forward, sideways, and up. Level ground reads 0 degrees no matter
how the phone sits in its mount.

WHAT IT RECORDS

• GPS route, speed, distance, and heading
• Barometric elevation, fused with GPS - far smoother than GPS altitude
alone, so real hills survive and noise does not
• Road grade, as a rolling window rather than jittery point-to-point noise
• Lean angle and slope in your vehicle's frame
• G-force: braking, acceleration, and cornering, measured in the horizontal
plane the way motorsport telemetry does, with the vertical jolts from
potholes filtered out instead of inflating your numbers
• Up to 100 Hz motion sampling, logged at the rate you choose

BUILT TO BE USED AT SPEED

The dashboard floats over a fullscreen map: big numbers, high contrast,
readable at a glance with gloves on. The controls are deliberately hard to
get wrong - a stray tap can never end your ride, because finishing is only
possible from a paused state.

It keeps recording with the screen locked, and you can pause, resume, or
drop a marker straight from the Dynamic Island and Lock Screen. Or from your
wrist: the Apple Watch app shows duration, speed, altitude, and your
position on the map, and lets you start, pause, and mark a ride without ever
touching the phone.

FOR VIDEO OVERLAYS

Drop a marker at any moment - a clap, a landmark, a starting gun - and it is
written into the data with an exact timestamp, so you can line the telemetry
up against your action-cam footage frame for frame. Exported CSV is shaped
for overlay tools like DashWare and Telemetry Overlay.

AFTER THE RIDE

• Replay any ride full-screen: scrub through it, or play it back and watch
the dashboard come alive over the map exactly as it was
• Speed and elevation charts, with distance, moving time, average and top
speed, elevation gain, and peak g
• Overlay past tracks on the live map and go and chase them
• Import rides from .trip, GPX, KML, or CSV
• Export full-telemetry CSV, GPX with telemetry extensions, or a compact
.trip archive

ENTIRELY YOURS

No account. No cloud. No analytics, no advertising, no third-party SDKs.
Every ride is processed and stored on your device, and nothing leaves it
unless you explicitly export or share it.


## Version history (last 5 releases)

### 1.9 — 2026-08-24

FIXED: The slope reading flickered between steep up and steep down while stopped on a hill
- Stopped on a 30-degree climb, the card alternated between about +65 and −54 per cent roughly once a second — 1115 swings between up and down in a single ride, and GPS Sync burned the flicker into the exported video
- Two unrelated things looked identical to the app. Slope deliberately withdraws a single reading when something jolts the bike, and a rider shifting their weight at a stop does exactly that. Every withdrawal handed the display back to the puck's motion chip — the very thing the app's own slope was built to replace, and upside-down on top of it (below)
- A withdrawal now falls back to the reading from a moment ago, up to four seconds old. It is a refusal to answer for this instant, not an absence of any answer, and the honest stand-in is what the same instrument said a second earlier
- The chip is used only when the app has never had a reading at all — a first-generation puck, or the first second of a fresh link

FIXED: The puck chip's own slope was upside-down
- Nose-up read as nose-down. The maths that turns the chip's reported orientation into an angle assumes one axis convention; the puck uses another, so pitch came out inverted
- Roll came through correctly, which is exactly why this hid for so long: half the attitude was right, and the wrong half was the half the app had already stopped using
- Measured against gravity over 4728 stopped rows — a still bike makes the accelerometer a true inclinometer, because there is no acceleration to confuse with tilt — the chip's pitch tracked the real angle at −0.98 times it. A clean sign flip, not a drift or a bias
- The app's own slope replaced this channel several versions ago, so it only ever showed through as the fallback above. It was also inverted in the pitch column of exported ride files, which is now correct

FIXED: A spinning wheel could throw the grade to 174 per cent
- Slope subtracts the bike's own acceleration before it reads gravity, because braking pushes you forward and an accelerometer cannot tell that from the bike tipping nose-down. That acceleration was taken from wheel speed
- On a loose climb the wheel spins: it reports 0 to 40 km/h and back while the bike has not moved. The app read that collapse as a full g of braking that never happened and drove the grade to 174 per cent — on a pitch the accelerometer itself was holding steady at 33 degrees
- The correction now applies only while the bike is genuinely rolling, and can never be larger than the jolt the accelerometer actually felt over the same instant. Real braking shows up there; a wheel spinning under a stationary bike does not
- Scored across four recorded rides against gravity at standstill: average error 1.32 down to 0.56 degrees, worst case 28.3 down to 11.6, and readings more than 5 degrees adrift fell from 6.6 per cent of rows to 1.3
- Removing the correction altogether scores better on the average and worse where it counts — one stop needs it and goes from 0.2 degrees of error to 21 without it — so it was fixed rather than dropped

FIXED: Slope ramped smoothly up from flat after a wheelspin spike
- Slope has two sources and blends across the handover so the number does not jump. It blended from zero whenever it had no current reading, which means it climbed smoothly out of an imaginary flat road: one spike bounced the source twice in three seconds and the reading ramped 0 to 33 degrees each time, looking for all the world like a hill arriving
- It now blends from the last real reading. Where there is no real reading to blend from, it steps straight to the measured one — a step onto something measured beats a smooth climb out of a number nobody measured

### 1.8 — 2026-08-19

- FIXED: slope read far too shallow on loose or steep climbs. 1.7 rebuilt it as height gained over ground covered, but took "ground covered" from the bike's speedometer — and a spinning wheel turns further than the bike travels. One ride's wheel read 152 per cent long through a climb. Distance now comes from GPS
- FIXED: short steep climbs read far gentler than they were. Slope was measured across 40 metres, a length sized for road gradients, so a technical climb got averaged in with the flat either side. It is now 10 metres: a true 24-degree climb used to read about 7 degrees and now reads about 17
- FIXED: braking read as downhill and accelerating as uphill. Hard speed changes shove the barometer by metres — a flat-road braking stretch read −11 per cent — so it is now ignored during them, and a blip from a gust can no longer spike the reading
- Slope without a puck now uses the phone's own barometer over GPS distance instead of how far the phone is tilted; it stays live below walking pace instead of freezing; it starts blank on a new ride rather than inheriting ground you rode before recording; and it runs about a second closer to real time
- FIXED: lean showed the wrong side — "Lean L" was really a lean to the right. Its two ingredients were wired with opposite sign conventions, which mirrored the label and made them fight through corner entries. All 27 corners across four rides now read correctly
- Lean also reads truthfully stopped or crawling now, from gravity — parked on the side stand it shows the real angle. The gyro's zero error is measured at every stop and subtracted instead of riding along as phantom lean, and lean uses the same corrected speed as slope
- FIXED: the g-force readings and max G still came from the faulty motion chip — one ride's hardest braking was recorded with the wrong sign. Rebuilt from the raw accelerometer and the app's own lean and slope: correlation against physics went from ~0 to +0.95
- FIXED: the Apple Watch and the Dynamic Island showed a different speed from the phone. They were still on GPS ground speed while the phone reads the bike's own wheel speed. All three now read one shared source
- GPS fixes worse than 20 m no longer feed distance, max speed or the wheel-scale learner — one 47 m fix implied 168 km/h. The learner also ignores any stretch below 15 km/h, because rolling to a stop used to teach it nonsense that carried into the next ride
- Switching the bike off before stopping the recording no longer writes garbage into the tail of the ride: a parked ride keeps its true values instead of recording the phone being handled as 68 degrees of lean
- Zero pitch & roll now also captures the mount's tilt, so stopped slope and crawling lean no longer carry it as a constant error — do it once after installing, sitting on the bike
- New Analytics button at the top of Rides totals your library over a timeframe you pick: distance, ride time, elevation, days ridden and best streak; energy, Wh/km, power, battery used and range per charge; lean, g and the eco/sport split; records that open the ride that set them; and charts of distance, efficiency and time of day
- Charge cycles are read from the gauge climbing between two rides — 34 per cent at the end of one and 88 at the start of the next is 54 per cent in. Calories are the watch's or nothing, so a range with phone-only rides says "from 6 of 11 rides"
- Ride details gained a Power & Energy card — watt-hours used, battery from→to, Wh/km, average and peak power and current — for every ride already in your library, plus active calories on watch rides
- Puck firmware: sensor updates now average all hundred readings a second instead of one in twenty, and new firmware flashes over the puck's own WiFi from Settings — no cable, no dismount
- Lean in rides recorded before this version carries the mirrored side letter; angle sizes are unaffected

### 1.7 — 2026-08-06

FIXED: Lean and slope were wrong, and are now rebuilt from scratch
- Lean could read 8 to 15 degrees on a dead-straight road and stay there for most of a ride. Parked upright it looked fine; the error only appeared once you were moving
- Slope had the same fault in the other axis: it could report a climb of over a degree while the road was visibly dropping, and three other sensors agreed it was dropping
- Both are now worked out from the puck's gyro, the bike's own wheel speed and the barometer, instead of from the motion chip's internal angle calculation — which was found to invent tilt that its own accelerometer contradicted at the same instant
- Measured across six recorded rides: lean on straight roads went from as much as 9.8 degrees off to within a degree, and on the worst ride the time spent reading more than 10 degrees of lean while travelling straight fell from 47 per cent of it to none
- Slope now agrees with GPS altitude where it used to disagree, and no longer reports grades no road has

What lean can and cannot show
- Lean is worked out from the turn you are making, so it shows how far the bike is over through a corner
- It does not show you shifting your weight, or the camber of a straight road, and it never will: a bike held in a steady corner feels gravity straight through itself, which is what stops it falling over. Nothing that senses gravity can read lean mid-corner — not this puck, not a dearer one
- Parked upright it still reads level, so it remains a check that a mount zero worked

Rides you already recorded
- Rides already in your library keep the numbers they were recorded with. Only rides recorded from this version on carry the corrected ones
- Nothing was thrown away: the angle the motion chip reported is still recorded beside the corrected one, in the ride file and in CSV exports

Tripper Puck
- Settings now shows which protocol version the puck is speaking, and says plainly when the app is older than the puck and some of what it sends is going unrecorded — previously a newer puck was read perfectly and its extra data silently dropped, with nothing on screen to say so
- The puck's raw accelerometer and its count of discarded sensor reads are now recorded into your rides and written to the .trip and CSV exports, alongside the gyro and calibration

Knowing which build you are running
- Settings now shows the app version, the date the build was made, and a note you can write yourself — useful for recording which puck firmware a build was paired with

### 1.6 — 2026-08-03

NEW: Rides in iCloud Drive
- Every finished ride is now saved to a Tripper folder in iCloud Drive, so your rides are no longer only on the phone
- Open the folder from Files on any device, or from a Mac; each ride is a .trip file carrying everything — route, speed, lean, g-force and heart rate
- To put one back into Tripper, import it the way you would any ride file
- Copies go one way: Tripper writes rides out and never changes what's already in your library. Turn it off in Settings if you'd rather not use the iCloud storage

Finishing a ride
- The name box now suggests where you set off as well as when — "Manhattan · 2 Aug 14:43" rather than the date on its own. Type over it, or clear it to go back to just the date
- Skip now does what it says: it asks, then discards the ride. It used to save it anyway under the default name, so there was no way to throw away a ride you hadn't meant to record

Select and export several rides at once
- Tap Edit in Rides to pick as many rides as you like — or Select All — then send them out in one go as .trip, GPX or CSV
- Delete a batch the same way, with one confirmation instead of one swipe per ride

Lean, beside slope
- Your lean angle now sits next to slope on the same card, at the same size — live while you ride and again in replay
- The side reads L or R rather than a minus sign, which is easier to take in at a glance on a moving bike; below a degree it doesn't claim a side at all
- It doubles as a check that a mount zero worked: parked upright, it should read Lean with no side
- The card no longer shifts and resizes as the numbers change

Tripper Puck
- Fixed: if the puck went quiet without the phone noticing the link had dropped — after the puck rebooted on the bike's power, for instance — Tripper kept believing it was still connected and never tried to reconnect, so the rest of the ride was recorded on phone sensors. It now spots the silence and reconnects by itself
- Fixed: a puck on the newest firmware could look disconnected, and a ride recorded in that state had no puck data in it at all. Tripper now reads a puck newer than the one it knows about instead of refusing it
- Zeroing the puck's mounting angle now tells you whether the puck accepted it — pending, confirmed, or no response — instead of only confirming your tap
- Settings shows the puck's IMU calibration, so you can see how confident it is about which way is down before trusting a lean reading
- The puck's own gyro and calibration are now recorded into your rides and written to the .trip and CSV exports, alongside the phone's

### 1.5 — 2026-07-31

NEW: Bluetooth heart-rate sensors
- Tripper now connects to any standard Bluetooth heart-rate sensor — a chest strap (Polar, Garmin, Wahoo…) or a sports watch broadcasting heart rate, like Garmin's "Broadcast Heart Rate" mode
- Turn it on in Settings: it pairs with the first sensor it finds, reconnects to that one from then on, and shows the live reading right in Settings; Forget lets you switch sensors
- While the sensor reports, its reading is what's recorded and shown — live on the dashboard, in replay and on the ride chart. The Apple Watch still works exactly as before and takes over whenever the sensor isn't reporting
- Heart rate synced into Apple Health by other apps (Garmin Connect, for example) is also stitched into your rides after the fact, filling any gaps

Tripper Puck
- Regen braking level from the bike is now recorded and shown — live in Settings, and in replay next to battery, power and ride mode
- Tripper recognises which puck it is talking to, so a Light puck (the CAN-only build, no GPS) keeps your phone as the position source instead of reporting a fix that is never coming

## More apps by Koray Birand

- [Ivao Active ATC](https://appshunter.io/ios/app/ivao-active-atc/id6504582463)
- [Weather Live: Wind & Forecast](https://appshunter.io/ios/app/weather-live-wind-and-forecast/id6780178621)

All apps by Koray Birand: https://appshunter.io/developer/1752915873

---

*Data collected daily from the US App Store and indexed by [AppsHunter](https://appshunter.io/). User reviews are verbatim App Store reviews. Ratings, prices and chart positions refresh continuously; this snapshot is from 2026-08-26.*