Not currently tracked · last seen 10h ago
- Flights observed
- 90 showing last 50
- Avg flight time
- 3h 23m
- Typical route
- PVG → TPE
- Last seen
- 10h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | SZX → PKX | May 30, 01:30 UTC | May 30, 01:45 UTC | 15m |
| 2026-05-29 | PEK → SZX | May 29, 13:50 UTC | May 29, 14:00 UTC | 10m |
| 2026-05-29 | PEK → SZX | May 29, 10:05 UTC | May 29, 10:25 UTC | 20m |
| 2026-05-29 | SZX → PEK | May 29, 05:20 UTC | May 29, 05:35 UTC | 15m |
| 2026-05-29 | PEK → SZX | May 29, 00:45 UTC | May 29, 01:10 UTC | 25m |
| 2026-05-28 | PEK → SHA | May 28, 10:30 UTC | May 28, 10:40 UTC | 10m |
| 2026-05-28 | TPE → PEK | May 28, 05:15 UTC | May 28, 05:40 UTC | 25m |
| 2026-05-28 | PEK → TPE | May 28, 02:55 UTC | May 28, 03:20 UTC | 25m |
| 2026-05-28 | PEK → TPE | May 28, 00:50 UTC | May 28, 01:00 UTC | 10m |
| 2026-05-27 | TPE → PVG | May 27, 07:00 UTC | May 27, 07:25 UTC | 25m |
| 2026-05-27 | PVG → TPE | May 27, 04:34 UTC | May 27, 05:04 UTC | 30m |
| 2026-05-27 | PEK → PVG | May 27, 00:10 UTC | May 27, 00:19 UTC | 10m |
| 2026-05-26 | TPE → PVG | May 26, 07:19 UTC | May 26, 07:45 UTC | 25m |
| 2026-05-26 | PVG → TPE | May 26, 05:00 UTC | May 26, 05:40 UTC | 40m |
| 2026-05-26 | PEK → PVG | May 26, 00:14 UTC | May 26, 00:24 UTC | 10m |
| 2026-05-25 | TPE → PVG | May 25, 07:05 UTC | May 25, 07:35 UTC | 30m |
| 2026-05-24 | TPE → PVG | May 24, 11:50 UTC | May 25, 04:50 UTC | 17h 0m |
| 2026-05-24 | PVG → TPE | May 24, 03:20 UTC | May 24, 10:10 UTC | 6h 50m |
| 2026-05-23 | TPE → PVG | May 23, 07:00 UTC | May 24, 01:20 UTC | 18h 21m |
| 2026-05-23 | PVG → TPE | May 23, 04:40 UTC | May 23, 05:10 UTC | 30m |
| 2026-05-18 | SZX → PEK | May 18, 02:45 UTC | May 18, 03:01 UTC | 15m |
| 2026-05-17 | PEK → SZX | May 17, 15:31 UTC | May 17, 15:45 UTC | 15m |
| 2026-05-17 | PEK → SZX | May 17, 12:40 UTC | May 17, 13:05 UTC | 25m |
| 2026-05-16 | SZX → PEK | May 16, 14:20 UTC | May 16, 14:35 UTC | 15m |
| 2026-05-16 | PKX → SZX | May 16, 11:51 UTC | May 16, 12:05 UTC | 15m |
| 2026-05-16 | SZX → PKX | May 16, 00:30 UTC | May 16, 00:45 UTC | 15m |
| 2026-05-15 | PEK → SZX | May 15, 15:05 UTC | May 15, 15:15 UTC | 10m |
| 2026-05-15 | SZX → PEK | May 15, 06:45 UTC | May 15, 06:55 UTC | 10m |
| 2026-05-14 | TPE → PVG | May 14, 07:05 UTC | May 14, 07:40 UTC | 35m |
| 2026-05-14 | PVG → TPE | May 14, 04:20 UTC | May 14, 05:05 UTC | 45m |
| 2026-05-13 | PVG → TPE | May 13, 07:35 UTC | May 14, 05:05 UTC | 21h 30m |
| 2026-05-13 | PVG → TPE | May 13, 06:55 UTC | May 14, 05:05 UTC | 22h 10m |
| 2026-05-13 | PVG → TPE | May 13, 04:35 UTC | May 13, 05:15 UTC | 40m |
| 2026-05-12 | PVG → TPE | May 12, 05:35 UTC | May 13, 05:15 UTC | 23h 40m |
| 2026-05-12 | TPE → PEK | May 12, 05:10 UTC | May 12, 05:50 UTC | 40m |
| 2026-05-12 | PEK → TPE | May 12, 02:45 UTC | May 12, 03:10 UTC | 25m |
| 2026-05-11 | TPE → PVG | May 11, 06:55 UTC | May 11, 07:35 UTC | 40m |
| 2026-05-10 | PVG → TPE | May 10, 10:15 UTC | May 11, 05:05 UTC | 18h 50m |
| 2026-05-10 | TPE → PVG | May 10, 03:14 UTC | May 10, 08:20 UTC | 5h 5m |
| 2026-05-10 | PVG → TPE | May 10, 00:45 UTC | May 10, 01:20 UTC | 35m |
| 2026-05-09 | PEK → PVG | May 9, 00:10 UTC | May 9, 00:20 UTC | 10m |
| 2026-05-07 | PEK → SHA | May 7, 12:55 UTC | May 7, 13:05 UTC | 10m |
| 2026-05-07 | TPE → PEK | May 7, 05:10 UTC | May 7, 05:45 UTC | 35m |
| 2026-05-07 | PEK → TPE | May 7, 02:45 UTC | May 7, 03:15 UTC | 30m |
| 2026-05-06 | TPE → PVG | May 6, 07:45 UTC | May 6, 08:25 UTC | 40m |
| 2026-05-06 | PVG → TPE | May 6, 05:05 UTC | May 6, 05:40 UTC | 35m |
| 2026-05-05 | TPE → PVG | May 5, 07:10 UTC | May 5, 07:45 UTC | 35m |
| 2026-05-05 | PVG → TPE | May 5, 04:45 UTC | May 5, 05:25 UTC | 40m |
| 2026-05-04 | TPE → PVG | May 4, 07:00 UTC | May 4, 07:35 UTC | 35m |
| 2026-05-03 | PVG → TPE | May 3, 10:05 UTC | May 4, 05:10 UTC | 19h 5m |
Specifications
| Registration | B-6512 |
| Aircraft type | AIRBUS A-330-300 (A333) |
| Mode-S code | 7803AE · 36001656 (octal) |
Looking for transponder-level data? View the Mode-S 7803AE page for country allocation, callsign history, and ADS-B signal details.
B-6512 frequently asked
What type of aircraft is B-6512?
B-6512 is a AIRBUS A-330-300 (ICAO type code A333).
What is the Mode-S transponder code for B-6512?
B-6512 broadcasts on Mode-S (ICAO 24-bit) address 7803AE (octal 36001656). View the transponder page.
What route does B-6512 typically fly?
B-6512 most frequently flies between PVG and TPE based on observed flights.
Where is B-6512 right now?
B-6512 is not currently being tracked; last seen 10h ago.