Not currently tracked · last seen 1d ago
- Flights observed
- 101 showing last 50
- Avg flight time
- 11h 7m
- Typical route
- BUD → TFU
- Last seen
- 1d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-28 | BUD → CTU | May 28, 14:40 UTC | May 28, 17:30 UTC | 2h 50m |
| 2026-05-27 | - | May 27, 18:05 UTC | May 28, 12:20 UTC | 18h 15m |
| 2026-05-27 | - | May 27, 16:00 UTC | May 28, 12:20 UTC | 20h 20m |
| 2026-05-27 | - | May 27, 10:05 UTC | May 27, 12:00 UTC | 1h 55m |
| 2026-05-26 | - | May 26, 16:00 UTC | May 27, 12:00 UTC | 20h 0m |
| 2026-05-26 | BUD → TFU | May 26, 13:19 UTC | May 27, 12:00 UTC | 22h 40m |
| 2026-05-26 | BUD → TFU | May 26, 13:04 UTC | May 27, 11:00 UTC | 21h 55m |
| 2026-05-26 | ALA → CTU | May 26, 07:19 UTC | May 26, 09:59 UTC | 2h 40m |
| 2026-05-24 | BUD → CTU | May 24, 13:50 UTC | May 24, 16:55 UTC | 3h 5m |
| 2026-05-24 | - | May 24, 06:40 UTC | May 24, 09:50 UTC | 3h 10m |
| 2026-05-22 | BRU → BRU | May 22, 19:25 UTC | May 23, 01:45 UTC | 6h 20m |
| 2026-05-22 | TFU → BRU | May 22, 14:55 UTC | May 22, 17:15 UTC | 2h 20m |
| 2026-05-22 | TFU → BRU | May 22, 12:15 UTC | May 22, 12:25 UTC | 10m |
| 2026-05-21 | TFU → BRU | May 21, 20:35 UTC | May 22, 10:30 UTC | 13h 55m |
| 2026-05-21 | - | May 21, 18:30 UTC | May 21, 18:50 UTC | 20m |
| 2026-05-21 | - | May 21, 08:35 UTC | May 21, 11:05 UTC | 2h 30m |
| 2026-05-20 | BUD → TFU | May 20, 12:40 UTC | May 21, 06:30 UTC | 17h 50m |
| 2026-05-19 | ALA → CTU | May 19, 15:15 UTC | May 20, 08:50 UTC | 17h 36m |
| 2026-05-18 | - | May 18, 17:20 UTC | May 19, 12:50 UTC | 19h 29m |
| 2026-05-18 | BUD → TFU | May 18, 16:00 UTC | May 19, 12:50 UTC | 20h 49m |
| 2026-05-17 | ALA → CTU | May 17, 18:01 UTC | May 18, 12:55 UTC | 18h 55m |
| 2026-05-17 | - | May 17, 15:15 UTC | May 17, 16:01 UTC | 45m |
| 2026-05-16 | BUD → WAW | May 16, 17:25 UTC | May 17, 16:01 UTC | 22h 35m |
| 2026-05-16 | BUD → WAW | May 16, 15:20 UTC | May 17, 15:15 UTC | 23h 55m |
| 2026-05-16 | BUD → WAW | May 16, 14:41 UTC | May 16, 18:20 UTC | 3h 40m |
| 2026-05-16 | BUD → WAW | May 16, 11:55 UTC | May 16, 12:55 UTC | 1h 0m |
| 2026-05-16 | - | May 16, 05:51 UTC | May 16, 06:01 UTC | 10m |
| 2026-05-14 | BUD → CTU | May 14, 22:10 UTC | May 15, 01:10 UTC | 3h 0m |
| 2026-05-13 | - | May 13, 23:20 UTC | May 14, 19:15 UTC | 19h 55m |
| 2026-05-13 | DEL → BUD | May 13, 21:40 UTC | May 14, 19:15 UTC | 21h 35m |
| 2026-05-13 | TFU → DEL | May 13, 19:05 UTC | May 13, 19:35 UTC | 30m |
| 2026-05-12 | TFU → DEL | May 12, 17:20 UTC | May 13, 15:05 UTC | 21h 45m |
| 2026-05-12 | TFU → DEL | May 12, 15:20 UTC | May 13, 15:05 UTC | 23h 45m |
| 2026-05-12 | BRU → BRU | May 12, 15:10 UTC | May 13, 13:05 UTC | 21h 55m |
| 2026-05-12 | BRU → SVO | May 12, 08:35 UTC | May 12, 12:00 UTC | 3h 25m |
| 2026-05-11 | BRU → SVO | May 11, 10:20 UTC | May 12, 03:30 UTC | 17h 10m |
| 2026-05-11 | BUD → TFU | May 11, 07:20 UTC | May 12, 03:30 UTC | 20h 10m |
| 2026-05-11 | ALA → CTU | May 11, 00:30 UTC | May 11, 02:25 UTC | 1h 55m |
| 2026-05-09 | BRU → BRU | May 9, 16:05 UTC | May 9, 18:35 UTC | 2h 30m |
| 2026-05-09 | BRU → SVO | May 9, 10:00 UTC | May 9, 13:35 UTC | 3h 35m |
| 2026-05-08 | FRA → TFU | May 8, 11:19 UTC | May 9, 06:05 UTC | 18h 45m |
| 2026-05-08 | FRA → TFU | May 8, 09:59 UTC | May 9, 06:05 UTC | 20h 5m |
| 2026-05-08 | HEL → HEL | May 8, 05:09 UTC | May 8, 07:29 UTC | 2h 20m |
| 2026-05-08 | HEL → HEL | May 8, 03:09 UTC | May 8, 03:19 UTC | 10m |
| 2026-05-07 | HEL → HEL | May 7, 21:50 UTC | May 8, 00:44 UTC | 2h 55m |
| 2026-05-06 | BUD → TFU | May 6, 13:20 UTC | May 6, 16:15 UTC | 2h 55m |
| 2026-05-05 | ALA → CTU | May 5, 14:50 UTC | May 6, 08:40 UTC | 17h 50m |
| 2026-05-04 | - | May 4, 17:20 UTC | May 5, 12:40 UTC | 19h 21m |
| 2026-05-04 | BUD → WAW | May 4, 16:20 UTC | May 5, 12:40 UTC | 20h 21m |
| 2026-05-04 | BUD → WAW | May 4, 13:05 UTC | May 4, 14:00 UTC | 55m |
Specifications
| Registration | B-308P |
| Aircraft type | AIRBUS A-330-200 (A332) |
| Mode-S code | 7816BD · 36013275 (octal) |
Looking for transponder-level data? View the Mode-S 7816BD page for country allocation, callsign history, and ADS-B signal details.
B-308P frequently asked
What type of aircraft is B-308P?
B-308P is a AIRBUS A-330-200 (ICAO type code A332).
What is the Mode-S transponder code for B-308P?
B-308P broadcasts on Mode-S (ICAO 24-bit) address 7816BD (octal 36013275). View the transponder page.
What route does B-308P typically fly?
B-308P most frequently flies between BUD and TFU based on observed flights.
Where is B-308P right now?
B-308P is not currently being tracked; last seen 1d ago.