Not currently tracked · last seen 3h ago
- Flights observed
- 135 showing last 50
- Avg flight time
- 3h 18m
- Typical route
- ZTH → AMS
- Last seen
- 3h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | - | May 29, 20:20 UTC | May 29, 23:50 UTC | 3h 30m |
| 2026-05-29 | - | May 29, 16:05 UTC | May 29, 19:00 UTC | 2h 55m |
| 2026-05-29 | ZTH → AMS | May 29, 09:50 UTC | May 29, 12:45 UTC | 2h 55m |
| 2026-05-29 | AMS → ZTH | May 29, 05:40 UTC | May 29, 08:15 UTC | 2h 35m |
| 2026-05-28 | PMI → AMS | May 28, 19:30 UTC | May 28, 21:45 UTC | 2h 15m |
| 2026-05-28 | AMS → PMI | May 28, 16:10 UTC | May 28, 18:15 UTC | 2h 5m |
| 2026-05-28 | - | May 28, 11:45 UTC | May 28, 14:25 UTC | 2h 40m |
| 2026-05-28 | - | May 28, 10:50 UTC | May 28, 11:00 UTC | 10m |
| 2026-05-28 | - | May 28, 05:45 UTC | May 28, 08:40 UTC | 2h 55m |
| 2026-05-27 | - | May 27, 10:35 UTC | May 27, 13:10 UTC | 2h 35m |
| 2026-05-27 | - | May 27, 09:45 UTC | May 27, 10:00 UTC | 15m |
| 2026-05-27 | - | May 27, 08:25 UTC | May 27, 08:35 UTC | 10m |
| 2026-05-27 | - | May 27, 04:49 UTC | May 27, 07:40 UTC | 2h 50m |
| 2026-05-26 | FUE → AMS | May 26, 19:25 UTC | May 26, 22:59 UTC | 3h 35m |
| 2026-05-26 | AMS → FUE | May 26, 14:00 UTC | May 26, 18:10 UTC | 4h 10m |
| 2026-05-26 | BDS → AMS | May 26, 09:49 UTC | May 26, 12:24 UTC | 2h 35m |
| 2026-05-26 | AMS → BDS | May 26, 06:20 UTC | May 26, 08:34 UTC | 2h 15m |
| 2026-05-25 | LPA → AMS | May 25, 19:00 UTC | May 25, 23:00 UTC | 3h 59m |
| 2026-05-25 | AMS → LPA | May 25, 13:10 UTC | May 25, 17:15 UTC | 4h 5m |
| 2026-05-24 | PMI → AMS | May 24, 23:00 UTC | May 24, 23:10 UTC | 10m |
| 2026-05-24 | PMI → AMS | May 24, 21:05 UTC | May 24, 21:51 UTC | 46m |
| 2026-05-24 | AMS → PMI | May 24, 17:35 UTC | May 24, 19:35 UTC | 2h 0m |
| 2026-05-24 | LPA → AMS | May 24, 11:45 UTC | May 24, 15:30 UTC | 3h 45m |
| 2026-05-24 | AMS → LPA | May 24, 06:00 UTC | May 24, 09:45 UTC | 3h 45m |
| 2026-05-23 | HER → AMS | May 23, 16:40 UTC | May 23, 19:55 UTC | 3h 15m |
| 2026-05-23 | AMS → HER | May 23, 12:05 UTC | May 23, 15:05 UTC | 3h 0m |
| 2026-05-23 | OHD → AMS | May 23, 07:35 UTC | May 23, 10:05 UTC | 2h 30m |
| 2026-05-23 | AMS → OHD | May 23, 04:05 UTC | May 23, 06:15 UTC | 2h 10m |
| 2026-05-22 | AMS → BVC | May 22, 05:40 UTC | May 22, 20:00 UTC | 14h 20m |
| 2026-05-21 | AMS → PDL | May 21, 05:30 UTC | May 21, 20:10 UTC | 14h 40m |
| 2026-05-20 | DLM → AMS | May 20, 10:55 UTC | May 20, 14:20 UTC | 3h 25m |
| 2026-05-20 | AMS → DLM | May 20, 06:05 UTC | May 20, 09:10 UTC | 3h 5m |
| 2026-05-19 | AMS → FUE | May 19, 13:55 UTC | May 19, 23:05 UTC | 9h 10m |
| 2026-05-19 | BDS → AMS | May 19, 09:45 UTC | May 19, 12:05 UTC | 2h 20m |
| 2026-05-19 | AMS → BDS | May 19, 06:10 UTC | May 19, 08:25 UTC | 2h 15m |
| 2026-05-18 | - | May 18, 19:35 UTC | May 18, 23:15 UTC | 3h 40m |
| 2026-05-18 | AMS → RHO | May 18, 15:05 UTC | May 18, 18:20 UTC | 3h 15m |
| 2026-05-18 | KGS → AMS | May 18, 09:35 UTC | May 18, 12:45 UTC | 3h 10m |
| 2026-05-18 | AMS → KGS | May 18, 04:45 UTC | May 18, 07:50 UTC | 3h 5m |
| 2026-05-17 | ZTH → AMS | May 17, 16:20 UTC | May 17, 19:10 UTC | 2h 50m |
| 2026-05-17 | AMS → ZTH | May 17, 12:25 UTC | May 17, 15:05 UTC | 2h 40m |
| 2026-05-17 | TIV → AMS | May 17, 08:10 UTC | May 17, 10:15 UTC | 2h 5m |
| 2026-05-17 | AMS → TIV | May 17, 04:40 UTC | May 17, 06:40 UTC | 2h 0m |
| 2026-05-16 | DLM → AMS | May 16, 20:30 UTC | May 17, 00:15 UTC | 3h 45m |
| 2026-05-16 | AMS → LPA | May 16, 14:41 UTC | May 16, 18:35 UTC | 3h 55m |
| 2026-05-16 | ZTH → AMS | May 16, 09:51 UTC | May 16, 12:55 UTC | 3h 5m |
| 2026-05-16 | AMS → ZTH | May 16, 05:05 UTC | May 16, 07:45 UTC | 2h 41m |
| 2026-05-15 | - | May 15, 20:05 UTC | May 15, 23:35 UTC | 3h 30m |
| 2026-05-15 | - | May 15, 16:10 UTC | May 15, 18:55 UTC | 2h 45m |
| 2026-05-15 | AMS → MJT | May 15, 11:10 UTC | May 15, 14:25 UTC | 3h 15m |
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 ZTH and AMS based on observed flights.
Where is PH-TFR right now?
PH-TFR is not currently being tracked; last seen 3h ago.