Not currently tracked · last seen 4h ago
- Flights observed
- 155 showing last 50
- Avg flight time
- 3h 58m
- Typical route
- AMS → BVC
- Last seen
- 4h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | AMS → BVC | May 29, 05:35 UTC | May 29, 19:55 UTC | 14h 20m |
| 2026-05-28 | AMS → PDL | May 28, 05:35 UTC | May 28, 20:25 UTC | 14h 50m |
| 2026-05-27 | TIV → AMS | May 27, 15:35 UTC | May 27, 17:40 UTC | 2h 5m |
| 2026-05-27 | AMS → TIV | May 27, 12:20 UTC | May 27, 14:10 UTC | 1h 50m |
| 2026-05-27 | OHD → AMS | May 27, 07:35 UTC | May 27, 10:05 UTC | 2h 30m |
| 2026-05-27 | - | May 27, 03:54 UTC | May 27, 06:04 UTC | 2h 10m |
| 2026-05-26 | AMS → BVC | May 26, 15:49 UTC | May 26, 19:45 UTC | 3h 55m |
| 2026-05-26 | AMS → BVC | May 26, 05:30 UTC | May 26, 09:40 UTC | 4h 10m |
| 2026-05-25 | ZTH → AMS | May 25, 17:10 UTC | May 25, 19:59 UTC | 2h 50m |
| 2026-05-25 | RTM → ZTH | May 25, 12:05 UTC | May 25, 14:50 UTC | 2h 45m |
| 2026-05-25 | - | May 25, 08:00 UTC | May 25, 10:45 UTC | 2h 45m |
| 2026-05-25 | AMS → ZTH | May 25, 04:05 UTC | May 25, 06:50 UTC | 2h 45m |
| 2026-05-24 | HRG → AMS | May 24, 17:00 UTC | May 24, 20:20 UTC | 3h 20m |
| 2026-05-24 | AMS → KGS | May 24, 12:40 UTC | May 24, 15:50 UTC | 3h 10m |
| 2026-05-24 | TIA → AMS | May 24, 08:15 UTC | May 24, 10:35 UTC | 2h 20m |
| 2026-05-24 | AMS → TIA | May 24, 04:45 UTC | May 24, 06:55 UTC | 2h 10m |
| 2026-05-23 | - | May 23, 20:45 UTC | May 24, 00:25 UTC | 3h 40m |
| 2026-05-23 | AMS → AYT | May 23, 15:50 UTC | May 23, 19:20 UTC | 3h 30m |
| 2026-05-23 | AYT → AMS | May 23, 11:05 UTC | May 23, 14:20 UTC | 3h 15m |
| 2026-05-23 | AMS → KGS | May 23, 06:30 UTC | May 23, 09:40 UTC | 3h 10m |
| 2026-05-22 | - | May 22, 14:00 UTC | May 22, 23:25 UTC | 9h 25m |
| 2026-05-22 | ZTH → AMS | May 22, 09:35 UTC | May 22, 12:35 UTC | 3h 0m |
| 2026-05-22 | AMS → ZTH | May 22, 05:45 UTC | May 22, 08:30 UTC | 2h 45m |
| 2026-05-21 | PMI → AMS | May 21, 19:30 UTC | May 21, 21:40 UTC | 2h 10m |
| 2026-05-21 | AMS → PMI | May 21, 16:10 UTC | May 21, 18:05 UTC | 1h 55m |
| 2026-05-21 | - | May 21, 11:20 UTC | May 21, 14:00 UTC | 2h 40m |
| 2026-05-21 | - | May 21, 10:30 UTC | May 21, 10:40 UTC | 10m |
| 2026-05-21 | - | May 21, 05:30 UTC | May 21, 08:35 UTC | 3h 5m |
| 2026-05-20 | KGS → AMS | May 20, 19:25 UTC | May 20, 22:50 UTC | 3h 25m |
| 2026-05-20 | AMS → KGS | May 20, 15:00 UTC | May 20, 18:00 UTC | 3h 0m |
| 2026-05-20 | - | May 20, 10:25 UTC | May 20, 13:10 UTC | 2h 45m |
| 2026-05-20 | - | May 20, 09:35 UTC | May 20, 09:50 UTC | 15m |
| 2026-05-20 | - | May 20, 08:20 UTC | May 20, 08:30 UTC | 10m |
| 2026-05-20 | - | May 20, 04:40 UTC | May 20, 07:35 UTC | 2h 55m |
| 2026-05-19 | AMS → BVC | May 19, 15:50 UTC | May 19, 19:55 UTC | 4h 5m |
| 2026-05-19 | AMS → BVC | May 19, 05:45 UTC | May 19, 09:55 UTC | 4h 10m |
| 2026-05-18 | ZTH → AMS | May 18, 16:05 UTC | May 18, 18:55 UTC | 2h 49m |
| 2026-05-18 | RTM → ZTH | May 18, 12:10 UTC | May 18, 14:45 UTC | 2h 35m |
| 2026-05-18 | - | May 18, 07:55 UTC | May 18, 10:45 UTC | 2h 50m |
| 2026-05-18 | AMS → ZTH | May 18, 03:50 UTC | May 18, 06:25 UTC | 2h 35m |
| 2026-05-17 | PMI → AMS | May 17, 20:55 UTC | May 17, 23:00 UTC | 2h 5m |
| 2026-05-17 | AMS → PMI | May 17, 17:15 UTC | May 17, 19:10 UTC | 1h 55m |
| 2026-05-17 | LPA → AMS | May 17, 11:50 UTC | May 17, 15:31 UTC | 3h 40m |
| 2026-05-17 | AMS → LPA | May 17, 05:50 UTC | May 17, 09:40 UTC | 3h 50m |
| 2026-05-16 | - | May 16, 11:01 UTC | May 16, 22:35 UTC | 11h 35m |
| 2026-05-15 | AMS → BVC | May 15, 05:40 UTC | May 15, 20:05 UTC | 14h 24m |
| 2026-05-14 | AMS → PDL | May 14, 05:30 UTC | May 14, 20:05 UTC | 14h 35m |
| 2026-05-13 | TIV → AMS | May 13, 15:50 UTC | May 13, 18:05 UTC | 2h 15m |
| 2026-05-13 | AMS → TIV | May 13, 12:25 UTC | May 13, 14:20 UTC | 1h 55m |
| 2026-05-12 | DLM → AMS | May 12, 19:15 UTC | May 12, 22:45 UTC | 3h 30m |
Specifications
| Registration | PH-TFP |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 485A83 · 22055203 (octal) |
Looking for transponder-level data? View the Mode-S 485A83 page for country allocation, callsign history, and ADS-B signal details.
PH-TFP frequently asked
What type of aircraft is PH-TFP?
PH-TFP is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for PH-TFP?
PH-TFP broadcasts on Mode-S (ICAO 24-bit) address 485A83 (octal 22055203). View the transponder page.
What route does PH-TFP typically fly?
PH-TFP most frequently flies between AMS and BVC based on observed flights.
Where is PH-TFP right now?
PH-TFP is not currently being tracked; last seen 4h ago.