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