Not currently tracked · last seen 28m ago
- Flights observed
- 357 showing last 50
- Avg flight time
- 2h 58m
- Typical route
- PRG → PRG
- Last seen
- 28m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 06:10 UTC | Jul 14, 09:05 UTC | 2h 55m |
| 2026-07-13 | - | Jul 13, 23:25 UTC | Jul 14, 06:05 UTC | 6h 40m |
| 2026-07-13 | - | Jul 13, 20:05 UTC | Jul 13, 21:55 UTC | 1h 50m |
| 2026-07-13 | - | Jul 13, 16:45 UTC | Jul 13, 18:10 UTC | 1h 25m |
| 2026-07-13 | - | Jul 13, 13:15 UTC | Jul 13, 14:15 UTC | 1h 0m |
| 2026-07-13 | - | Jul 13, 10:50 UTC | Jul 13, 12:00 UTC | 1h 10m |
| 2026-07-13 | - | Jul 13, 06:45 UTC | Jul 13, 09:10 UTC | 2h 25m |
| 2026-07-13 | - | Jul 13, 03:10 UTC | Jul 13, 05:25 UTC | 2h 15m |
| 2026-07-12 | - | Jul 12, 19:10 UTC | Jul 12, 23:05 UTC | 3h 55m |
| 2026-07-12 | - | Jul 12, 12:35 UTC | Jul 12, 17:01 UTC | 4h 25m |
| 2026-07-12 | PRG → PRG | Jul 12, 01:20 UTC | Jul 12, 11:01 UTC | 9h 40m |
| 2026-07-11 | - | Jul 11, 21:20 UTC | Jul 11, 23:10 UTC | 1h 50m |
| 2026-07-11 | - | Jul 11, 18:15 UTC | Jul 11, 20:00 UTC | 1h 45m |
| 2026-07-11 | - | Jul 11, 14:35 UTC | Jul 11, 17:00 UTC | 2h 25m |
| 2026-07-11 | - | Jul 11, 10:50 UTC | Jul 11, 13:10 UTC | 2h 20m |
| 2026-07-10 | PRG → PRG | Jul 10, 23:05 UTC | Jul 11, 08:15 UTC | 9h 10m |
| 2026-07-10 | - | Jul 10, 19:50 UTC | Jul 10, 21:30 UTC | 1h 40m |
| 2026-07-10 | - | Jul 10, 16:45 UTC | Jul 10, 18:10 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 12:35 UTC | Jul 10, 14:05 UTC | 1h 30m |
| 2026-07-10 | PRG → FCO | Jul 10, 09:45 UTC | Jul 10, 11:10 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 05:45 UTC | Jul 10, 08:25 UTC | 2h 40m |
| 2026-07-10 | - | Jul 10, 02:15 UTC | Jul 10, 04:25 UTC | 2h 10m |
| 2026-07-09 | OPO → PRG | Jul 9, 14:35 UTC | Jul 9, 17:15 UTC | 2h 40m |
| 2026-07-09 | PRG → OPO | Jul 9, 10:10 UTC | Jul 9, 13:00 UTC | 2h 50m |
| 2026-07-08 | PRG → PRG | Jul 8, 23:20 UTC | Jul 9, 08:45 UTC | 9h 25m |
| 2026-07-08 | - | Jul 8, 19:40 UTC | Jul 8, 21:35 UTC | 1h 55m |
| 2026-07-08 | - | Jul 8, 17:15 UTC | Jul 8, 18:40 UTC | 1h 25m |
| 2026-07-08 | - | Jul 8, 15:45 UTC | Jul 8, 16:05 UTC | 20m |
| 2026-07-08 | - | Jul 8, 13:10 UTC | Jul 8, 14:50 UTC | 1h 40m |
| 2026-07-08 | PRG → BOJ | Jul 8, 10:25 UTC | Jul 8, 12:10 UTC | 1h 45m |
| 2026-07-07 | RMF → PRG | Jul 7, 23:20 UTC | Jul 8, 08:55 UTC | 9h 35m |
| 2026-07-07 | - | Jul 7, 18:00 UTC | Jul 7, 21:20 UTC | 3h 20m |
| 2026-07-07 | - | Jul 7, 17:05 UTC | Jul 7, 17:15 UTC | 10m |
| 2026-07-07 | - | Jul 7, 10:55 UTC | Jul 7, 15:25 UTC | 4h 30m |
| 2026-07-06 | PRG → PRG | Jul 6, 23:15 UTC | Jul 7, 08:20 UTC | 9h 5m |
| 2026-07-06 | - | Jul 6, 20:10 UTC | Jul 6, 22:05 UTC | 1h 55m |
| 2026-07-06 | PRG → BOJ | Jul 6, 17:00 UTC | Jul 6, 18:50 UTC | 1h 50m |
| 2026-07-06 | - | Jul 6, 13:45 UTC | Jul 6, 15:50 UTC | 2h 5m |
| 2026-07-06 | PRG → EFL | Jul 6, 10:45 UTC | Jul 6, 12:45 UTC | 2h 0m |
| 2026-07-06 | - | Jul 6, 06:50 UTC | Jul 6, 09:15 UTC | 2h 25m |
| 2026-07-06 | - | Jul 6, 02:55 UTC | Jul 6, 04:55 UTC | 2h 0m |
| 2026-07-05 | RHO → PRG | Jul 5, 20:45 UTC | Jul 5, 23:25 UTC | 2h 40m |
| 2026-07-05 | PRG → RHO | Jul 5, 16:45 UTC | Jul 5, 19:15 UTC | 2h 30m |
| 2026-07-05 | - | Jul 5, 12:50 UTC | Jul 5, 14:50 UTC | 2h 0m |
| 2026-07-05 | - | Jul 5, 10:15 UTC | Jul 5, 11:55 UTC | 1h 40m |
| 2026-07-05 | - | Jul 5, 07:05 UTC | Jul 5, 08:55 UTC | 1h 50m |
| 2026-07-05 | PRG → BOJ | Jul 5, 04:15 UTC | Jul 5, 06:00 UTC | 1h 45m |
| 2026-07-04 | AYT → PRG | Jul 4, 22:20 UTC | Jul 5, 01:15 UTC | 2h 55m |
| 2026-07-04 | KLV → AYT | Jul 4, 18:30 UTC | Jul 4, 21:10 UTC | 2h 40m |
| 2026-07-04 | AYT → KLV | Jul 4, 14:20 UTC | Jul 4, 17:30 UTC | 3h 10m |
Specifications
| Registration | OK-SWE |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 49D2EE · 22351356 (octal) |
Looking for transponder-level data? View the Mode-S 49D2EE page for country allocation, callsign history, and ADS-B signal details.
OK-SWE frequently asked
What type of aircraft is OK-SWE?
OK-SWE is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for OK-SWE?
OK-SWE broadcasts on Mode-S (ICAO 24-bit) address 49D2EE (octal 22351356). View the transponder page.
What route does OK-SWE typically fly?
OK-SWE most frequently flies between PRG and PRG based on observed flights.
Where is OK-SWE right now?
OK-SWE is not currently being tracked; last seen 28m ago.