On the ground · transponder active
- Flights observed
- 515 showing last 50
- Avg flight time
- 1h 51m
- Typical route
- OSL → ARN
- Last seen
- 19m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 13:20 UTC | Jul 14, 14:00 UTC | 40m |
| 2026-07-14 | OSL → ARN | Jul 14, 10:25 UTC | Jul 14, 11:10 UTC | 45m |
| 2026-07-14 | - | Jul 14, 08:45 UTC | Jul 14, 09:25 UTC | 40m |
| 2026-07-14 | OSL → ARN | Jul 14, 06:55 UTC | Jul 14, 07:35 UTC | 40m |
| 2026-07-14 | ARN → OSL | Jul 14, 05:15 UTC | Jul 14, 05:55 UTC | 40m |
| 2026-07-13 | - | Jul 13, 19:10 UTC | Jul 13, 21:15 UTC | 2h 5m |
| 2026-07-13 | - | Jul 13, 15:35 UTC | Jul 13, 17:45 UTC | 2h 10m |
| 2026-07-13 | CPH → ARN | Jul 13, 13:45 UTC | Jul 13, 14:40 UTC | 55m |
| 2026-07-13 | - | Jul 13, 09:35 UTC | Jul 13, 11:50 UTC | 2h 15m |
| 2026-07-13 | - | Jul 13, 06:05 UTC | Jul 13, 08:10 UTC | 2h 5m |
| 2026-07-12 | NCE → CPH | Jul 12, 12:55 UTC | Jul 12, 14:50 UTC | 1h 55m |
| 2026-07-12 | CPH → NCE | Jul 12, 09:35 UTC | Jul 12, 11:40 UTC | 2h 5m |
| 2026-07-12 | ARN → CPH | Jul 12, 07:10 UTC | Jul 12, 08:10 UTC | 1h 0m |
| 2026-07-12 | CPH → ARN | Jul 12, 05:20 UTC | Jul 12, 06:10 UTC | 50m |
| 2026-07-11 | CPH → CPH | Jul 11, 16:00 UTC | Jul 11, 20:20 UTC | 4h 20m |
| 2026-07-11 | - | Jul 11, 10:45 UTC | Jul 11, 13:30 UTC | 2h 45m |
| 2026-07-11 | - | Jul 11, 06:25 UTC | Jul 11, 09:05 UTC | 2h 40m |
| 2026-07-11 | - | Jul 11, 04:01 UTC | Jul 11, 04:50 UTC | 50m |
| 2026-07-10 | CPH → OSL | Jul 10, 21:35 UTC | Jul 10, 22:30 UTC | 55m |
| 2026-07-10 | ATH → CPH | Jul 10, 16:55 UTC | Jul 10, 20:00 UTC | 3h 5m |
| 2026-07-10 | CPH → ATH | Jul 10, 13:05 UTC | Jul 10, 15:45 UTC | 2h 40m |
| 2026-07-10 | ZRH → CPH | Jul 10, 08:45 UTC | Jul 10, 10:15 UTC | 1h 30m |
| 2026-07-10 | CPH → ZRH | Jul 10, 06:10 UTC | Jul 10, 07:35 UTC | 1h 25m |
| 2026-07-09 | - | Jul 9, 18:55 UTC | Jul 9, 21:25 UTC | 2h 30m |
| 2026-07-09 | CPH → VAR | Jul 9, 15:10 UTC | Jul 9, 17:10 UTC | 2h 0m |
| 2026-07-09 | - | Jul 9, 09:25 UTC | Jul 9, 12:55 UTC | 3h 30m |
| 2026-07-09 | - | Jul 9, 05:25 UTC | Jul 9, 08:10 UTC | 2h 45m |
| 2026-07-08 | FLR → CPH | Jul 8, 18:20 UTC | Jul 8, 20:25 UTC | 2h 5m |
| 2026-07-08 | - | Jul 8, 15:20 UTC | Jul 8, 17:00 UTC | 1h 40m |
| 2026-07-08 | OSL → CPH | Jul 8, 13:20 UTC | Jul 8, 14:05 UTC | 45m |
| 2026-07-08 | CPH → OSL | Jul 8, 11:25 UTC | Jul 8, 12:20 UTC | 55m |
| 2026-07-08 | AMS → CPH | Jul 8, 09:10 UTC | Jul 8, 10:15 UTC | 1h 5m |
| 2026-07-08 | - | Jul 8, 06:25 UTC | Jul 8, 07:30 UTC | 1h 5m |
| 2026-07-08 | OSL → CPH | Jul 8, 04:10 UTC | Jul 8, 04:55 UTC | 45m |
| 2026-07-07 | BCN → OSL | Jul 7, 16:10 UTC | Jul 7, 19:15 UTC | 3h 5m |
| 2026-07-07 | OSL → BCN | Jul 7, 11:25 UTC | Jul 7, 14:15 UTC | 2h 50m |
| 2026-07-07 | ARN → OSL | Jul 7, 08:50 UTC | Jul 7, 09:40 UTC | 50m |
| 2026-07-07 | OSL → ARN | Jul 7, 07:05 UTC | Jul 7, 07:45 UTC | 40m |
| 2026-07-07 | ARN → OSL | Jul 7, 05:15 UTC | Jul 7, 06:00 UTC | 45m |
| 2026-07-06 | - | Jul 6, 14:10 UTC | Jul 6, 15:30 UTC | 1h 20m |
| 2026-07-06 | - | Jul 6, 12:00 UTC | Jul 6, 13:10 UTC | 1h 10m |
| 2026-07-06 | - | Jul 6, 08:40 UTC | Jul 6, 10:45 UTC | 2h 5m |
| 2026-07-06 | ARN → CDG | Jul 6, 05:05 UTC | Jul 6, 07:20 UTC | 2h 15m |
| 2026-07-05 | MAN → ARN | Jul 5, 19:35 UTC | Jul 5, 21:25 UTC | 1h 50m |
| 2026-07-05 | ARN → MAN | Jul 5, 16:20 UTC | Jul 5, 18:35 UTC | 2h 15m |
| 2026-07-05 | RHO → ARN | Jul 5, 09:25 UTC | Jul 5, 13:20 UTC | 3h 55m |
| 2026-07-05 | ARN → RHO | Jul 5, 04:15 UTC | Jul 5, 07:35 UTC | 3h 20m |
| 2026-07-04 | - | Jul 4, 17:10 UTC | Jul 4, 21:05 UTC | 3h 55m |
| 2026-07-04 | - | Jul 4, 12:35 UTC | Jul 4, 16:10 UTC | 3h 35m |
| 2026-07-04 | - | Jul 4, 10:05 UTC | Jul 4, 11:00 UTC | 55m |
Specifications
| Registration | SE-ROP |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 4AC9F0 · 22544760 (octal) |
Looking for transponder-level data? View the Mode-S 4AC9F0 page for country allocation, callsign history, and ADS-B signal details.
SE-ROP frequently asked
What type of aircraft is SE-ROP?
SE-ROP is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for SE-ROP?
SE-ROP broadcasts on Mode-S (ICAO 24-bit) address 4AC9F0 (octal 22544760). View the transponder page.
What route does SE-ROP typically fly?
SE-ROP most frequently flies between OSL and ARN based on observed flights.
Where is SE-ROP right now?
SE-ROP is currently on the ground with its transponder active.