On the ground · transponder active
- Flights observed
- 260 showing last 50
- Avg flight time
- 2h 0m
- Typical route
- LGW → ARN
- Last seen
- 36m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | ARN → NCE | May 30, 05:45 UTC | May 30, 08:20 UTC | 2h 35m |
| 2026-05-29 | AMS → ARN | May 29, 22:55 UTC | May 30, 00:25 UTC | 1h 30m |
| 2026-05-29 | ARN → AMS | May 29, 18:05 UTC | May 29, 19:45 UTC | 1h 40m |
| 2026-05-29 | PRG → ARN | May 29, 14:30 UTC | May 29, 16:10 UTC | 1h 40m |
| 2026-05-29 | ARN → PRG | May 29, 11:50 UTC | May 29, 13:25 UTC | 1h 35m |
| 2026-05-29 | BSL → ARN | May 29, 08:45 UTC | May 29, 10:50 UTC | 2h 5m |
| 2026-05-29 | ARN → BSL | May 29, 05:25 UTC | May 29, 07:20 UTC | 1h 55m |
| 2026-05-28 | LGW → ARN | May 28, 19:40 UTC | May 28, 21:40 UTC | 2h 0m |
| 2026-05-28 | ARN → LGW | May 28, 15:55 UTC | May 28, 18:05 UTC | 2h 10m |
| 2026-05-28 | LGW → ARN | May 28, 12:35 UTC | May 28, 14:35 UTC | 2h 0m |
| 2026-05-28 | ARN → LGW | May 28, 09:15 UTC | May 28, 11:25 UTC | 2h 10m |
| 2026-05-28 | CPH → ARN | May 28, 06:55 UTC | May 28, 07:50 UTC | 55m |
| 2026-05-28 | CPH → ARN | May 28, 05:05 UTC | May 28, 05:55 UTC | 50m |
| 2026-05-27 | BCN → ARN | May 27, 18:30 UTC | May 27, 21:45 UTC | 3h 15m |
| 2026-05-27 | ARN → BCN | May 27, 14:10 UTC | May 27, 17:15 UTC | 3h 5m |
| 2026-05-27 | BUD → ARN | May 27, 11:05 UTC | May 27, 13:05 UTC | 2h 0m |
| 2026-05-27 | ARN → BUD | May 27, 09:55 UTC | May 27, 10:05 UTC | 10m |
| 2026-05-27 | ARN → BUD | May 27, 08:15 UTC | May 27, 09:25 UTC | 1h 10m |
| 2026-05-27 | OSL → ARN | May 27, 06:34 UTC | May 27, 07:15 UTC | 41m |
| 2026-05-27 | ARN → OSL | May 27, 05:04 UTC | May 27, 05:55 UTC | 50m |
| 2026-05-26 | ATH → ARN | May 26, 19:10 UTC | May 26, 22:35 UTC | 3h 25m |
| 2026-05-26 | ARN → ATH | May 26, 13:54 UTC | May 26, 16:59 UTC | 3h 5m |
| 2026-05-26 | LGW → ARN | May 26, 10:10 UTC | May 26, 12:00 UTC | 1h 50m |
| 2026-05-26 | ARN → LGW | May 26, 06:49 UTC | May 26, 09:04 UTC | 2h 15m |
| 2026-05-25 | NCE → ARN | May 25, 19:30 UTC | May 25, 22:00 UTC | 2h 30m |
| 2026-05-25 | ARN → NCE | May 25, 15:30 UTC | May 25, 18:15 UTC | 2h 45m |
| 2026-05-25 | AGP → ARN | May 25, 10:10 UTC | May 25, 14:00 UTC | 3h 50m |
| 2026-05-25 | ARN → AGP | May 25, 05:05 UTC | May 25, 09:00 UTC | 3h 55m |
| 2026-05-24 | EDI → ARN | May 24, 19:55 UTC | May 24, 21:40 UTC | 1h 45m |
| 2026-05-24 | ARN → EDI | May 24, 16:50 UTC | May 24, 19:00 UTC | 2h 10m |
| 2026-05-24 | LGW → ARN | May 24, 13:40 UTC | May 24, 15:40 UTC | 2h 0m |
| 2026-05-24 | ARN → LGW | May 24, 10:00 UTC | May 24, 12:20 UTC | 2h 20m |
| 2026-05-24 | UME → ARN | May 24, 08:00 UTC | May 24, 08:50 UTC | 50m |
| 2026-05-24 | ARN → UME | May 24, 06:25 UTC | May 24, 07:00 UTC | 35m |
| 2026-05-22 | PRG → ARN | May 22, 18:05 UTC | May 22, 19:50 UTC | 1h 45m |
| 2026-05-22 | ARN → PRG | May 22, 15:35 UTC | May 22, 17:10 UTC | 1h 35m |
| 2026-05-22 | HAM → ARN | May 22, 13:15 UTC | May 22, 14:30 UTC | 1h 15m |
| 2026-05-22 | ARN → HAM | May 22, 11:05 UTC | May 22, 12:20 UTC | 1h 15m |
| 2026-05-22 | MXP → ARN | May 22, 07:40 UTC | May 22, 10:10 UTC | 2h 29m |
| 2026-05-22 | ARN → MXP | May 22, 04:15 UTC | May 22, 06:30 UTC | 2h 15m |
| 2026-05-21 | HEL → ARN | May 21, 18:10 UTC | May 21, 18:50 UTC | 40m |
| 2026-05-21 | ARN → HEL | May 21, 16:40 UTC | May 21, 17:20 UTC | 40m |
| 2026-05-21 | HEL → ARN | May 21, 15:00 UTC | May 21, 15:45 UTC | 45m |
| 2026-05-21 | AGP → HEL | May 21, 09:25 UTC | May 21, 13:40 UTC | 4h 15m |
| 2026-05-21 | HEL → AGP | May 21, 03:45 UTC | May 21, 08:05 UTC | 4h 20m |
| 2026-05-20 | BCN → HEL | May 20, 19:40 UTC | May 20, 23:20 UTC | 3h 40m |
| 2026-05-20 | HEL → BCN | May 20, 14:50 UTC | May 20, 18:20 UTC | 3h 30m |
| 2026-05-20 | ARN → HEL | May 20, 12:55 UTC | May 20, 13:35 UTC | 40m |
| 2026-05-20 | PRG → ARN | May 20, 10:30 UTC | May 20, 12:00 UTC | 1h 30m |
| 2026-05-20 | ARN → PRG | May 20, 07:25 UTC | May 20, 09:10 UTC | 1h 45m |
Specifications
| Registration | SE-RTC |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 4ACA83 · 22545203 (octal) |
Looking for transponder-level data? View the Mode-S 4ACA83 page for country allocation, callsign history, and ADS-B signal details.
SE-RTC frequently asked
What type of aircraft is SE-RTC?
SE-RTC is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for SE-RTC?
SE-RTC broadcasts on Mode-S (ICAO 24-bit) address 4ACA83 (octal 22545203). View the transponder page.
What route does SE-RTC typically fly?
SE-RTC most frequently flies between LGW and ARN based on observed flights.
Where is SE-RTC right now?
SE-RTC is currently on the ground with its transponder active.