sensors Mode-S transponder
782126
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-226G · BOEING 737 MAX 8
- Hex
- 782126
- Octal
- 36020446
- Decimal
- 7,872,806
- Country
- CN
- Tail
- B-226G
- Type
- B38M
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 17m ago
Last known position
Country allocation
The ICAO 24-bit address 782126 falls within the block assigned to China (CN) by ICAO Annex 10, Volume III. Every aircraft registered in China receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSH866 | Shanghai Airlines | 10 | 2026-06-14 |
| CSH863 | - | 10 | 2026-07-13 |
| CSH865 | - | 9 | 2026-07-13 |
| CSH856 | - | 8 | 2026-06-29 |
| CSH855 | - | 7 | 2026-06-29 |
| CSH864 | - | 6 | 2026-07-12 |
| CSH861 | Shanghai Airlines | 6 | 2026-06-15 |
| CSH834 | - | 6 | 2026-06-28 |
| CSH847 | Shanghai Airlines | 5 | 2026-05-30 |
| CSH841 | - | 5 | 2026-06-30 |
| CSH833 | - | 5 | 2026-06-27 |
| CSH831 | - | 5 | 2026-06-18 |
| CSH857 | - | 4 | 2026-07-09 |
| CSH868 | - | 3 | 2026-07-01 |
| CSH867 | Shanghai Airlines | 3 | 2026-06-20 |
| CSH812 | - | 3 | 2026-07-10 |
| CSH862 | Shanghai Airlines | 2 | 2026-06-15 |
| CSH854 | - | 2 | 2026-07-01 |
| CSH848 | Shanghai Airlines | 2 | 2026-05-30 |
| CSH843 | Shanghai Airlines | 2 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CSH865 | - | Jul 13, 23:25 UTC | Jul 14, 11:30 UTC | 12h 5m |
| 2026-07-13 | CSH863 | - | Jul 13, 17:20 UTC | Jul 13, 21:45 UTC | 4h 25m |
| 2026-07-12 | CSH864 | - | Jul 12, 17:40 UTC | Jul 13, 17:30 UTC | 23h 50m |
| 2026-07-12 | CSH864 | - | Jul 12, 13:45 UTC | Jul 12, 17:55 UTC | 4h 10m |
| 2026-07-12 | CSH863 | - | Jul 12, 07:40 UTC | Jul 12, 11:55 UTC | 4h 15m |
| 2026-07-10 | CSH812 | - | Jul 10, 06:30 UTC | Jul 10, 07:25 UTC | 55m |
| 2026-07-09 | CSH857 | - | Jul 9, 12:00 UTC | Jul 10, 04:10 UTC | 16h 10m |
| 2026-07-01 | CSH868 | - | Jul 1, 17:25 UTC | Jul 1, 19:50 UTC | 2h 25m |
| 2026-07-01 | CSH868 | - | Jul 1, 06:00 UTC | Jul 1, 15:55 UTC | 9h 55m |
| 2026-07-01 | CSH854 | - | Jul 1, 04:55 UTC | Jul 1, 05:05 UTC | 10m |
| 2026-06-30 | CSH841 | - | Jun 30, 10:20 UTC | Jun 30, 18:30 UTC | 8h 10m |
| 2026-06-29 | CSH856 | - | Jun 29, 14:09 UTC | Jun 30, 10:25 UTC | 20h 16m |
| 2026-06-29 | CSH856 | - | Jun 29, 12:49 UTC | Jun 30, 10:25 UTC | 21h 36m |
| 2026-06-29 | CSH855 | - | Jun 29, 02:50 UTC | Jun 29, 10:44 UTC | 7h 55m |
| 2026-06-28 | CSH855 | - | Jun 28, 11:50 UTC | Jun 29, 10:44 UTC | 22h 55m |
| 2026-06-28 | CSH834 | - | Jun 28, 10:24 UTC | Jun 29, 09:14 UTC | 22h 50m |
| 2026-06-27 | CSH833 | - | Jun 27, 19:49 UTC | Jun 28, 07:54 UTC | 12h 5m |
| 2026-06-27 | CSH843 | PVG → SIN | Jun 27, 13:55 UTC | Jun 27, 18:04 UTC | 4h 10m |
| 2026-06-25 | CSH857 | - | Jun 25, 11:10 UTC | Jun 25, 19:29 UTC | 8h 20m |
| 2026-06-20 | CSH868 | - | Jun 20, 17:39 UTC | Jun 20, 20:09 UTC | 2h 30m |
| 2026-06-20 | CSH867 | PVG → BKI | Jun 20, 16:09 UTC | Jun 20, 16:34 UTC | 25m |
| 2026-06-19 | CSH867 | PVG → BKI | Jun 19, 17:34 UTC | Jun 20, 13:44 UTC | 20h 10m |
| 2026-06-19 | CSH840 | - | Jun 19, 15:54 UTC | Jun 20, 13:29 UTC | 21h 35m |
| 2026-06-19 | CSH839 | - | Jun 19, 11:54 UTC | Jun 19, 14:19 UTC | 2h 25m |
| 2026-06-18 | CSH839 | - | Jun 18, 17:35 UTC | Jun 19, 14:19 UTC | 20h 44m |
| 2026-06-18 | CSH831 | - | Jun 18, 13:35 UTC | Jun 19, 13:29 UTC | 23h 54m |
| 2026-06-18 | CSH831 | - | Jun 18, 13:05 UTC | Jun 18, 19:25 UTC | 6h 20m |
| 2026-06-15 | CSH862 | KUL → PVG | Jun 15, 17:59 UTC | Jun 15, 21:04 UTC | 3h 5m |
| 2026-06-15 | CSH861 | PVG → KUL | Jun 15, 03:45 UTC | Jun 15, 16:15 UTC | 12h 30m |
| 2026-06-14 | CSH861 | PVG → KUL | Jun 14, 15:45 UTC | Jun 15, 12:30 UTC | 20h 44m |
| 2026-06-14 | CSH866 | KUL → PVG | Jun 14, 12:30 UTC | Jun 15, 03:55 UTC | 15h 25m |
| 2026-06-13 | CSH865 | PVG → KUL | Jun 13, 16:35 UTC | Jun 14, 11:00 UTC | 18h 25m |
| 2026-06-13 | CSH866 | KUL → PVG | Jun 13, 13:35 UTC | Jun 14, 11:00 UTC | 21h 25m |
| 2026-06-13 | CSH866 | KUL → PVG | Jun 13, 13:20 UTC | Jun 14, 11:00 UTC | 21h 40m |
| 2026-06-12 | CSH865 | PVG → KUL | Jun 12, 23:50 UTC | Jun 13, 11:45 UTC | 11h 54m |
| 2026-06-12 | CSH863 | PVG → KUL | Jun 12, 09:55 UTC | Jun 12, 22:15 UTC | 12h 20m |
| 2026-06-11 | CSH833 | PVG → BKK | Jun 11, 19:45 UTC | Jun 12, 07:50 UTC | 12h 5m |
| 2026-06-11 | CSH843 | PVG → SIN | Jun 11, 13:55 UTC | Jun 11, 18:05 UTC | 4h 10m |
| 2026-06-10 | CSH812 | HKG → PVG | Jun 10, 06:20 UTC | Jun 10, 07:15 UTC | 55m |
| 2026-06-10 | CSH811 | PVG → HKG | Jun 10, 02:40 UTC | Jun 10, 04:10 UTC | 1h 30m |
| 2026-06-03 | CSH856 | BKK → PVG | Jun 3, 13:45 UTC | Jun 4, 08:05 UTC | 18h 20m |
| 2026-06-03 | CSH856 | BKK → PVG | Jun 3, 12:25 UTC | Jun 4, 08:05 UTC | 19h 40m |
| 2026-06-03 | CSH855 | PVG → BKK | Jun 3, 02:35 UTC | Jun 3, 10:50 UTC | 8h 15m |
| 2026-06-02 | CSH864 | KUL → PVG | Jun 2, 23:20 UTC | Jun 2, 23:35 UTC | 15m |
| 2026-06-02 | CSH863 | PVG → KUL | Jun 2, 21:10 UTC | Jun 2, 21:30 UTC | 20m |
| 2026-06-02 | CSH834 | BKK → PVG | Jun 2, 10:05 UTC | Jun 2, 18:20 UTC | 8h 15m |
| 2026-06-01 | CSH833 | PVG → BKK | Jun 1, 17:25 UTC | Jun 2, 08:20 UTC | 14h 55m |
| 2026-06-01 | CSH867 | PVG → BKI | Jun 1, 03:50 UTC | Jun 1, 16:05 UTC | 12h 15m |
| 2026-05-31 | CSH834 | BKK → PVG | May 31, 11:35 UTC | Jun 1, 08:10 UTC | 20h 35m |
| 2026-05-31 | CSH834 | BKK → PVG | May 31, 10:00 UTC | Jun 1, 08:10 UTC | 22h 10m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the B-226G page for operator, model, and routing details .