Skip to content
TrackJet

About TrackJet

v5 ·

TrackJet is built and run by one person: me, Luis Romero, a software developer living in Frankfurt am Main. This page is the honest version of who is behind the site, why it exists, and the rules the product follows.

Why I built this #

Before TrackJet I spent years building software for people who move things and fight paperwork — a web-hosting business, and a tool that helps people navigate German bureaucracy and customs. Around customs forms and online orders, the same small, stubborn problem kept coming back: a bare tracking number with no carrier name attached. A supplier pastes MSCU… into an email. A marketplace forwards an RR…DE postal code. An air waybill arrives as eleven digits and a hyphen. Search engines rarely land on the right tracking page on the first try — and half of the "universal tracking" sites either guess, or quietly invent status events to look useful.

So I built the tool I wanted to exist: paste anything, and let the structure of the number do the work. Tracking numbers are not random strings. An air waybill carries a three-digit IATA airline prefix and a mod-7 check digit. An ocean container names its owner in the first four letters and validates itself with an ISO 6346 check digit. A postal item ends in the two letters of its origin country, per UPU standard S10. TrackJet reads that structure, identifies the carrier, routes you to the official tracking surface, and — where a licensed data source exists — builds a timeline you can save, share and verify.

What running this site taught me #

The most useful lessons came from watching anonymised searches fail. People paste fragments: a container number missing its four-letter owner code, a booking number where a container number should go, an air waybill missing its airline prefix. And numbers that fail their own check digit — one mistyped digit, and every tracking site on the internet answers "not found" without telling you why. That is the reason TrackJet validates structure first and explains the arithmetic (try the check-digit tool) instead of bouncing you to a dead end, and the reason the blog keeps coming back to the unglamorous mechanics — check digits, prefixes, status codes — that cause most real tracking pain.

The rules the product follows #

  • Never fabricate. TrackJet never invents carrier events. Where no licensed source exists, we say so and route you to the carrier instead.
  • Label every source. Each timeline event carries its real provenance — the licensed DHL feed, a forwarded email, manual input. Estimates are labelled as estimates.
  • No scraping. Live data comes only from licensed or user-authorised sources. We do not evade carrier access controls.
  • Verifiable history. Saved timelines are sealed into an append-only transparency log — anyone can re-check a record at /verify, offline if they wish.
  • Privacy first. Public tracking needs no account and sets no tracking cookies; anonymous search analytics use daily-rotating hashes that cannot be correlated across days. Details in the privacy policy.

What TrackJet covers #

  • Air Cargo (MAWB) — airlines indexed by IATA prefix.
  • Ocean Container (ISO 6346) — shipping lines resolved by BIC owner code.
  • Bill of Lading — carriers resolved by SCAC.
  • Postal & EMS (UPU S10) — national operators resolved by country code.
  • Parcel — UPS, FedEx, DHL, DPD, GLS, TNT, Evri, Royal Mail and more.

Who is responsible #

TrackJet is operated by Luis Romero from Frankfurt am Main — full provider details are in the imprint. How content is researched, written and corrected is documented in the editorial & data policy. Found a mistake? Tell me — corrections are acknowledged on the page they fix.