Not currently tracked · last seen 12d ago
- Flights observed
- 84 showing last 50
- Avg flight time
- 10h 23m
- Typical route
- MUC → PVG
- Last seen
- 12d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-18 | PEK → CAN | May 18, 04:20 UTC | May 18, 04:40 UTC | 20m |
| 2026-05-18 | CPH → PEK | May 18, 00:55 UTC | May 18, 01:10 UTC | 15m |
| 2026-05-17 | CPH → PEK | May 17, 17:05 UTC | May 17, 22:25 UTC | 5h 20m |
| 2026-05-16 | PEK → CPH | May 16, 17:25 UTC | May 17, 14:40 UTC | 21h 15m |
| 2026-05-16 | PEK → CPH | May 16, 15:20 UTC | May 17, 14:40 UTC | 23h 20m |
| 2026-05-16 | NCE → PEK | May 16, 13:05 UTC | May 17, 12:30 UTC | 23h 25m |
| 2026-05-16 | NCE → PEK | May 16, 11:51 UTC | May 17, 09:20 UTC | 21h 30m |
| 2026-05-15 | PEK → NCE | May 15, 22:20 UTC | May 16, 05:10 UTC | 6h 50m |
| 2026-05-14 | NCE → PEK | May 14, 11:40 UTC | May 14, 18:05 UTC | 6h 25m |
| 2026-05-13 | PEK → NCE | May 13, 20:55 UTC | May 14, 05:05 UTC | 8h 10m |
| 2026-05-12 | MXP → PEK | May 12, 11:45 UTC | May 12, 17:55 UTC | 6h 10m |
| 2026-05-11 | PVG → MXP | May 11, 12:55 UTC | May 12, 05:30 UTC | 16h 36m |
| 2026-05-11 | PVG → MXP | May 11, 10:10 UTC | May 12, 05:30 UTC | 19h 21m |
| 2026-05-10 | MUC → PVG | May 10, 13:44 UTC | May 11, 07:10 UTC | 17h 25m |
| 2026-05-10 | MUC → PVG | May 10, 11:05 UTC | May 11, 07:10 UTC | 20h 5m |
| 2026-05-10 | MUC → PVG | May 10, 10:40 UTC | May 11, 07:10 UTC | 20h 30m |
| 2026-05-09 | PVG → MUC | May 9, 12:35 UTC | May 10, 05:34 UTC | 17h 0m |
| 2026-05-09 | PVG → MUC | May 9, 09:45 UTC | May 10, 05:34 UTC | 19h 50m |
| 2026-05-09 | PVG → SIN | May 9, 04:00 UTC | May 9, 04:15 UTC | 15m |
| 2026-05-07 | LGW → PVG | May 7, 10:35 UTC | May 7, 19:30 UTC | 8h 55m |
| 2026-05-06 | PVG → LGW | May 6, 19:20 UTC | May 7, 05:55 UTC | 10h 35m |
| 2026-05-06 | PVG → LGW | May 6, 01:05 UTC | May 6, 23:15 UTC | 22h 9m |
| 2026-05-06 | PVG → LGW | May 6, 00:50 UTC | May 6, 23:00 UTC | 22h 9m |
| 2026-05-05 | NCE → PEK | May 5, 20:10 UTC | May 5, 20:25 UTC | 15m |
| 2026-05-05 | NCE → PEK | May 5, 11:40 UTC | May 5, 17:50 UTC | 6h 10m |
| 2026-05-04 | PVG → LGW | May 4, 12:45 UTC | May 5, 06:15 UTC | 17h 31m |
| 2026-05-04 | PVG → LGW | May 4, 10:00 UTC | May 5, 06:15 UTC | 20h 16m |
| 2026-05-03 | MUC → PVG | May 3, 13:30 UTC | May 4, 07:20 UTC | 17h 50m |
| 2026-05-03 | MUC → PVG | May 3, 11:25 UTC | May 4, 07:20 UTC | 19h 55m |
| 2026-05-03 | MUC → PVG | May 3, 10:25 UTC | May 3, 11:20 UTC | 55m |
| 2026-05-02 | PVG → MUC | May 2, 19:45 UTC | May 3, 05:50 UTC | 10h 4m |
| 2026-05-02 | PVG → MUC | May 2, 01:05 UTC | May 2, 23:45 UTC | 22h 41m |
| 2026-05-02 | PVG → MUC | May 2, 00:50 UTC | May 2, 22:00 UTC | 21h 11m |
| 2026-05-01 | VIE → PEK | May 1, 20:15 UTC | May 1, 20:30 UTC | 15m |
| 2026-05-01 | VIE → PEK | May 1, 11:45 UTC | May 1, 17:45 UTC | 6h 0m |
| 2026-04-30 | PEK → VIE | Apr 30, 21:00 UTC | May 1, 04:25 UTC | 7h 25m |
| 2026-04-30 | PEK → VIE | Apr 30, 19:10 UTC | Apr 30, 19:20 UTC | 10m |
| 2026-04-29 | VIE → PEK | Apr 29, 11:55 UTC | Apr 29, 20:10 UTC | 8h 15m |
| 2026-04-28 | PEK → VIE | Apr 28, 20:55 UTC | Apr 29, 04:15 UTC | 7h 20m |
| 2026-04-28 | PEK → SHA | Apr 28, 08:40 UTC | Apr 28, 08:50 UTC | 10m |
| 2026-04-28 | JNB → SZX | Apr 28, 00:25 UTC | Apr 28, 00:35 UTC | 10m |
| 2026-04-27 | JNB → SZX | Apr 27, 20:35 UTC | Apr 27, 20:50 UTC | 15m |
| 2026-04-27 | JNB → SZX | Apr 27, 08:30 UTC | Apr 27, 19:05 UTC | 10h 35m |
| 2026-04-26 | SZX → JNB | Apr 26, 18:35 UTC | Apr 27, 05:40 UTC | 11h 5m |
| 2026-04-26 | SZX → JNB | Apr 26, 16:55 UTC | Apr 26, 17:10 UTC | 15m |
| 2026-04-26 | SZX → JNB | Apr 26, 13:25 UTC | Apr 26, 13:40 UTC | 15m |
| 2026-04-26 | SZX → JNB | Apr 26, 11:05 UTC | Apr 26, 11:15 UTC | 10m |
| 2026-04-25 | CDG → PEK | Apr 25, 10:55 UTC | Apr 25, 14:50 UTC | 3h 55m |
| 2026-04-24 | PEK → CDG | Apr 24, 20:00 UTC | Apr 25, 04:20 UTC | 8h 20m |
| 2026-04-24 | PEK → CDG | Apr 24, 18:10 UTC | Apr 24, 18:20 UTC | 10m |
Specifications
| Registration | B-32F1 |
| Aircraft type | AIRBUS A-350-900 (A359) |
| Mode-S code | 781FB4 · 36017664 (octal) |
Looking for transponder-level data? View the Mode-S 781FB4 page for country allocation, callsign history, and ADS-B signal details.
B-32F1 frequently asked
What type of aircraft is B-32F1?
B-32F1 is a AIRBUS A-350-900 (ICAO type code A359).
What is the Mode-S transponder code for B-32F1?
B-32F1 broadcasts on Mode-S (ICAO 24-bit) address 781FB4 (octal 36017664). View the transponder page.
What route does B-32F1 typically fly?
B-32F1 most frequently flies between MUC and PVG based on observed flights.
Where is B-32F1 right now?
B-32F1 is not currently being tracked; last seen 12d ago.