On the ground · transponder active
- Flights observed
- 140 showing last 50
- Avg flight time
- 3h 34m
- Typical route
- ZTH → AMS
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | ZTH → AMS | May 30, 09:30 UTC | May 30, 11:15 UTC | 1h 45m |
| 2026-05-30 | AMS → ZTH | May 30, 05:15 UTC | May 30, 07:50 UTC | 2h 35m |
| 2026-05-29 | GRQ → AMS | May 29, 14:15 UTC | May 29, 23:55 UTC | 9h 40m |
| 2026-05-29 | - | May 29, 12:35 UTC | May 29, 12:50 UTC | 15m |
| 2026-05-27 | AMS → AMS | May 27, 12:00 UTC | May 27, 22:55 UTC | 10h 55m |
| 2026-05-25 | RHO → AMS | May 25, 18:15 UTC | May 25, 21:35 UTC | 3h 20m |
| 2026-05-25 | AMS → RHO | May 25, 13:35 UTC | May 25, 16:55 UTC | 3h 20m |
| 2026-05-25 | AMS → PVK | May 25, 09:00 UTC | May 25, 11:45 UTC | 2h 45m |
| 2026-05-25 | AMS → PVK | May 25, 03:50 UTC | May 25, 06:20 UTC | 2h 30m |
| 2026-05-24 | ZTH → AMS | May 24, 16:15 UTC | May 24, 19:05 UTC | 2h 50m |
| 2026-05-24 | AMS → ZTH | May 24, 12:30 UTC | May 24, 15:10 UTC | 2h 40m |
| 2026-05-24 | TIV → AMS | May 24, 08:15 UTC | May 24, 10:25 UTC | 2h 10m |
| 2026-05-24 | AMS → TIV | May 24, 04:55 UTC | May 24, 07:00 UTC | 2h 5m |
| 2026-05-23 | - | May 23, 11:30 UTC | May 23, 14:15 UTC | 2h 45m |
| 2026-05-23 | - | May 23, 10:40 UTC | May 23, 10:55 UTC | 15m |
| 2026-05-23 | - | May 23, 09:20 UTC | May 23, 09:25 UTC | 5m |
| 2026-05-23 | - | May 23, 05:45 UTC | May 23, 08:30 UTC | 2h 45m |
| 2026-05-22 | - | May 22, 20:25 UTC | May 22, 23:45 UTC | 3h 20m |
| 2026-05-22 | - | May 22, 15:55 UTC | May 22, 18:55 UTC | 3h 0m |
| 2026-05-22 | AMS → MJT | May 22, 11:05 UTC | May 22, 14:15 UTC | 3h 10m |
| 2026-05-22 | AMS → MJT | May 22, 09:25 UTC | May 22, 09:50 UTC | 25m |
| 2026-05-22 | AMS → MJT | May 22, 05:15 UTC | May 22, 08:05 UTC | 2h 50m |
| 2026-05-21 | TFS → AMS | May 21, 16:10 UTC | May 21, 20:00 UTC | 3h 50m |
| 2026-05-21 | AMS → TFS | May 21, 10:30 UTC | May 21, 14:50 UTC | 4h 20m |
| 2026-05-20 | AYT → AMS | May 20, 19:50 UTC | May 20, 23:30 UTC | 3h 40m |
| 2026-05-20 | - | May 20, 17:25 UTC | May 20, 18:45 UTC | 1h 20m |
| 2026-05-20 | - | May 20, 14:25 UTC | May 20, 16:20 UTC | 1h 55m |
| 2026-05-20 | ADB → AMS | May 20, 09:45 UTC | May 20, 12:55 UTC | 3h 10m |
| 2026-05-20 | AMS → ADB | May 20, 05:20 UTC | May 20, 08:05 UTC | 2h 45m |
| 2026-05-19 | RHO → AMS | May 19, 19:00 UTC | May 19, 22:30 UTC | 3h 30m |
| 2026-05-19 | AMS → RHO | May 19, 14:35 UTC | May 19, 17:50 UTC | 3h 15m |
| 2026-05-19 | CFU → AMS | May 19, 09:45 UTC | May 19, 12:10 UTC | 2h 25m |
| 2026-05-19 | AMS → CFU | May 19, 06:00 UTC | May 19, 08:15 UTC | 2h 15m |
| 2026-05-18 | GRQ → AMS | May 18, 16:00 UTC | May 19, 01:35 UTC | 9h 34m |
| 2026-05-18 | - | May 18, 04:30 UTC | May 18, 14:40 UTC | 10h 10m |
| 2026-05-17 | TFS → AMS | May 17, 16:15 UTC | May 17, 20:05 UTC | 3h 50m |
| 2026-05-17 | AMS → TFS | May 17, 10:30 UTC | May 17, 14:30 UTC | 4h 0m |
| 2026-05-16 | FNC → AMS | May 16, 10:31 UTC | May 16, 14:05 UTC | 3h 35m |
| 2026-05-16 | AMS → FNC | May 16, 05:40 UTC | May 16, 09:21 UTC | 3h 41m |
| 2026-05-15 | TFS → AMS | May 15, 16:25 UTC | May 15, 19:35 UTC | 3h 10m |
| 2026-05-15 | - | May 15, 09:50 UTC | May 15, 13:30 UTC | 3h 40m |
| 2026-05-14 | PMI → AMS | May 14, 19:25 UTC | May 14, 21:30 UTC | 2h 5m |
| 2026-05-14 | AMS → PMI | May 14, 16:10 UTC | May 14, 18:05 UTC | 1h 55m |
| 2026-05-14 | - | May 14, 10:35 UTC | May 14, 14:05 UTC | 3h 30m |
| 2026-05-14 | - | May 14, 05:45 UTC | May 14, 08:25 UTC | 2h 40m |
| 2026-05-13 | ZTH → AMS | May 13, 16:10 UTC | May 13, 19:00 UTC | 2h 50m |
| 2026-05-13 | AMS → ZTH | May 13, 12:10 UTC | May 13, 14:51 UTC | 2h 40m |
| 2026-05-12 | AMS → BVC | May 12, 16:10 UTC | May 12, 19:55 UTC | 3h 45m |
| 2026-05-12 | AMS → BVC | May 12, 05:50 UTC | May 12, 10:05 UTC | 4h 15m |
| 2026-05-11 | AMS → PDL | May 11, 05:50 UTC | May 11, 20:45 UTC | 14h 56m |
Specifications
| Registration | PH-TFT |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 485A85 · 22055205 (octal) |
Looking for transponder-level data? View the Mode-S 485A85 page for country allocation, callsign history, and ADS-B signal details.
PH-TFT frequently asked
What type of aircraft is PH-TFT?
PH-TFT is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for PH-TFT?
PH-TFT broadcasts on Mode-S (ICAO 24-bit) address 485A85 (octal 22055205). View the transponder page.
What route does PH-TFT typically fly?
PH-TFT most frequently flies between ZTH and AMS based on observed flights.
Where is PH-TFT right now?
PH-TFT is currently on the ground with its transponder active.