Not currently tracked · last seen 3h ago
- Flights observed
- 191 showing last 50
- Avg flight time
- 10h 32m
- Typical route
- -
- Last seen
- 3h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-21 | HND → SHA | Jul 21, 05:45 UTC | Jul 21, 07:15 UTC | 1h 30m |
| 2026-07-21 | SHA → HND | Jul 21, 02:40 UTC | Jul 21, 04:20 UTC | 1h 40m |
| 2026-07-18 | - | Jul 18, 07:25 UTC | Jul 18, 07:45 UTC | 20m |
| 2026-07-17 | - | Jul 17, 01:25 UTC | Jul 17, 01:39 UTC | 15m |
| 2026-07-15 | - | Jul 15, 17:55 UTC | Jul 15, 21:10 UTC | 3h 15m |
| 2026-07-15 | - | Jul 15, 14:15 UTC | Jul 15, 15:00 UTC | 45m |
| 2026-07-14 | - | Jul 14, 11:20 UTC | Jul 14, 13:10 UTC | 1h 50m |
| 2026-07-13 | - | Jul 13, 14:05 UTC | Jul 14, 04:35 UTC | 14h 30m |
| 2026-07-12 | - | Jul 12, 23:45 UTC | Jul 13, 12:55 UTC | 13h 10m |
| 2026-07-12 | - | Jul 12, 15:45 UTC | Jul 12, 20:35 UTC | 4h 50m |
| 2026-07-11 | - | Jul 11, 08:15 UTC | Jul 11, 09:55 UTC | 1h 40m |
| 2026-07-10 | - | Jul 10, 12:35 UTC | Jul 11, 06:40 UTC | 18h 5m |
| 2026-07-10 | - | Jul 10, 11:25 UTC | Jul 11, 06:40 UTC | 19h 15m |
| 2026-07-10 | - | Jul 10, 04:10 UTC | Jul 10, 04:30 UTC | 20m |
| 2026-07-09 | - | Jul 9, 08:35 UTC | Jul 10, 03:35 UTC | 19h 0m |
| 2026-07-09 | - | Jul 9, 07:30 UTC | Jul 10, 03:35 UTC | 20h 5m |
| 2026-07-08 | - | Jul 8, 17:40 UTC | Jul 9, 05:55 UTC | 12h 15m |
| 2026-07-08 | - | Jul 8, 06:35 UTC | Jul 9, 05:55 UTC | 23h 20m |
| 2026-07-08 | - | Jul 8, 03:25 UTC | Jul 8, 18:20 UTC | 14h 55m |
| 2026-07-07 | - | Jul 7, 12:35 UTC | Jul 8, 07:15 UTC | 18h 40m |
| 2026-07-07 | - | Jul 7, 11:15 UTC | Jul 8, 07:15 UTC | 20h 0m |
| 2026-07-07 | - | Jul 7, 04:25 UTC | Jul 7, 04:40 UTC | 15m |
| 2026-07-07 | - | Jul 7, 02:10 UTC | Jul 7, 03:40 UTC | 1h 30m |
| 2026-07-06 | - | Jul 6, 11:45 UTC | Jul 6, 12:35 UTC | 50m |
| 2026-07-06 | ICN → TPE | Jul 6, 05:25 UTC | Jul 6, 10:15 UTC | 4h 50m |
| 2026-07-05 | - | Jul 5, 08:40 UTC | Jul 6, 03:10 UTC | 18h 30m |
| 2026-07-04 | - | Jul 4, 12:35 UTC | Jul 5, 12:30 UTC | 23h 55m |
| 2026-07-04 | - | Jul 4, 11:15 UTC | Jul 5, 10:30 UTC | 23h 15m |
| 2026-07-04 | - | Jul 4, 04:50 UTC | Jul 4, 05:10 UTC | 20m |
| 2026-07-03 | - | Jul 3, 12:15 UTC | Jul 4, 04:10 UTC | 15h 55m |
| 2026-07-03 | - | Jul 3, 10:30 UTC | Jul 3, 11:00 UTC | 30m |
| 2026-07-03 | - | Jul 3, 05:15 UTC | Jul 3, 05:35 UTC | 20m |
| 2026-07-02 | SYD → ICN | Jul 2, 10:45 UTC | Jul 3, 03:30 UTC | 16h 45m |
| 2026-07-02 | PVG → SYD | Jul 2, 00:45 UTC | Jul 2, 02:45 UTC | 2h 0m |
| 2026-07-01 | - | Jul 1, 01:30 UTC | Jul 1, 02:05 UTC | 35m |
| 2026-06-30 | ICN → MEL | Jun 30, 05:45 UTC | Jun 30, 22:55 UTC | 17h 10m |
| 2026-06-29 | - | Jun 29, 11:20 UTC | Jun 30, 04:10 UTC | 16h 51m |
| 2026-06-29 | - | Jun 29, 04:39 UTC | Jun 29, 05:00 UTC | 20m |
| 2026-06-28 | - | Jun 28, 11:09 UTC | Jun 29, 04:04 UTC | 16h 55m |
| 2026-06-28 | - | Jun 28, 09:15 UTC | Jun 28, 09:45 UTC | 30m |
| 2026-06-28 | - | Jun 28, 04:40 UTC | Jun 28, 04:59 UTC | 20m |
| 2026-06-27 | - | Jun 27, 17:39 UTC | Jun 28, 02:49 UTC | 9h 10m |
| 2026-06-27 | - | Jun 27, 10:40 UTC | Jun 27, 11:14 UTC | 35m |
| 2026-06-26 | - | Jun 26, 17:50 UTC | Jun 27, 07:24 UTC | 13h 35m |
| 2026-06-26 | - | Jun 26, 08:34 UTC | Jun 27, 07:24 UTC | 22h 50m |
| 2026-06-26 | - | Jun 26, 07:55 UTC | Jun 27, 03:49 UTC | 19h 55m |
| 2026-06-26 | - | Jun 26, 04:34 UTC | Jun 27, 03:49 UTC | 23h 15m |
| 2026-06-25 | - | Jun 25, 20:34 UTC | Jun 26, 18:29 UTC | 21h 55m |
| 2026-06-25 | - | Jun 25, 20:09 UTC | Jun 26, 18:29 UTC | 22h 20m |
| 2026-06-25 | - | Jun 25, 10:35 UTC | Jun 26, 08:45 UTC | 22h 10m |
Specifications
| Registration | B-300P |
| Aircraft type | AIRBUS A-330-300 (A333) |
| Mode-S code | 781462 · 36012142 (octal) |
Looking for transponder-level data? View the Mode-S 781462 page for country allocation, callsign history, and ADS-B signal details.
B-300P frequently asked
What type of aircraft is B-300P?
B-300P is a AIRBUS A-330-300 (ICAO type code A333).
What is the Mode-S transponder code for B-300P?
B-300P broadcasts on Mode-S (ICAO 24-bit) address 781462 (octal 36012142). View the transponder page.
Where is B-300P right now?
B-300P is not currently being tracked; last seen 3h ago.