TravStats
Self-hosted travel logbook for small households and groups (1–10 users).
A logbook first — record trips by hand, scan a boarding pass, import a confirmation email, or let the Companion app (in beta) record them on your phone — and TravStats turns them into history, stats and maps.
travstats.de ·
Documentation — installation, the parsers,
the API and day-to-day operation.
Why TravStats
Log every flight and cruise you take, visualise your routes on
interactive 2D and 3D maps, collect 270+ achievements, and import flights
from boarding passes (QR / PDF417 / OCR), confirmation emails, or
Excel/CSV — all on your own server, no cloud, no telemetry.
A logbook first — you record trips by hand, scan a boarding pass, or
import a confirmation email, and TravStats turns them into history,
stats and maps. Recording is optional and opt-in: the TravStats
Companion app (in beta) can record your own flights and trips on your
phone and upload them to your own server. TravTrack is an opt-in location
history with privacy zones: positions arrive from the Companion, from
OwnTracks and Overland (a per-device ingest token, POST /api/v1/travtrack/ingest/owntracks
and /overland), or from files and a copy of your Dawarich history (below).
TravStats does not follow
other aircraft or people, and nobody sees where you are unless you
create a share link yourself. Flight data is optionally enriched from
AirLabs / Aviationstack / OpenSky, but everything you record lives in
your own PostgreSQL. No accounts on someone else's servers, no analytics,
no ads.
- 🚢 Flights and cruises — import a cruise from email or PDF: the ship, every port of call and sea day; fly-and-cruise trips link both
- 🗺️ Multi-domain maps — routes, heatmap, animated trips and a 3D globe for flights and cruises, colour-coded by frequency and status
- 📊 Cross-domain statistics — distance, countries, active days, top airlines and cruise lines, with year and all-time views
- 🏆 270+ achievements across flights, cruises and cross-domain — bronze to diamond
- 🎫 Boarding-pass scanner — QR / barcode / OCR
- 📧 Email import — plain text, HTML, Outlook
.msg, .eml, with optional local LLM parsing via Ollama
- 📍 TravTrack location history (opt-in) — record from the Companion, OwnTracks or Overland, or import GPX / KML / GeoJSON / TCX files, a Google Timeline export or a copy of your Dawarich history; privacy zones drop fixes on the server
- 🚆 More than flights and cruises — rail, bus, ferry, rental cars, hotels and places, road trips and tours, each with its own map layer and statistics
- 🖼️ Immich albums on trips, and trip sharing between servers with consent on both sides
- 📑 Excel/CSV round-trip import — export, edit in Excel, re-import; rows with an
id update existing flights
- 🤖 Public REST API + OpenAPI 3.0 / Swagger UI — Personal Access Tokens with
read / write / admin scopes for AI agents and automation
- 💾 Automated backups with retention + optional WebDAV sync
- 🔐 Invite-only by default — toggle public registration anytime from the admin UI; JWT in HttpOnly cookies, rate limiting on every sensitive endpoint
- 🌐 German + English UI with browser-locale auto-detection, i18n-ready
Is TravStats for you?
Being honest about the fit costs one paragraph and saves an evening of
someone else's time.
It probably is, if you want your travel history on hardware you
control; keep a household's or a small group's trips in one place; already
run Docker and Postgres, or are happy to let the bundled compose file run
Postgres for you; like filling in a logbook after the fact and getting
maps, stats and achievements out of it; and want flights and cruises
(and hotels and places) in one timeline rather than four apps.
It probably is not, if you want live flight tracking or a radar — this
records where you have been, it does not watch aircraft move; expect a
hosted account you just sign up for, because there is no SaaS version and
running it means running a server; need to onboard more than a handful of
people, since it is built and tested for roughly 1–10 users on one
instance and has no SSO, no org/tenant model and no per-team permissions;
need it on a phone as the primary interface — the web UI is responsive,
but the native app is not released yet; or need automatic, hands-off
import of everything, because a lot of travel history is typed in or
imported from files you supply.
Screenshots
Quick start
The only thing you set in a file is a database password. Everything else —
instance name, user cap, API keys, Ollama model, backup schedule, WebDAV —
is captured by the first-run setup wizard in the browser.
The same route with screenshots and the per-platform detail:
Installation and
First run.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
