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