Not currently tracked · last seen 6h ago
- Flights observed
- 511 showing last 50
- Avg flight time
- 1h 11m
- Typical route
- BGO → AMS
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 19:30 UTC | Jul 13, 20:55 UTC | 1h 25m |
| 2026-07-13 | MAN → AMS | Jul 13, 17:15 UTC | Jul 13, 18:05 UTC | 50m |
| 2026-07-13 | AMS → MAN | Jul 13, 14:50 UTC | Jul 13, 15:40 UTC | 50m |
| 2026-07-13 | - | Jul 13, 12:45 UTC | Jul 13, 13:35 UTC | 50m |
| 2026-07-13 | AMS → BLL | Jul 13, 11:05 UTC | Jul 13, 11:45 UTC | 40m |
| 2026-07-13 | BRU → AMS | Jul 13, 09:10 UTC | Jul 13, 09:40 UTC | 30m |
| 2026-07-13 | - | Jul 13, 07:35 UTC | Jul 13, 08:01 UTC | 25m |
| 2026-07-13 | VCE → AMS | Jul 13, 04:10 UTC | Jul 13, 05:45 UTC | 1h 35m |
| 2026-07-12 | AMS → VCE | Jul 12, 19:05 UTC | Jul 12, 20:30 UTC | 1h 25m |
| 2026-07-12 | IBZ → AMS | Jul 12, 15:35 UTC | Jul 12, 17:40 UTC | 2h 5m |
| 2026-07-12 | - | Jul 12, 11:55 UTC | Jul 12, 14:05 UTC | 2h 10m |
| 2026-07-12 | BGO → AMS | Jul 12, 08:50 UTC | Jul 12, 10:20 UTC | 1h 30m |
| 2026-07-12 | - | Jul 12, 06:35 UTC | Jul 12, 07:55 UTC | 1h 20m |
| 2026-07-12 | BER → AMS | Jul 12, 04:05 UTC | Jul 12, 05:05 UTC | 1h 0m |
| 2026-07-11 | AMS → BER | Jul 11, 19:50 UTC | Jul 11, 20:50 UTC | 1h 0m |
| 2026-07-11 | - | Jul 11, 15:40 UTC | Jul 11, 17:45 UTC | 2h 5m |
| 2026-07-11 | - | Jul 11, 12:10 UTC | Jul 11, 14:15 UTC | 2h 5m |
| 2026-07-11 | - | Jul 11, 09:45 UTC | Jul 11, 10:55 UTC | 1h 10m |
| 2026-07-11 | - | Jul 11, 07:30 UTC | Jul 11, 08:40 UTC | 1h 10m |
| 2026-07-11 | - | Jul 11, 04:20 UTC | Jul 11, 05:55 UTC | 1h 35m |
| 2026-07-10 | - | Jul 10, 18:45 UTC | Jul 10, 20:20 UTC | 1h 35m |
| 2026-07-10 | - | Jul 10, 15:40 UTC | Jul 10, 17:15 UTC | 1h 35m |
| 2026-07-10 | AMS → WAW | Jul 10, 13:05 UTC | Jul 10, 14:35 UTC | 1h 30m |
| 2026-07-10 | BGO → AMS | Jul 10, 10:15 UTC | Jul 10, 11:40 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 08:10 UTC | Jul 10, 09:25 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 05:15 UTC | Jul 10, 06:20 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 20:35 UTC | Jul 9, 21:50 UTC | 1h 15m |
| 2026-07-09 | ZRH → AMS | Jul 9, 17:55 UTC | Jul 9, 19:00 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 15:55 UTC | Jul 9, 16:45 UTC | 50m |
| 2026-07-09 | - | Jul 9, 13:45 UTC | Jul 9, 14:25 UTC | 40m |
| 2026-07-09 | - | Jul 9, 11:30 UTC | Jul 9, 12:20 UTC | 50m |
| 2026-07-09 | CDG → AMS | Jul 9, 09:25 UTC | Jul 9, 10:05 UTC | 40m |
| 2026-07-09 | - | Jul 9, 06:50 UTC | Jul 9, 07:40 UTC | 50m |
| 2026-07-09 | - | Jul 9, 04:15 UTC | Jul 9, 05:05 UTC | 50m |
| 2026-07-08 | - | Jul 8, 20:10 UTC | Jul 8, 21:00 UTC | 50m |
| 2026-07-08 | ZRH → AMS | Jul 8, 17:40 UTC | Jul 8, 18:45 UTC | 1h 5m |
| 2026-07-08 | AMS → ZRH | Jul 8, 15:35 UTC | Jul 8, 16:35 UTC | 1h 0m |
| 2026-07-08 | PRG → AMS | Jul 8, 12:40 UTC | Jul 8, 13:50 UTC | 1h 10m |
| 2026-07-08 | - | Jul 8, 10:35 UTC | Jul 8, 11:40 UTC | 1h 5m |
| 2026-07-08 | - | Jul 8, 08:40 UTC | Jul 8, 09:05 UTC | 25m |
| 2026-07-08 | - | Jul 8, 07:15 UTC | Jul 8, 07:35 UTC | 20m |
| 2026-07-08 | - | Jul 8, 04:45 UTC | Jul 8, 05:55 UTC | 1h 10m |
| 2026-07-07 | - | Jul 7, 19:50 UTC | Jul 7, 20:55 UTC | 1h 5m |
| 2026-07-07 | LIN → AMS | Jul 7, 15:20 UTC | Jul 7, 16:45 UTC | 1h 25m |
| 2026-07-07 | - | Jul 7, 12:45 UTC | Jul 7, 14:00 UTC | 1h 15m |
| 2026-07-07 | - | Jul 7, 08:00 UTC | Jul 7, 08:45 UTC | 45m |
| 2026-07-07 | AMS → CDG | Jul 7, 05:35 UTC | Jul 7, 06:25 UTC | 50m |
| 2026-07-06 | - | Jul 6, 11:30 UTC | Jul 6, 13:50 UTC | 2h 20m |
| 2026-07-06 | - | Jul 6, 08:35 UTC | Jul 6, 10:25 UTC | 1h 50m |
| 2026-07-06 | VIE → AMS | Jul 6, 05:15 UTC | Jul 6, 06:45 UTC | 1h 30m |
Specifications
| Registration | PH-BXD |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 484133 · 22040463 (octal) |
Looking for transponder-level data? View the Mode-S 484133 page for country allocation, callsign history, and ADS-B signal details.
PH-BXD frequently asked
What type of aircraft is PH-BXD?
PH-BXD is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for PH-BXD?
PH-BXD broadcasts on Mode-S (ICAO 24-bit) address 484133 (octal 22040463). View the transponder page.
What route does PH-BXD typically fly?
PH-BXD most frequently flies between BGO and AMS based on observed flights.
Where is PH-BXD right now?
PH-BXD is not currently being tracked; last seen 6h ago.