Not currently tracked · last seen 6h ago
- Flights observed
- 448 showing last 50
- Avg flight time
- 1h 41m
- Typical route
- OSL → SVG
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 20:30 UTC | Jul 13, 21:10 UTC | 40m |
| 2026-07-13 | OSL → SVG | Jul 13, 19:15 UTC | Jul 13, 19:55 UTC | 40m |
| 2026-07-13 | - | Jul 13, 17:50 UTC | Jul 13, 18:25 UTC | 35m |
| 2026-07-13 | OSL → SVG | Jul 13, 15:30 UTC | Jul 13, 16:05 UTC | 35m |
| 2026-07-12 | - | Jul 12, 18:40 UTC | Jul 12, 19:55 UTC | 1h 15m |
| 2026-07-12 | - | Jul 12, 16:15 UTC | Jul 12, 17:30 UTC | 1h 15m |
| 2026-07-12 | - | Jul 12, 14:10 UTC | Jul 12, 15:30 UTC | 1h 20m |
| 2026-07-12 | - | Jul 12, 11:45 UTC | Jul 12, 12:55 UTC | 1h 10m |
| 2026-07-12 | - | Jul 12, 08:50 UTC | Jul 12, 10:45 UTC | 1h 55m |
| 2026-07-12 | - | Jul 12, 05:30 UTC | Jul 12, 07:35 UTC | 2h 5m |
| 2026-07-11 | ALC → OSL | Jul 11, 18:35 UTC | Jul 11, 21:50 UTC | 3h 15m |
| 2026-07-11 | OSL → ALC | Jul 11, 14:05 UTC | Jul 11, 17:30 UTC | 3h 25m |
| 2026-07-11 | - | Jul 11, 12:20 UTC | Jul 11, 13:05 UTC | 45m |
| 2026-07-11 | - | Jul 11, 08:15 UTC | Jul 11, 11:05 UTC | 2h 50m |
| 2026-07-11 | - | Jul 11, 04:01 UTC | Jul 11, 06:55 UTC | 2h 55m |
| 2026-07-10 | - | Jul 10, 19:05 UTC | Jul 10, 21:30 UTC | 2h 25m |
| 2026-07-10 | - | Jul 10, 15:25 UTC | Jul 10, 17:55 UTC | 2h 30m |
| 2026-07-10 | CPH → SVG | Jul 10, 13:25 UTC | Jul 10, 14:15 UTC | 50m |
| 2026-07-10 | - | Jul 10, 11:40 UTC | Jul 10, 12:35 UTC | 55m |
| 2026-07-10 | - | Jul 10, 08:40 UTC | Jul 10, 10:45 UTC | 2h 5m |
| 2026-07-10 | - | Jul 10, 05:30 UTC | Jul 10, 07:30 UTC | 2h 0m |
| 2026-07-09 | - | Jul 9, 19:20 UTC | Jul 9, 20:00 UTC | 40m |
| 2026-07-09 | - | Jul 9, 17:55 UTC | Jul 9, 18:35 UTC | 40m |
| 2026-07-09 | OSL → ARN | Jul 9, 16:30 UTC | Jul 9, 17:10 UTC | 40m |
| 2026-07-09 | ARN → OSL | Jul 9, 15:05 UTC | Jul 9, 15:45 UTC | 40m |
| 2026-07-09 | BER → ARN | Jul 9, 11:35 UTC | Jul 9, 12:55 UTC | 1h 20m |
| 2026-07-09 | ARN → BER | Jul 9, 09:30 UTC | Jul 9, 10:40 UTC | 1h 10m |
| 2026-07-09 | - | Jul 9, 07:30 UTC | Jul 9, 08:25 UTC | 55m |
| 2026-07-09 | - | Jul 9, 05:35 UTC | Jul 9, 06:35 UTC | 1h 0m |
| 2026-07-08 | LGW → ARN | Jul 8, 19:10 UTC | Jul 8, 21:10 UTC | 2h 0m |
| 2026-07-08 | ARN → LGW | Jul 8, 15:40 UTC | Jul 8, 17:45 UTC | 2h 5m |
| 2026-07-08 | LGW → ARN | Jul 8, 12:20 UTC | Jul 8, 14:35 UTC | 2h 15m |
| 2026-07-08 | ARN → LGW | Jul 8, 09:00 UTC | Jul 8, 10:55 UTC | 1h 55m |
| 2026-07-08 | - | Jul 8, 06:55 UTC | Jul 8, 07:40 UTC | 45m |
| 2026-07-08 | ARN → UME | Jul 8, 05:25 UTC | Jul 8, 06:00 UTC | 35m |
| 2026-07-07 | - | Jul 7, 21:40 UTC | Jul 7, 21:55 UTC | 15m |
| 2026-07-07 | - | Jul 7, 19:15 UTC | Jul 7, 21:20 UTC | 2h 5m |
| 2026-07-07 | ARN → NCE | Jul 7, 15:30 UTC | Jul 7, 18:10 UTC | 2h 40m |
| 2026-07-07 | - | Jul 7, 10:15 UTC | Jul 7, 14:20 UTC | 4h 5m |
| 2026-07-07 | ARN → FAO | Jul 7, 05:10 UTC | Jul 7, 09:10 UTC | 4h 0m |
| 2026-07-06 | NCE → ARN | Jul 6, 19:55 UTC | Jul 6, 22:30 UTC | 2h 35m |
| 2026-07-06 | ARN → NCE | Jul 6, 16:20 UTC | Jul 6, 18:50 UTC | 2h 30m |
| 2026-07-06 | BUD → ARN | Jul 6, 13:25 UTC | Jul 6, 15:25 UTC | 2h 0m |
| 2026-07-06 | ARN → BUD | Jul 6, 09:40 UTC | Jul 6, 11:25 UTC | 1h 45m |
| 2026-07-06 | BER → ARN | Jul 6, 07:25 UTC | Jul 6, 08:45 UTC | 1h 20m |
| 2026-07-06 | ARN → BER | Jul 6, 05:05 UTC | Jul 6, 06:20 UTC | 1h 15m |
| 2026-07-05 | MXP → ARN | Jul 5, 20:05 UTC | Jul 5, 22:25 UTC | 2h 20m |
| 2026-07-05 | ARN → MXP | Jul 5, 15:40 UTC | Jul 5, 18:05 UTC | 2h 25m |
| 2026-07-05 | HAM → ARN | Jul 5, 13:05 UTC | Jul 5, 14:30 UTC | 1h 25m |
| 2026-07-05 | ARN → HAM | Jul 5, 10:50 UTC | Jul 5, 12:05 UTC | 1h 15m |
Specifications
| Registration | SE-RTU |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 4ACA95 · 22545225 (octal) |
Looking for transponder-level data? View the Mode-S 4ACA95 page for country allocation, callsign history, and ADS-B signal details.
SE-RTU frequently asked
What type of aircraft is SE-RTU?
SE-RTU is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for SE-RTU?
SE-RTU broadcasts on Mode-S (ICAO 24-bit) address 4ACA95 (octal 22545225). View the transponder page.
What route does SE-RTU typically fly?
SE-RTU most frequently flies between OSL and SVG based on observed flights.
Where is SE-RTU right now?
SE-RTU is not currently being tracked; last seen 6h ago.