Not currently tracked · last seen Jul 26, 21:50 UTC
- Flights observed
- 133 showing last 50
- Avg flight time
- 7h 53m
- Typical route
- KUL → PVG
- Last seen
- Jul 26, 21:50 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | KUL → PVG | Jul 26, 17:25 UTC | Jul 26, 21:50 UTC | 4h 25m |
| 2026-07-26 | PVG → KUL | Jul 26, 02:15 UTC | Jul 26, 15:30 UTC | 13h 16m |
| 2026-07-25 | KUL → PVG | Jul 25, 23:45 UTC | Jul 26, 00:05 UTC | 20m |
| 2026-07-25 | PVG → KUL | Jul 25, 19:10 UTC | Jul 25, 22:05 UTC | 2h 55m |
| 2026-07-24 | - | Jul 24, 12:40 UTC | Jul 24, 16:35 UTC | 3h 55m |
| 2026-07-23 | PVG → KUL | Jul 23, 23:20 UTC | Jul 24, 11:10 UTC | 11h 50m |
| 2026-07-23 | - | Jul 23, 17:40 UTC | Jul 23, 21:55 UTC | 4h 15m |
| 2026-07-22 | - | Jul 22, 12:45 UTC | Jul 22, 16:45 UTC | 4h 0m |
| 2026-07-22 | PVG → KUL | Jul 22, 11:10 UTC | Jul 22, 11:30 UTC | 20m |
| 2026-07-22 | KUL → PVG | Jul 22, 00:05 UTC | Jul 22, 04:05 UTC | 4h 0m |
| 2026-07-21 | - | Jul 21, 18:15 UTC | Jul 21, 22:40 UTC | 4h 25m |
| 2026-07-20 | - | Jul 20, 12:55 UTC | Jul 20, 17:00 UTC | 4h 5m |
| 2026-07-20 | - | Jul 20, 11:20 UTC | Jul 20, 11:45 UTC | 25m |
| 2026-07-19 | KUL → PVG | Jul 19, 23:55 UTC | Jul 20, 08:20 UTC | 8h 25m |
| 2026-07-19 | - | Jul 19, 22:15 UTC | Jul 19, 22:35 UTC | 20m |
| 2026-07-19 | - | Jul 19, 19:45 UTC | Jul 19, 20:10 UTC | 25m |
| 2026-07-18 | PVG → HKT | Jul 18, 12:25 UTC | Jul 18, 19:50 UTC | 7h 25m |
| 2026-07-17 | PVG → HKT | Jul 17, 16:34 UTC | Jul 18, 14:50 UTC | 22h 16m |
| 2026-07-17 | - | Jul 17, 15:40 UTC | Jul 18, 14:25 UTC | 22h 46m |
| 2026-07-17 | - | Jul 17, 12:35 UTC | Jul 18, 12:30 UTC | 23h 56m |
| 2026-07-17 | - | Jul 17, 12:25 UTC | Jul 17, 16:34 UTC | 4h 10m |
| 2026-07-17 | - | Jul 17, 02:39 UTC | Jul 17, 11:00 UTC | 8h 20m |
| 2026-07-15 | - | Jul 15, 03:50 UTC | Jul 15, 04:55 UTC | 1h 5m |
| 2026-07-15 | - | Jul 15, 00:50 UTC | Jul 15, 01:00 UTC | 10m |
| 2026-07-14 | - | Jul 14, 22:40 UTC | Jul 14, 22:55 UTC | 14m |
| 2026-07-13 | - | Jul 13, 20:55 UTC | Jul 14, 19:45 UTC | 22h 50m |
| 2026-07-13 | - | Jul 13, 12:25 UTC | Jul 13, 20:55 UTC | 8h 30m |
| 2026-07-12 | - | Jul 12, 17:55 UTC | Jul 13, 14:40 UTC | 20h 45m |
| 2026-07-12 | - | Jul 12, 14:35 UTC | Jul 13, 14:30 UTC | 23h 55m |
| 2026-07-12 | - | Jul 12, 01:10 UTC | Jul 12, 13:01 UTC | 11h 50m |
| 2026-07-11 | - | Jul 11, 14:15 UTC | Jul 11, 14:50 UTC | 35m |
| 2026-07-11 | - | Jul 11, 11:15 UTC | Jul 11, 12:00 UTC | 45m |
| 2026-07-10 | - | Jul 10, 14:40 UTC | Jul 11, 12:00 UTC | 21h 21m |
| 2026-07-10 | - | Jul 10, 12:35 UTC | Jul 11, 12:00 UTC | 23h 26m |
| 2026-07-10 | - | Jul 10, 12:25 UTC | Jul 10, 14:40 UTC | 2h 15m |
| 2026-07-09 | - | Jul 9, 23:35 UTC | Jul 10, 10:40 UTC | 11h 5m |
| 2026-07-09 | - | Jul 9, 21:45 UTC | Jul 9, 22:20 UTC | 35m |
| 2026-07-09 | - | Jul 9, 11:10 UTC | Jul 9, 19:05 UTC | 7h 55m |
| 2026-07-08 | SIN → PVG | Jul 8, 20:20 UTC | Jul 9, 09:50 UTC | 13h 30m |
| 2026-07-08 | PVG → SIN | Jul 8, 14:35 UTC | Jul 8, 18:45 UTC | 4h 10m |
| 2026-07-06 | - | Jul 6, 17:30 UTC | Jul 7, 09:35 UTC | 16h 5m |
| 2026-07-06 | - | Jul 6, 03:40 UTC | Jul 6, 16:00 UTC | 12h 20m |
| 2026-06-30 | - | Jun 30, 12:20 UTC | Jun 30, 14:40 UTC | 2h 20m |
| 2026-06-30 | - | Jun 30, 08:40 UTC | Jun 30, 10:50 UTC | 2h 10m |
| 2026-06-25 | - | Jun 25, 22:45 UTC | Jun 25, 22:59 UTC | 15m |
| 2026-06-25 | - | Jun 25, 19:34 UTC | Jun 25, 20:30 UTC | 55m |
| 2026-06-22 | - | Jun 22, 15:24 UTC | Jun 23, 03:29 UTC | 12h 5m |
| 2026-06-22 | - | Jun 22, 11:50 UTC | Jun 22, 14:05 UTC | 2h 15m |
| 2026-06-19 | - | Jun 19, 10:14 UTC | Jun 19, 12:34 UTC | 2h 20m |
| 2026-06-18 | - | Jun 18, 19:35 UTC | Jun 19, 07:54 UTC | 12h 19m |
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 KUL and PVG based on observed flights.
Where is B-224D right now?
B-224D is not currently being tracked; last seen Jul 26, 21:50 UTC.