Not currently tracked · last seen 5d ago
- Flights observed
- 74 showing last 50
- Avg flight time
- 3h 36m
- Typical route
- RMO → MXP
- Last seen
- 5d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-24 | - | May 24, 20:35 UTC | May 24, 21:35 UTC | 1h 0m |
| 2026-05-24 | - | May 24, 17:35 UTC | May 24, 19:25 UTC | 1h 50m |
| 2026-05-04 | SSH → RMO | May 4, 06:10 UTC | May 4, 13:10 UTC | 7h 0m |
| 2026-05-03 | LTN → RMO | May 3, 21:10 UTC | May 3, 23:45 UTC | 2h 35m |
| 2026-05-03 | RMO → LTN | May 3, 16:55 UTC | May 3, 19:50 UTC | 2h 55m |
| 2026-05-03 | - | May 3, 03:50 UTC | May 3, 11:05 UTC | 7h 15m |
| 2026-05-02 | - | May 2, 13:45 UTC | May 2, 15:40 UTC | 1h 55m |
| 2026-05-02 | - | May 2, 10:25 UTC | May 2, 12:05 UTC | 1h 40m |
| 2026-05-02 | AYT → RMO | May 2, 00:00 UTC | May 2, 01:25 UTC | 1h 25m |
| 2026-05-01 | HHN → RMO | May 1, 06:30 UTC | May 1, 22:50 UTC | 16h 20m |
| 2026-05-01 | RMO → HHN | May 1, 03:05 UTC | May 1, 05:10 UTC | 2h 5m |
| 2026-04-30 | - | Apr 30, 03:45 UTC | Apr 30, 11:05 UTC | 7h 20m |
| 2026-04-29 | AMS → RMO | Apr 29, 13:55 UTC | Apr 29, 15:55 UTC | 2h 0m |
| 2026-04-29 | RMO → AMS | Apr 29, 09:45 UTC | Apr 29, 12:15 UTC | 2h 30m |
| 2026-04-28 | - | Apr 28, 04:40 UTC | Apr 28, 05:35 UTC | 55m |
| 2026-04-27 | - | Apr 27, 21:50 UTC | Apr 27, 23:25 UTC | 1h 35m |
| 2026-04-26 | LTN → RMO | Apr 26, 21:15 UTC | Apr 26, 23:45 UTC | 2h 30m |
| 2026-04-26 | RMO → LTN | Apr 26, 16:50 UTC | Apr 26, 20:00 UTC | 3h 10m |
| 2026-04-26 | - | Apr 26, 04:50 UTC | Apr 26, 12:45 UTC | 7h 55m |
| 2026-04-25 | - | Apr 25, 12:50 UTC | Apr 26, 12:30 UTC | 23h 40m |
| 2026-04-25 | - | Apr 25, 09:30 UTC | Apr 25, 11:35 UTC | 2h 5m |
| 2026-04-25 | MUC → RMO | Apr 25, 06:15 UTC | Apr 25, 07:40 UTC | 1h 25m |
| 2026-04-25 | RMO → MUC | Apr 25, 03:10 UTC | Apr 25, 04:55 UTC | 1h 45m |
| 2026-04-24 | MXP → RMO | Apr 24, 14:00 UTC | Apr 24, 16:00 UTC | 2h 0m |
| 2026-04-23 | RMO → MXP | Apr 23, 21:45 UTC | Apr 24, 12:10 UTC | 14h 25m |
| 2026-04-23 | HRG → RMO | Apr 23, 04:15 UTC | Apr 23, 11:15 UTC | 7h 1m |
| 2026-04-22 | AMS → RMO | Apr 22, 14:10 UTC | Apr 22, 16:25 UTC | 2h 15m |
| 2026-04-22 | RMO → AMS | Apr 22, 09:35 UTC | Apr 22, 11:55 UTC | 2h 20m |
| 2026-04-21 | TBS → RMO | Apr 21, 22:50 UTC | Apr 22, 00:00 UTC | 1h 10m |
| 2026-04-21 | RMO → TBS | Apr 21, 20:35 UTC | Apr 21, 20:45 UTC | 10m |
| 2026-04-21 | RMO → TBS | Apr 21, 18:45 UTC | Apr 21, 19:20 UTC | 35m |
| 2026-04-20 | MXP → RMO | Apr 20, 13:55 UTC | Apr 20, 15:40 UTC | 1h 45m |
| 2026-04-19 | DUB → RMO | Apr 19, 22:30 UTC | Apr 20, 12:20 UTC | 13h 50m |
| 2026-04-19 | RMO → DUB | Apr 19, 17:30 UTC | Apr 19, 21:05 UTC | 3h 35m |
| 2026-04-19 | - | Apr 19, 03:40 UTC | Apr 19, 11:10 UTC | 7h 30m |
| 2026-04-18 | VRN → RMO | Apr 18, 20:20 UTC | Apr 18, 22:00 UTC | 1h 40m |
| 2026-04-18 | RMO → VRN | Apr 18, 17:10 UTC | Apr 18, 19:05 UTC | 1h 55m |
| 2026-04-18 | RMO → SSH | Apr 18, 08:25 UTC | Apr 18, 15:10 UTC | 6h 45m |
| 2026-04-18 | - | Apr 18, 04:45 UTC | Apr 18, 05:30 UTC | 45m |
| 2026-04-18 | - | Apr 18, 04:30 UTC | Apr 18, 05:20 UTC | 50m |
| 2026-04-17 | - | Apr 17, 15:20 UTC | Apr 17, 15:35 UTC | 15m |
| 2026-04-17 | - | Apr 17, 13:50 UTC | Apr 17, 15:15 UTC | 1h 24m |
| 2026-04-17 | RMO → MXP | Apr 17, 11:20 UTC | Apr 17, 12:00 UTC | 40m |
| 2026-04-17 | RMO → MXP | Apr 17, 10:20 UTC | Apr 17, 11:15 UTC | 55m |
| 2026-04-17 | - | Apr 17, 05:20 UTC | Apr 17, 05:30 UTC | 10m |
| 2026-04-17 | - | Apr 17, 04:40 UTC | Apr 17, 05:15 UTC | 35m |
| 2026-04-16 | HRG → RMO | Apr 16, 09:10 UTC | Apr 16, 11:04 UTC | 1h 55m |
| 2026-04-16 | HRG → RMO | Apr 16, 08:45 UTC | Apr 16, 09:05 UTC | 20m |
| 2026-04-16 | - | Apr 16, 05:09 UTC | Apr 16, 06:20 UTC | 1h 10m |
| 2026-04-16 | - | Apr 16, 04:14 UTC | Apr 16, 05:05 UTC | 50m |
Specifications
| Registration | ER-00008 |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 504E72 · 24047162 (octal) |
Looking for transponder-level data? View the Mode-S 504E72 page for country allocation, callsign history, and ADS-B signal details.
ER-00008 frequently asked
What type of aircraft is ER-00008?
ER-00008 is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for ER-00008?
ER-00008 broadcasts on Mode-S (ICAO 24-bit) address 504E72 (octal 24047162). View the transponder page.
What route does ER-00008 typically fly?
ER-00008 most frequently flies between RMO and MXP based on observed flights.
Where is ER-00008 right now?
ER-00008 is not currently being tracked; last seen 5d ago.