Not currently tracked · last seen Jul 26, 21:40 UTC
- Flights observed
- 541 showing last 50
- Avg flight time
- 2h 29m
- Typical route
- ARN → FCO
- Last seen
- Jul 26, 21:40 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | MXP → ARN | Jul 26, 19:15 UTC | Jul 26, 21:35 UTC | 2h 20m |
| 2026-07-26 | ARN → MXP | Jul 26, 15:30 UTC | Jul 26, 18:00 UTC | 2h 30m |
| 2026-07-26 | HAM → ARN | Jul 26, 13:00 UTC | Jul 26, 14:15 UTC | 1h 15m |
| 2026-07-26 | ARN → HAM | Jul 26, 10:55 UTC | Jul 26, 12:05 UTC | 1h 10m |
| 2026-07-26 | PRG → ARN | Jul 26, 08:20 UTC | Jul 26, 09:45 UTC | 1h 25m |
| 2026-07-26 | ARN → PRG | Jul 26, 05:35 UTC | Jul 26, 07:10 UTC | 1h 36m |
| 2026-07-25 | LCA → ARN | Jul 25, 18:25 UTC | Jul 25, 22:30 UTC | 4h 5m |
| 2026-07-25 | ARN → LCA | Jul 25, 13:10 UTC | Jul 25, 17:00 UTC | 3h 50m |
| 2026-07-25 | BIA → ARN | Jul 25, 09:20 UTC | Jul 25, 11:55 UTC | 2h 35m |
| 2026-07-25 | ARN → BIA | Jul 25, 05:20 UTC | Jul 25, 07:55 UTC | 2h 35m |
| 2026-07-24 | BER → ARN | Jul 24, 20:00 UTC | Jul 24, 21:25 UTC | 1h 25m |
| 2026-07-24 | ARN → BER | Jul 24, 17:55 UTC | Jul 24, 19:10 UTC | 1h 15m |
| 2026-07-24 | BUD → ARN | Jul 24, 15:05 UTC | Jul 24, 17:05 UTC | 2h 0m |
| 2026-07-24 | ARN → BUD | Jul 24, 12:15 UTC | Jul 24, 14:00 UTC | 1h 45m |
| 2026-07-24 | LYS → ARN | Jul 24, 08:30 UTC | Jul 24, 11:10 UTC | 2h 40m |
| 2026-07-24 | ARN → LYS | Jul 24, 05:00 UTC | Jul 24, 07:25 UTC | 2h 25m |
| 2026-07-23 | FCO → ARN | Jul 23, 18:20 UTC | Jul 23, 21:15 UTC | 2h 55m |
| 2026-07-23 | ARN → FCO | Jul 23, 14:25 UTC | Jul 23, 16:45 UTC | 2h 20m |
| 2026-07-23 | BCN → ARN | Jul 23, 09:25 UTC | Jul 23, 12:35 UTC | 3h 10m |
| 2026-07-23 | ARN → BCN | Jul 23, 05:15 UTC | Jul 23, 08:10 UTC | 2h 55m |
| 2026-07-22 | AMS → ARN | Jul 22, 19:55 UTC | Jul 22, 21:40 UTC | 1h 45m |
| 2026-07-22 | ARN → AMS | Jul 22, 17:10 UTC | Jul 22, 18:45 UTC | 1h 35m |
| 2026-07-22 | LLA → ARN | Jul 22, 15:10 UTC | Jul 22, 16:10 UTC | 1h 0m |
| 2026-07-22 | ARN → LLA | Jul 22, 13:20 UTC | Jul 22, 14:10 UTC | 50m |
| 2026-07-22 | SPU → ARN | Jul 22, 10:20 UTC | Jul 22, 11:25 UTC | 1h 5m |
| 2026-07-21 | BIO → ARN | Jul 21, 15:20 UTC | Jul 21, 18:20 UTC | 3h 0m |
| 2026-07-21 | ARN → BIO | Jul 21, 11:05 UTC | Jul 21, 13:50 UTC | 2h 45m |
| 2026-07-21 | MUC → ARN | Jul 21, 08:25 UTC | Jul 21, 10:10 UTC | 1h 45m |
| 2026-07-21 | ARN → MUC | Jul 21, 05:25 UTC | Jul 21, 07:20 UTC | 1h 55m |
| 2026-07-20 | - | Jul 20, 18:55 UTC | Jul 20, 22:45 UTC | 3h 50m |
| 2026-07-20 | ARN → AGP | Jul 20, 13:55 UTC | Jul 20, 17:45 UTC | 3h 50m |
| 2026-07-20 | - | Jul 20, 09:20 UTC | Jul 20, 12:00 UTC | 2h 40m |
| 2026-07-20 | ARN → FCO | Jul 20, 05:05 UTC | Jul 20, 07:55 UTC | 2h 50m |
| 2026-07-19 | NCE → ARN | Jul 19, 20:05 UTC | Jul 19, 22:30 UTC | 2h 25m |
| 2026-07-19 | ARN → NCE | Jul 19, 15:40 UTC | Jul 19, 18:20 UTC | 2h 40m |
| 2026-07-19 | - | Jul 19, 14:05 UTC | Jul 19, 14:30 UTC | 25m |
| 2026-07-19 | ARN → VBY | Jul 19, 12:50 UTC | Jul 19, 13:10 UTC | 20m |
| 2026-07-19 | LGW → ARN | Jul 19, 09:50 UTC | Jul 19, 11:50 UTC | 2h 0m |
| 2026-07-19 | ARN → LGW | Jul 19, 06:15 UTC | Jul 19, 08:25 UTC | 2h 10m |
| 2026-07-18 | CHQ → ARN | Jul 18, 19:00 UTC | Jul 18, 22:25 UTC | 3h 25m |
| 2026-07-18 | ARN → CHQ | Jul 18, 13:30 UTC | Jul 18, 17:00 UTC | 3h 30m |
| 2026-07-18 | HEL → ARN | Jul 18, 11:15 UTC | Jul 18, 12:00 UTC | 45m |
| 2026-07-18 | PSA → HEL | Jul 18, 07:40 UTC | Jul 18, 10:25 UTC | 2h 45m |
| 2026-07-18 | HEL → PSA | Jul 18, 03:30 UTC | Jul 18, 06:35 UTC | 3h 5m |
| 2026-07-17 | - | Jul 17, 19:40 UTC | Jul 17, 23:35 UTC | 3h 55m |
| 2026-07-17 | - | Jul 17, 13:55 UTC | Jul 17, 18:34 UTC | 4h 40m |
| 2026-07-17 | LCA → HEL | Jul 17, 08:40 UTC | Jul 17, 12:50 UTC | 4h 10m |
| 2026-07-17 | HEL → LCA | Jul 17, 03:10 UTC | Jul 17, 07:05 UTC | 3h 55m |
| 2026-07-16 | - | Jul 16, 19:25 UTC | Jul 16, 23:29 UTC | 4h 5m |
| 2026-07-16 | - | Jul 16, 13:20 UTC | Jul 16, 17:49 UTC | 4h 30m |
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 ARN and FCO based on observed flights.
Where is SE-RTC right now?
SE-RTC is not currently being tracked; last seen Jul 26, 21:40 UTC.