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