Not currently tracked · last seen 36m ago
- Flights observed
- 525 showing last 50
- Avg flight time
- 1h 26m
- Typical route
- AMS → FLR
- Last seen
- 36m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 08:10 UTC | Jul 14, 09:00 UTC | 50m |
| 2026-07-14 | - | Jul 14, 04:45 UTC | Jul 14, 06:45 UTC | 2h 0m |
| 2026-07-13 | AMS → VLC | Jul 13, 19:00 UTC | Jul 13, 21:05 UTC | 2h 5m |
| 2026-07-13 | - | Jul 13, 16:00 UTC | Jul 13, 17:45 UTC | 1h 45m |
| 2026-07-13 | AMS → FLR | Jul 13, 13:05 UTC | Jul 13, 14:40 UTC | 1h 35m |
| 2026-07-13 | - | Jul 13, 10:40 UTC | Jul 13, 12:10 UTC | 1h 30m |
| 2026-07-13 | - | Jul 13, 07:30 UTC | Jul 13, 09:20 UTC | 1h 50m |
| 2026-07-13 | BOD → AMS | Jul 13, 04:40 UTC | Jul 13, 06:01 UTC | 1h 20m |
| 2026-07-12 | AMS → BOD | Jul 12, 20:01 UTC | Jul 12, 21:25 UTC | 1h 25m |
| 2026-07-12 | KRK → AMS | Jul 12, 16:35 UTC | Jul 12, 18:15 UTC | 1h 40m |
| 2026-07-12 | - | Jul 12, 14:10 UTC | Jul 12, 15:50 UTC | 1h 40m |
| 2026-07-12 | - | Jul 12, 11:10 UTC | Jul 12, 12:50 UTC | 1h 40m |
| 2026-07-12 | - | Jul 12, 08:45 UTC | Jul 12, 10:10 UTC | 1h 25m |
| 2026-07-12 | GVA → AMS | Jul 12, 05:35 UTC | Jul 12, 06:40 UTC | 1h 5m |
| 2026-07-11 | AMS → GVA | Jul 11, 19:20 UTC | Jul 11, 20:20 UTC | 1h 0m |
| 2026-07-11 | - | Jul 11, 16:00 UTC | Jul 11, 18:10 UTC | 2h 10m |
| 2026-07-11 | - | Jul 11, 12:55 UTC | Jul 11, 14:50 UTC | 1h 55m |
| 2026-07-11 | - | Jul 11, 10:10 UTC | Jul 11, 11:15 UTC | 1h 5m |
| 2026-07-11 | - | Jul 11, 07:55 UTC | Jul 11, 09:00 UTC | 1h 5m |
| 2026-07-11 | BEG → AMS | Jul 11, 04:30 UTC | Jul 11, 06:40 UTC | 2h 10m |
| 2026-07-10 | AMS → BEG | Jul 10, 19:00 UTC | Jul 10, 20:45 UTC | 1h 45m |
| 2026-07-10 | LHR → AMS | Jul 10, 16:35 UTC | Jul 10, 17:15 UTC | 40m |
| 2026-07-10 | - | Jul 10, 14:25 UTC | Jul 10, 15:15 UTC | 50m |
| 2026-07-10 | BEG → AMS | Jul 10, 10:45 UTC | Jul 10, 13:05 UTC | 2h 20m |
| 2026-07-10 | - | Jul 10, 07:55 UTC | Jul 10, 09:40 UTC | 1h 45m |
| 2026-07-10 | - | Jul 10, 05:35 UTC | Jul 10, 06:40 UTC | 1h 5m |
| 2026-07-09 | AMS → ABZ | Jul 9, 21:05 UTC | Jul 9, 22:15 UTC | 1h 10m |
| 2026-07-09 | - | Jul 9, 18:15 UTC | Jul 9, 20:10 UTC | 1h 55m |
| 2026-07-09 | AMS → FLR | Jul 9, 15:25 UTC | Jul 9, 17:10 UTC | 1h 45m |
| 2026-07-09 | - | Jul 9, 10:05 UTC | Jul 9, 10:55 UTC | 50m |
| 2026-07-09 | - | Jul 9, 08:25 UTC | Jul 9, 09:15 UTC | 50m |
| 2026-07-09 | TLS → AMS | Jul 9, 04:20 UTC | Jul 9, 05:50 UTC | 1h 30m |
| 2026-07-08 | - | Jul 8, 19:10 UTC | Jul 8, 20:40 UTC | 1h 30m |
| 2026-07-08 | - | Jul 8, 15:20 UTC | Jul 8, 17:10 UTC | 1h 50m |
| 2026-07-08 | - | Jul 8, 13:05 UTC | Jul 8, 14:25 UTC | 1h 20m |
| 2026-07-08 | KRK → AMS | Jul 8, 10:10 UTC | Jul 8, 11:50 UTC | 1h 40m |
| 2026-07-08 | - | Jul 8, 07:30 UTC | Jul 8, 09:00 UTC | 1h 30m |
| 2026-07-08 | - | Jul 8, 04:10 UTC | Jul 8, 06:00 UTC | 1h 50m |
| 2026-07-07 | - | Jul 7, 19:35 UTC | Jul 7, 21:00 UTC | 1h 25m |
| 2026-07-07 | - | Jul 7, 17:15 UTC | Jul 7, 18:25 UTC | 1h 10m |
| 2026-07-07 | - | Jul 7, 14:55 UTC | Jul 7, 15:55 UTC | 1h 0m |
| 2026-07-07 | - | Jul 7, 12:40 UTC | Jul 7, 14:00 UTC | 1h 20m |
| 2026-07-07 | - | Jul 7, 10:40 UTC | Jul 7, 11:50 UTC | 1h 10m |
| 2026-07-07 | GVA → AMS | Jul 7, 07:15 UTC | Jul 7, 08:35 UTC | 1h 20m |
| 2026-07-07 | AMS → GVA | Jul 7, 05:15 UTC | Jul 7, 06:20 UTC | 1h 5m |
| 2026-07-06 | - | Jul 6, 20:00 UTC | Jul 6, 20:40 UTC | 40m |
| 2026-07-06 | AMS → LHR | Jul 6, 17:45 UTC | Jul 6, 18:35 UTC | 50m |
| 2026-07-06 | MPL → AMS | Jul 6, 14:55 UTC | Jul 6, 16:30 UTC | 1h 35m |
| 2026-07-06 | - | Jul 6, 12:25 UTC | Jul 6, 13:50 UTC | 1h 25m |
| 2026-07-06 | PRG → AMS | Jul 6, 10:00 UTC | Jul 6, 11:15 UTC | 1h 15m |
Specifications
| Registration | PH-NXZ |
| Aircraft type | EMBRAER ERJ-190-400 (E295) |
| Mode-S code | 486954 · 22064524 (octal) |
Looking for transponder-level data? View the Mode-S 486954 page for country allocation, callsign history, and ADS-B signal details.
PH-NXZ frequently asked
What type of aircraft is PH-NXZ?
PH-NXZ is a EMBRAER ERJ-190-400 (ICAO type code E295).
What is the Mode-S transponder code for PH-NXZ?
PH-NXZ broadcasts on Mode-S (ICAO 24-bit) address 486954 (octal 22064524). View the transponder page.
What route does PH-NXZ typically fly?
PH-NXZ most frequently flies between AMS and FLR based on observed flights.
Where is PH-NXZ right now?
PH-NXZ is not currently being tracked; last seen 36m ago.