Not currently tracked · last seen 8d ago
- Flights observed
- 609 showing last 50
- Avg flight time
- 1h 2m
- Typical route
- AMS → GVA
- Last seen
- 8d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-05 | - | Jul 5, 19:15 UTC | Jul 5, 20:45 UTC | 1h 30m |
| 2026-07-05 | - | Jul 5, 17:05 UTC | Jul 5, 17:55 UTC | 50m |
| 2026-07-05 | - | Jul 5, 16:20 UTC | Jul 5, 16:55 UTC | 35m |
| 2026-07-05 | - | Jul 5, 15:10 UTC | Jul 5, 16:15 UTC | 1h 5m |
| 2026-07-05 | - | Jul 5, 12:30 UTC | Jul 5, 14:05 UTC | 1h 35m |
| 2026-07-05 | - | Jul 5, 10:20 UTC | Jul 5, 11:30 UTC | 1h 10m |
| 2026-07-05 | SOU → AMS | Jul 5, 08:35 UTC | Jul 5, 09:20 UTC | 45m |
| 2026-07-05 | AMS → SOU | Jul 5, 07:00 UTC | Jul 5, 07:50 UTC | 50m |
| 2026-07-05 | KRS → AMS | Jul 5, 04:50 UTC | Jul 5, 05:55 UTC | 1h 5m |
| 2026-07-04 | AMS → KRS | Jul 4, 19:55 UTC | Jul 4, 20:55 UTC | 1h 0m |
| 2026-07-04 | - | Jul 4, 17:25 UTC | Jul 4, 18:40 UTC | 1h 15m |
| 2026-07-04 | AMS → GVA | Jul 4, 15:25 UTC | Jul 4, 16:25 UTC | 1h 0m |
| 2026-07-04 | - | Jul 4, 12:40 UTC | Jul 4, 14:00 UTC | 1h 20m |
| 2026-07-04 | - | Jul 4, 10:20 UTC | Jul 4, 11:45 UTC | 1h 25m |
| 2026-07-04 | - | Jul 4, 08:25 UTC | Jul 4, 09:10 UTC | 45m |
| 2026-07-04 | - | Jul 4, 06:10 UTC | Jul 4, 07:10 UTC | 1h 0m |
| 2026-07-04 | LUX → AMS | Jul 4, 04:15 UTC | Jul 4, 05:00 UTC | 45m |
| 2026-07-03 | - | Jul 3, 20:35 UTC | Jul 3, 21:10 UTC | 35m |
| 2026-07-03 | GVA → AMS | Jul 3, 17:25 UTC | Jul 3, 18:40 UTC | 1h 15m |
| 2026-07-03 | - | Jul 3, 15:20 UTC | Jul 3, 16:30 UTC | 1h 10m |
| 2026-07-03 | - | Jul 3, 12:40 UTC | Jul 3, 14:10 UTC | 1h 30m |
| 2026-07-03 | - | Jul 3, 10:20 UTC | Jul 3, 11:40 UTC | 1h 20m |
| 2026-07-03 | - | Jul 3, 07:55 UTC | Jul 3, 09:15 UTC | 1h 20m |
| 2026-07-03 | - | Jul 3, 05:55 UTC | Jul 3, 07:10 UTC | 1h 15m |
| 2026-07-03 | HAJ → AMS | Jul 3, 04:15 UTC | Jul 3, 04:55 UTC | 40m |
| 2026-07-02 | - | Jul 2, 19:35 UTC | Jul 2, 20:15 UTC | 40m |
| 2026-07-02 | NUE → AMS | Jul 2, 17:05 UTC | Jul 2, 18:05 UTC | 1h 0m |
| 2026-07-02 | AMS → NUE | Jul 2, 15:25 UTC | Jul 2, 16:15 UTC | 50m |
| 2026-07-02 | - | Jul 2, 13:10 UTC | Jul 2, 14:20 UTC | 1h 10m |
| 2026-07-02 | AMS → GVA | Jul 2, 11:15 UTC | Jul 2, 12:20 UTC | 1h 5m |
| 2026-07-02 | - | Jul 2, 09:05 UTC | Jul 2, 10:05 UTC | 1h 0m |
| 2026-07-02 | - | Jul 2, 07:30 UTC | Jul 2, 08:15 UTC | 45m |
| 2026-07-02 | - | Jul 2, 04:15 UTC | Jul 2, 05:55 UTC | 1h 40m |
| 2026-07-01 | - | Jul 1, 19:15 UTC | Jul 1, 20:40 UTC | 1h 25m |
| 2026-07-01 | LPI → AMS | Jul 1, 16:55 UTC | Jul 1, 18:05 UTC | 1h 10m |
| 2026-07-01 | - | Jul 1, 15:00 UTC | Jul 1, 16:10 UTC | 1h 10m |
| 2026-07-01 | STR → AMS | Jul 1, 13:00 UTC | Jul 1, 13:55 UTC | 55m |
| 2026-07-01 | - | Jul 1, 10:55 UTC | Jul 1, 11:50 UTC | 55m |
| 2026-07-01 | - | Jul 1, 08:40 UTC | Jul 1, 09:40 UTC | 1h 0m |
| 2026-07-01 | - | Jul 1, 07:00 UTC | Jul 1, 07:55 UTC | 55m |
| 2026-07-01 | - | Jul 1, 04:20 UTC | Jul 1, 06:00 UTC | 1h 40m |
| 2026-06-30 | - | Jun 30, 19:10 UTC | Jun 30, 20:40 UTC | 1h 30m |
| 2026-06-30 | BRE → AMS | Jun 30, 16:40 UTC | Jun 30, 17:15 UTC | 35m |
| 2026-06-30 | - | Jun 30, 15:20 UTC | Jun 30, 15:50 UTC | 30m |
| 2026-06-30 | NCL → AMS | Jun 30, 13:10 UTC | Jun 30, 14:10 UTC | 1h 0m |
| 2026-06-30 | - | Jun 30, 11:20 UTC | Jun 30, 12:20 UTC | 1h 0m |
| 2026-06-30 | - | Jun 30, 09:20 UTC | Jun 30, 10:00 UTC | 40m |
| 2026-06-30 | - | Jun 30, 07:55 UTC | Jun 30, 08:30 UTC | 35m |
| 2026-06-29 | LCY → AMS | Jun 29, 20:19 UTC | Jun 29, 21:05 UTC | 45m |
| 2026-06-29 | AMS → LCY | Jun 29, 18:55 UTC | Jun 29, 19:29 UTC | 35m |
Specifications
| Registration | PH-EZE |
| Aircraft type | EMBRAER ERJ-190-100 (E190) |
| Mode-S code | 484B32 · 22045462 (octal) |
Looking for transponder-level data? View the Mode-S 484B32 page for country allocation, callsign history, and ADS-B signal details.
PH-EZE frequently asked
What type of aircraft is PH-EZE?
PH-EZE is a EMBRAER ERJ-190-100 (ICAO type code E190).
What is the Mode-S transponder code for PH-EZE?
PH-EZE broadcasts on Mode-S (ICAO 24-bit) address 484B32 (octal 22045462). View the transponder page.
What route does PH-EZE typically fly?
PH-EZE most frequently flies between AMS and GVA based on observed flights.
Where is PH-EZE right now?
PH-EZE is not currently being tracked; last seen 8d ago.