Not currently tracked · last seen 1d ago
- Flights observed
- 63 showing last 50
- Avg flight time
- 8h 18m
- Typical route
- PVG → KUL
- Last seen
- 1d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | BKK → PVG | May 29, 02:55 UTC | May 29, 05:30 UTC | 2h 35m |
| 2026-05-28 | CGQ → PVG | May 28, 10:55 UTC | May 28, 18:05 UTC | 7h 10m |
| 2026-05-27 | BKK → PVG | May 27, 03:09 UTC | May 27, 05:24 UTC | 2h 15m |
| 2026-05-26 | PVG → BKK | May 26, 07:05 UTC | May 26, 16:00 UTC | 8h 55m |
| 2026-05-25 | PVG → HKG | May 25, 18:00 UTC | May 26, 05:30 UTC | 11h 30m |
| 2026-05-25 | PVG → KUL | May 25, 05:10 UTC | May 25, 16:10 UTC | 11h 0m |
| 2026-05-24 | PVG → BKK | May 24, 13:25 UTC | May 24, 15:30 UTC | 2h 5m |
| 2026-05-24 | HKG → PVG | May 24, 06:35 UTC | May 24, 06:50 UTC | 15m |
| 2026-05-24 | PVG → HKG | May 24, 03:40 UTC | May 24, 05:00 UTC | 1h 20m |
| 2026-05-17 | BKK → PVG | May 17, 12:35 UTC | May 17, 14:50 UTC | 2h 15m |
| 2026-05-17 | PVG → BKK | May 17, 08:35 UTC | May 17, 11:05 UTC | 2h 30m |
| 2026-05-11 | BKK → PVG | May 11, 15:10 UTC | May 11, 17:25 UTC | 2h 15m |
| 2026-05-11 | PVG → BKK | May 11, 05:00 UTC | May 11, 13:50 UTC | 8h 50m |
| 2026-05-10 | HAK → PVG | May 10, 07:25 UTC | May 11, 05:00 UTC | 21h 35m |
| 2026-05-10 | PVG → HAK | May 10, 03:25 UTC | May 10, 08:20 UTC | 4h 55m |
| 2026-05-08 | KUL → PVG | May 8, 18:25 UTC | May 8, 22:35 UTC | 4h 10m |
| 2026-05-08 | PVG → KUL | May 8, 16:05 UTC | May 8, 16:20 UTC | 15m |
| 2026-05-08 | BKK → PVG | May 8, 05:05 UTC | May 8, 12:49 UTC | 7h 45m |
| 2026-05-07 | PVG → BKK | May 7, 07:55 UTC | May 7, 15:45 UTC | 7h 50m |
| 2026-05-06 | KUL → PVG | May 6, 12:45 UTC | May 7, 03:40 UTC | 14h 54m |
| 2026-05-05 | KUL → PVG | May 5, 23:15 UTC | May 6, 11:25 UTC | 12h 10m |
| 2026-05-05 | PVG → KUL | May 5, 03:25 UTC | May 5, 21:30 UTC | 18h 5m |
| 2026-05-04 | PVG → BKK | May 4, 06:15 UTC | May 4, 14:55 UTC | 8h 40m |
| 2026-05-04 | PVG → HKG | May 4, 02:45 UTC | May 4, 04:20 UTC | 1h 35m |
| 2026-05-03 | KUL → PVG | May 3, 18:09 UTC | May 3, 18:25 UTC | 15m |
| 2026-05-03 | PVG → KUL | May 3, 03:35 UTC | May 3, 16:34 UTC | 13h 0m |
| 2026-05-02 | PVG → KUL | May 2, 19:45 UTC | May 3, 16:34 UTC | 20h 49m |
| 2026-05-02 | PVG → PEN | May 2, 07:10 UTC | May 3, 04:30 UTC | 21h 19m |
| 2026-05-02 | BKK → PVG | May 2, 05:10 UTC | May 3, 04:30 UTC | 23h 19m |
| 2026-05-01 | CGQ → PVG | May 1, 10:55 UTC | May 1, 18:50 UTC | 7h 55m |
| 2026-04-26 | HKT → PVG | Apr 26, 16:35 UTC | Apr 27, 11:00 UTC | 18h 25m |
| 2026-04-26 | HKT → PVG | Apr 26, 13:25 UTC | Apr 27, 11:00 UTC | 21h 35m |
| 2026-04-26 | HKT → PVG | Apr 26, 11:40 UTC | Apr 26, 19:05 UTC | 7h 25m |
| 2026-04-25 | PVG → HKT | Apr 25, 17:00 UTC | Apr 26, 13:55 UTC | 20h 55m |
| 2026-04-25 | PVG → HKT | Apr 25, 14:35 UTC | Apr 26, 13:55 UTC | 23h 20m |
| 2026-04-25 | KUL → PVG | Apr 25, 13:10 UTC | Apr 26, 11:50 UTC | 22h 40m |
| 2026-04-24 | PVG → KUL | Apr 24, 23:20 UTC | Apr 25, 11:40 UTC | 12h 20m |
| 2026-04-24 | PVG → KUL | Apr 24, 17:15 UTC | Apr 24, 21:50 UTC | 4h 35m |
| 2026-04-18 | PEN → PVG | Apr 18, 19:45 UTC | Apr 19, 02:00 UTC | 6h 15m |
| 2026-04-18 | PEN → PVG | Apr 18, 04:45 UTC | Apr 19, 02:00 UTC | 21h 15m |
| 2026-04-17 | - | Apr 17, 14:50 UTC | Apr 17, 15:00 UTC | 9m |
| 2026-04-17 | - | Apr 17, 12:50 UTC | Apr 17, 13:00 UTC | 10m |
| 2026-04-17 | PVG → BKK | Apr 17, 10:55 UTC | Apr 17, 11:15 UTC | 20m |
| 2026-04-16 | - | Apr 16, 15:45 UTC | Apr 16, 16:40 UTC | 55m |
| 2026-04-16 | - | Apr 16, 13:54 UTC | Apr 16, 14:10 UTC | 15m |
| 2026-04-16 | - | Apr 16, 12:39 UTC | Apr 16, 13:05 UTC | 25m |
| 2026-04-16 | PVG → KUL | Apr 16, 09:45 UTC | Apr 16, 11:04 UTC | 1h 20m |
| 2026-04-16 | PVG → KUL | Apr 16, 07:09 UTC | Apr 16, 08:00 UTC | 50m |
| 2026-04-16 | PVG → KUL | Apr 16, 06:49 UTC | Apr 16, 07:05 UTC | 15m |
| 2026-04-16 | KUL → PVG | Apr 16, 02:24 UTC | Apr 16, 02:34 UTC | 10m |
Specifications
| Registration | B-224D |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 781FFA · 36017772 (octal) |
Looking for transponder-level data? View the Mode-S 781FFA page for country allocation, callsign history, and ADS-B signal details.
B-224D frequently asked
What type of aircraft is B-224D?
B-224D is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for B-224D?
B-224D broadcasts on Mode-S (ICAO 24-bit) address 781FFA (octal 36017772). View the transponder page.
What route does B-224D typically fly?
B-224D most frequently flies between PVG and KUL based on observed flights.
Where is B-224D right now?
B-224D is not currently being tracked; last seen 1d ago.