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