Not currently tracked · last seen 8h ago
- Flights observed
- 214 showing last 50
- Avg flight time
- 7h 20m
- Typical route
- CPH → CPH
- Last seen
- 8h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 16:55 UTC | Jul 13, 18:20 UTC | 1h 25m |
| 2026-07-13 | CPH → CPH | Jul 13, 10:55 UTC | Jul 13, 15:40 UTC | 4h 45m |
| 2026-07-13 | CPH → CPH | Jul 13, 04:35 UTC | Jul 13, 09:40 UTC | 5h 5m |
| 2026-07-12 | CPH → CPH | Jul 12, 16:45 UTC | Jul 12, 21:20 UTC | 4h 35m |
| 2026-07-12 | CPH → CPH | Jul 12, 10:35 UTC | Jul 12, 15:30 UTC | 4h 55m |
| 2026-07-12 | CPH → CPH | Jul 12, 04:30 UTC | Jul 12, 09:25 UTC | 4h 55m |
| 2026-07-11 | CPH → CPH | Jul 11, 17:10 UTC | Jul 11, 21:50 UTC | 4h 40m |
| 2026-07-11 | CPH → CPH | Jul 11, 10:50 UTC | Jul 11, 15:35 UTC | 4h 45m |
| 2026-07-11 | CPH → CPH | Jul 11, 04:25 UTC | Jul 11, 09:05 UTC | 4h 40m |
| 2026-07-10 | CPH → CPH | Jul 10, 16:50 UTC | Jul 10, 21:35 UTC | 4h 45m |
| 2026-07-10 | CPH → CPH | Jul 10, 10:45 UTC | Jul 10, 15:30 UTC | 4h 45m |
| 2026-07-09 | CPH → CPH | Jul 9, 17:05 UTC | Jul 10, 09:15 UTC | 16h 10m |
| 2026-07-09 | - | Jul 9, 10:55 UTC | Jul 9, 15:40 UTC | 4h 45m |
| 2026-07-08 | CPH → CPH | Jul 8, 17:25 UTC | Jul 9, 09:10 UTC | 15h 45m |
| 2026-07-08 | - | Jul 8, 10:45 UTC | Jul 8, 15:40 UTC | 4h 55m |
| 2026-07-07 | - | Jul 7, 16:50 UTC | Jul 8, 09:00 UTC | 16h 10m |
| 2026-07-07 | CPH → CPH | Jul 7, 10:40 UTC | Jul 7, 15:25 UTC | 4h 45m |
| 2026-07-06 | - | Jul 6, 16:50 UTC | Jul 7, 09:00 UTC | 16h 10m |
| 2026-07-06 | - | Jul 6, 10:55 UTC | Jul 6, 15:45 UTC | 4h 50m |
| 2026-07-06 | - | Jul 6, 04:35 UTC | Jul 6, 09:35 UTC | 5h 0m |
| 2026-07-05 | CPH → CPH | Jul 5, 17:10 UTC | Jul 5, 21:50 UTC | 4h 40m |
| 2026-07-05 | - | Jul 5, 11:20 UTC | Jul 5, 15:55 UTC | 4h 35m |
| 2026-07-05 | - | Jul 5, 04:45 UTC | Jul 5, 09:30 UTC | 4h 45m |
| 2026-07-04 | - | Jul 4, 16:50 UTC | Jul 4, 21:40 UTC | 4h 50m |
| 2026-07-04 | - | Jul 4, 10:40 UTC | Jul 4, 15:40 UTC | 5h 0m |
| 2026-07-04 | - | Jul 4, 04:40 UTC | Jul 4, 09:25 UTC | 4h 45m |
| 2026-07-03 | - | Jul 3, 17:10 UTC | Jul 3, 21:55 UTC | 4h 45m |
| 2026-07-03 | - | Jul 3, 11:00 UTC | Jul 3, 15:35 UTC | 4h 35m |
| 2026-07-02 | - | Jul 2, 16:45 UTC | Jul 3, 09:10 UTC | 16h 25m |
| 2026-07-02 | - | Jul 2, 10:45 UTC | Jul 2, 15:30 UTC | 4h 45m |
| 2026-07-01 | CPH → CPH | Jul 1, 17:05 UTC | Jul 2, 09:15 UTC | 16h 10m |
| 2026-07-01 | CPH → CPH | Jul 1, 10:40 UTC | Jul 1, 15:10 UTC | 4h 30m |
| 2026-06-30 | CPH → CPH | Jun 30, 16:50 UTC | Jul 1, 09:05 UTC | 16h 15m |
| 2026-06-30 | - | Jun 30, 10:30 UTC | Jun 30, 15:35 UTC | 5h 5m |
| 2026-06-29 | - | Jun 29, 23:05 UTC | Jun 30, 09:15 UTC | 10h 11m |
| 2026-06-29 | - | Jun 29, 16:50 UTC | Jun 29, 21:39 UTC | 4h 50m |
| 2026-06-29 | - | Jun 29, 10:34 UTC | Jun 29, 15:24 UTC | 4h 50m |
| 2026-06-29 | - | Jun 29, 04:34 UTC | Jun 29, 09:20 UTC | 4h 45m |
| 2026-06-28 | - | Jun 28, 21:40 UTC | Jun 29, 03:05 UTC | 5h 25m |
| 2026-06-28 | - | Jun 28, 15:29 UTC | Jun 28, 20:34 UTC | 5h 5m |
| 2026-06-28 | - | Jun 28, 09:34 UTC | Jun 28, 13:49 UTC | 4h 15m |
| 2026-06-27 | - | Jun 27, 17:04 UTC | Jun 27, 20:34 UTC | 3h 30m |
| 2026-06-27 | FAE → CPH | Jun 27, 10:40 UTC | Jun 27, 15:49 UTC | 5h 10m |
| 2026-06-26 | - | Jun 26, 16:54 UTC | Jun 27, 09:19 UTC | 16h 25m |
| 2026-06-26 | - | Jun 26, 10:39 UTC | Jun 26, 15:29 UTC | 4h 50m |
| 2026-06-25 | CPH → FAE | Jun 25, 17:05 UTC | Jun 26, 09:14 UTC | 16h 10m |
| 2026-06-25 | - | Jun 25, 10:50 UTC | Jun 25, 15:50 UTC | 5h 0m |
| 2026-06-24 | CPH → FAE | Jun 24, 17:10 UTC | Jun 25, 09:20 UTC | 16h 10m |
| 2026-06-24 | - | Jun 24, 10:55 UTC | Jun 24, 15:49 UTC | 4h 55m |
| 2026-06-23 | CPH → FAE | Jun 23, 16:54 UTC | Jun 24, 09:34 UTC | 16h 40m |
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 CPH based on observed flights.
Where is OY-RCM right now?
OY-RCM is not currently being tracked; last seen 8h ago.