Not currently tracked · last seen 7h ago
- Flights observed
- 113 showing last 50
- Avg flight time
- 8h 34m
- Typical route
- CPH → FAE
- Last seen
- 7h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | CPH → FAE | May 29, 16:40 UTC | May 29, 18:05 UTC | 1h 25m |
| 2026-05-29 | FAE → CPH | May 29, 10:45 UTC | May 29, 15:40 UTC | 4h 55m |
| 2026-05-29 | FAE → CPH | May 29, 08:00 UTC | May 29, 09:20 UTC | 1h 20m |
| 2026-05-26 | CPH → FAE | May 26, 19:15 UTC | May 26, 20:50 UTC | 1h 35m |
| 2026-05-26 | CPH → FAE | May 26, 10:50 UTC | May 26, 15:29 UTC | 4h 40m |
| 2026-05-26 | CPH → FAE | May 26, 04:45 UTC | May 26, 09:45 UTC | 5h 0m |
| 2026-05-25 | CPH → FAE | May 25, 17:00 UTC | May 25, 21:30 UTC | 4h 30m |
| 2026-05-25 | CPH → FAE | May 25, 11:00 UTC | May 25, 15:50 UTC | 4h 50m |
| 2026-05-25 | FAE → CPH | May 25, 08:20 UTC | May 25, 09:35 UTC | 1h 15m |
| 2026-05-23 | CPH → FAE | May 23, 16:50 UTC | May 23, 18:25 UTC | 1h 35m |
| 2026-05-23 | CPH → FAE | May 23, 10:55 UTC | May 23, 15:35 UTC | 4h 40m |
| 2026-05-22 | CPH → FAE | May 22, 17:05 UTC | May 23, 09:20 UTC | 16h 14m |
| 2026-05-22 | CPH → FAE | May 22, 10:40 UTC | May 22, 15:55 UTC | 5h 15m |
| 2026-05-21 | CPH → FAE | May 21, 16:40 UTC | May 22, 09:15 UTC | 16h 35m |
| 2026-05-21 | CPH → FAE | May 21, 10:40 UTC | May 21, 15:30 UTC | 4h 50m |
| 2026-05-20 | CPH → FAE | May 20, 16:50 UTC | May 21, 09:15 UTC | 16h 25m |
| 2026-05-20 | FAE → CPH | May 20, 10:40 UTC | May 20, 15:30 UTC | 4h 50m |
| 2026-05-19 | FAE → CPH | May 19, 16:55 UTC | May 20, 09:25 UTC | 16h 31m |
| 2026-05-19 | FAE → CPH | May 19, 10:45 UTC | May 19, 15:30 UTC | 4h 45m |
| 2026-05-18 | CPH → FAE | May 18, 16:55 UTC | May 19, 09:15 UTC | 16h 19m |
| 2026-05-18 | FAE → CPH | May 18, 10:35 UTC | May 18, 15:30 UTC | 4h 55m |
| 2026-05-17 | FAE → CPH | May 17, 16:50 UTC | May 18, 09:15 UTC | 16h 25m |
| 2026-05-17 | FAE → CPH | May 17, 10:35 UTC | May 17, 15:31 UTC | 4h 55m |
| 2026-05-16 | FAE → CPH | May 16, 16:35 UTC | May 17, 09:15 UTC | 16h 40m |
| 2026-05-16 | FAE → CPH | May 16, 10:31 UTC | May 16, 15:31 UTC | 5h 0m |
| 2026-05-15 | FAE → CPH | May 15, 16:40 UTC | May 16, 09:10 UTC | 16h 31m |
| 2026-05-15 | FAE → CPH | May 15, 10:30 UTC | May 15, 15:25 UTC | 4h 54m |
| 2026-05-14 | FAE → CPH | May 14, 16:50 UTC | May 15, 09:10 UTC | 16h 20m |
| 2026-05-14 | FAE → CPH | May 14, 10:35 UTC | May 14, 15:40 UTC | 5h 5m |
| 2026-05-13 | FAE → CPH | May 13, 17:00 UTC | May 14, 09:25 UTC | 16h 25m |
| 2026-05-13 | FAE → CPH | May 13, 10:40 UTC | May 13, 15:40 UTC | 5h 0m |
| 2026-05-13 | FAE → CPH | May 13, 08:05 UTC | May 13, 09:20 UTC | 1h 15m |
| 2026-05-11 | CPH → FAE | May 11, 16:45 UTC | May 11, 18:10 UTC | 1h 25m |
| 2026-05-11 | CPH → FAE | May 11, 10:45 UTC | May 11, 15:30 UTC | 4h 45m |
| 2026-05-10 | FAE → CPH | May 10, 16:44 UTC | May 11, 09:15 UTC | 16h 30m |
| 2026-05-10 | CPH → FAE | May 10, 10:30 UTC | May 10, 15:24 UTC | 4h 55m |
| 2026-05-10 | FAE → CPH | May 10, 07:50 UTC | May 10, 09:10 UTC | 1h 20m |
| 2026-05-09 | FAE → CPH | May 9, 11:20 UTC | May 10, 09:10 UTC | 21h 50m |
| 2026-05-09 | CPH → FAE | May 9, 10:40 UTC | May 10, 09:10 UTC | 22h 30m |
| 2026-05-08 | CPH → FAE | May 8, 16:55 UTC | May 9, 09:15 UTC | 16h 20m |
| 2026-05-08 | FAE → CPH | May 8, 10:35 UTC | May 8, 15:25 UTC | 4h 50m |
| 2026-05-07 | FAE → CPH | May 7, 17:35 UTC | May 8, 09:14 UTC | 15h 40m |
| 2026-05-07 | CPH → FAE | May 7, 10:55 UTC | May 7, 16:05 UTC | 5h 10m |
| 2026-05-06 | FAE → CPH | May 6, 17:40 UTC | May 7, 09:30 UTC | 15h 50m |
| 2026-05-06 | CPH → FAE | May 6, 11:25 UTC | May 6, 16:15 UTC | 4h 50m |
| 2026-05-05 | FAE → CPH | May 5, 23:05 UTC | May 6, 09:45 UTC | 10h 40m |
| 2026-05-05 | CPH → FAE | May 5, 17:10 UTC | May 5, 22:05 UTC | 4h 55m |
| 2026-05-05 | CPH → FAE | May 5, 10:55 UTC | May 5, 15:45 UTC | 4h 50m |
| 2026-05-04 | CPH → FAE | May 4, 17:10 UTC | May 5, 09:25 UTC | 16h 16m |
| 2026-05-04 | CPH → FAE | May 4, 10:45 UTC | May 4, 15:50 UTC | 5h 5m |
Specifications
| Registration | OY-RCM |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 45C86D · 21344155 (octal) |
Looking for transponder-level data? View the Mode-S 45C86D page for country allocation, callsign history, and ADS-B signal details.
OY-RCM frequently asked
What type of aircraft is OY-RCM?
OY-RCM is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for OY-RCM?
OY-RCM broadcasts on Mode-S (ICAO 24-bit) address 45C86D (octal 21344155). View the transponder page.
What route does OY-RCM typically fly?
OY-RCM most frequently flies between CPH and FAE based on observed flights.
Where is OY-RCM right now?
OY-RCM is not currently being tracked; last seen 7h ago.