Airborne now · flying as TFL3MA at 37,000 ft
- Flights observed
- 284 showing last 50
- Avg flight time
- 4h 0m
- Typical route
- AMS → MJT
- Last seen
- 6h ago
Live position
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | AMS → LPA | Jul 13, 13:15 UTC | Jul 13, 22:55 UTC | 9h 40m |
| 2026-07-13 | - | Jul 13, 08:45 UTC | Jul 13, 11:40 UTC | 2h 55m |
| 2026-07-13 | - | Jul 13, 03:50 UTC | Jul 13, 06:01 UTC | 2h 10m |
| 2026-07-12 | - | Jul 12, 18:10 UTC | Jul 12, 21:50 UTC | 3h 40m |
| 2026-07-12 | - | Jul 12, 12:25 UTC | Jul 12, 16:40 UTC | 4h 15m |
| 2026-07-12 | - | Jul 12, 07:55 UTC | Jul 12, 10:15 UTC | 2h 20m |
| 2026-07-12 | - | Jul 12, 04:45 UTC | Jul 12, 06:40 UTC | 1h 55m |
| 2026-07-11 | - | Jul 11, 12:15 UTC | Jul 11, 23:25 UTC | 11h 10m |
| 2026-07-10 | - | Jul 10, 21:30 UTC | Jul 11, 01:10 UTC | 3h 40m |
| 2026-07-10 | - | Jul 10, 15:30 UTC | Jul 10, 19:40 UTC | 4h 10m |
| 2026-07-10 | - | Jul 10, 04:35 UTC | Jul 10, 14:15 UTC | 9h 40m |
| 2026-07-09 | - | Jul 9, 18:45 UTC | Jul 9, 22:35 UTC | 3h 50m |
| 2026-07-09 | - | Jul 9, 13:20 UTC | Jul 9, 17:30 UTC | 4h 10m |
| 2026-07-08 | AYT → AMS | Jul 8, 19:05 UTC | Jul 8, 22:55 UTC | 3h 50m |
| 2026-07-08 | AMS → AYT | Jul 8, 14:45 UTC | Jul 8, 18:00 UTC | 3h 15m |
| 2026-07-08 | ADB → AMS | Jul 8, 09:40 UTC | Jul 8, 13:05 UTC | 3h 25m |
| 2026-07-08 | - | Jul 8, 05:15 UTC | Jul 8, 07:50 UTC | 2h 35m |
| 2026-07-07 | FUE → AMS | Jul 7, 19:20 UTC | Jul 7, 23:15 UTC | 3h 55m |
| 2026-07-07 | AMS → FUE | Jul 7, 14:15 UTC | Jul 7, 18:20 UTC | 4h 5m |
| 2026-07-07 | - | Jul 7, 08:25 UTC | Jul 7, 12:10 UTC | 3h 45m |
| 2026-07-07 | - | Jul 7, 04:10 UTC | Jul 7, 07:05 UTC | 2h 55m |
| 2026-07-06 | - | Jul 6, 05:35 UTC | Jul 6, 21:00 UTC | 15h 25m |
| 2026-07-05 | - | Jul 5, 20:35 UTC | Jul 5, 22:45 UTC | 2h 10m |
| 2026-07-05 | AMS → PMI | Jul 5, 17:25 UTC | Jul 5, 19:25 UTC | 2h 0m |
| 2026-07-05 | LPA → AMS | Jul 5, 11:35 UTC | Jul 5, 15:30 UTC | 3h 55m |
| 2026-07-05 | - | Jul 5, 06:10 UTC | Jul 5, 10:15 UTC | 4h 5m |
| 2026-07-04 | RHO → AMS | Jul 4, 20:50 UTC | Jul 5, 00:30 UTC | 3h 40m |
| 2026-07-04 | AMS → RHO | Jul 4, 16:15 UTC | Jul 4, 19:20 UTC | 3h 5m |
| 2026-07-04 | FNC → AMS | Jul 4, 10:35 UTC | Jul 4, 14:10 UTC | 3h 35m |
| 2026-07-04 | - | Jul 4, 09:15 UTC | Jul 4, 09:20 UTC | 5m |
| 2026-07-04 | - | Jul 4, 05:40 UTC | Jul 4, 08:45 UTC | 3h 5m |
| 2026-07-03 | - | Jul 3, 20:20 UTC | Jul 3, 23:50 UTC | 3h 30m |
| 2026-07-03 | - | Jul 3, 16:00 UTC | Jul 3, 18:50 UTC | 2h 50m |
| 2026-07-03 | AMS → MJT | Jul 3, 10:40 UTC | Jul 3, 14:05 UTC | 3h 25m |
| 2026-07-03 | AMS → MJT | Jul 3, 08:45 UTC | Jul 3, 09:05 UTC | 20m |
| 2026-07-03 | AMS → MJT | Jul 3, 04:50 UTC | Jul 3, 07:35 UTC | 2h 45m |
| 2026-07-02 | AYT → AMS | Jul 2, 19:15 UTC | Jul 2, 22:40 UTC | 3h 25m |
| 2026-07-02 | AMS → KGS | Jul 2, 14:00 UTC | Jul 2, 17:10 UTC | 3h 10m |
| 2026-07-02 | - | Jul 2, 09:45 UTC | Jul 2, 12:20 UTC | 2h 35m |
| 2026-07-02 | - | Jul 2, 06:00 UTC | Jul 2, 08:10 UTC | 2h 10m |
| 2026-07-01 | KGS → AMS | Jul 1, 19:15 UTC | Jul 1, 22:30 UTC | 3h 15m |
| 2026-07-01 | AMS → KGS | Jul 1, 14:55 UTC | Jul 1, 18:10 UTC | 3h 15m |
| 2026-07-01 | ADB → AMS | Jul 1, 09:45 UTC | Jul 1, 12:50 UTC | 3h 5m |
| 2026-07-01 | AMS → ADB | Jul 1, 05:30 UTC | Jul 1, 08:25 UTC | 2h 55m |
| 2026-06-30 | RHO → AMS | Jun 30, 19:25 UTC | Jun 30, 22:50 UTC | 3h 25m |
| 2026-06-30 | AMS → RHO | Jun 30, 14:45 UTC | Jun 30, 18:10 UTC | 3h 25m |
| 2026-06-30 | BDS → AMS | Jun 30, 09:55 UTC | Jun 30, 12:10 UTC | 2h 15m |
| 2026-06-30 | AMS → BDS | Jun 30, 06:25 UTC | Jun 30, 08:40 UTC | 2h 15m |
| 2026-06-29 | GRQ → AMS | Jun 29, 15:34 UTC | Jun 30, 01:09 UTC | 9h 35m |
| 2026-06-29 | AMS → GRQ | Jun 29, 04:30 UTC | Jun 29, 14:19 UTC | 9h 50m |
Specifications
| Registration | PH-TFR |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 485A84 · 22055204 (octal) |
Looking for transponder-level data? View the Mode-S 485A84 page for country allocation, callsign history, and ADS-B signal details.
PH-TFR frequently asked
What type of aircraft is PH-TFR?
PH-TFR is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for PH-TFR?
PH-TFR broadcasts on Mode-S (ICAO 24-bit) address 485A84 (octal 22055204). View the transponder page.
What route does PH-TFR typically fly?
PH-TFR most frequently flies between AMS and MJT based on observed flights.
Where is PH-TFR right now?
PH-TFR is currently airborne flying as TFL3MA. Live position is shown on the map above.