sensors Mode-S transponder
782125
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-226F · BOEING 737 MAX 8
- Hex
- 782125
- Octal
- 36020445
- Decimal
- 7,872,805
- Country
- CN
- Tail
- B-226F
- Type
- B38M
- Flights observed
- 76
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address 782125 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 |
|---|---|---|---|
| CSH877 | - | 10 | 2026-07-04 |
| CSH863 | Shanghai Airlines | 7 | 2026-05-30 |
| CSH865 | Shanghai Airlines | 6 | 2026-05-30 |
| CSH866 | Shanghai Airlines | 4 | 2026-05-31 |
| CSH841 | Shanghai Airlines | 4 | 2026-06-06 |
| CSH862 | - | 3 | 2026-06-17 |
| CSH861 | Shanghai Airlines | 3 | 2026-06-17 |
| CSH858 | Shanghai Airlines | 3 | 2026-06-05 |
| CSH839 | Shanghai Airlines | 3 | 2026-06-02 |
| CSH834 | Shanghai Airlines | 3 | 2026-06-11 |
| CSH833 | Shanghai Airlines | 3 | 2026-06-10 |
| CSH9255 | Shanghai Airlines | 2 | 2026-06-10 |
| CSH9253 | - | 2 | 2026-06-24 |
| CSH878 | - | 2 | 2026-06-29 |
| CSH864 | Shanghai Airlines | 2 | 2026-04-27 |
| CSH848 | Shanghai Airlines | 2 | 2026-05-12 |
| CSH847 | Shanghai Airlines | 2 | 2026-05-12 |
| CSH840 | Shanghai Airlines | 2 | 2026-06-03 |
| CSH9540 | Shanghai Airlines | 1 | 2026-05-21 |
| CSH9539 | Shanghai Airlines | 1 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-04 | CSH877 | - | Jul 4, 22:55 UTC | Jul 4, 23:15 UTC | 20m |
| 2026-07-04 | CSH877 | - | Jul 4, 01:50 UTC | Jul 4, 20:15 UTC | 18h 25m |
| 2026-07-04 | CSH877 | - | Jul 4, 01:00 UTC | Jul 4, 20:15 UTC | 19h 15m |
| 2026-07-03 | CSH844 | SIN → PVG | Jul 3, 21:35 UTC | Jul 4, 19:15 UTC | 21h 40m |
| 2026-07-03 | CSH843 | PVG → SIN | Jul 3, 15:50 UTC | Jul 3, 20:00 UTC | 4h 10m |
| 2026-06-29 | CSH878 | - | Jun 29, 03:54 UTC | Jun 29, 05:00 UTC | 1h 5m |
| 2026-06-28 | CSH877 | - | Jun 28, 22:39 UTC | Jun 28, 22:55 UTC | 15m |
| 2026-06-28 | CSH877 | - | Jun 28, 19:34 UTC | Jun 28, 20:29 UTC | 55m |
| 2026-06-24 | CSH9253 | - | Jun 24, 11:20 UTC | Jun 24, 14:45 UTC | 3h 25m |
| 2026-06-17 | CSH862 | - | Jun 17, 17:55 UTC | Jun 17, 22:15 UTC | 4h 20m |
| 2026-06-17 | CSH861 | PVG → KUL | Jun 17, 12:05 UTC | Jun 17, 16:25 UTC | 4h 20m |
| 2026-06-14 | CSH878 | PEN → PVG | Jun 14, 00:45 UTC | Jun 14, 00:55 UTC | 10m |
| 2026-06-13 | CSH877 | - | Jun 13, 22:50 UTC | Jun 13, 23:00 UTC | 10m |
| 2026-06-13 | CSH877 | - | Jun 13, 03:40 UTC | Jun 13, 20:05 UTC | 16h 24m |
| 2026-06-12 | CSH877 | - | Jun 12, 22:45 UTC | Jun 12, 22:55 UTC | 10m |
| 2026-06-12 | CSH877 | - | Jun 12, 10:10 UTC | Jun 12, 20:35 UTC | 10h 25m |
| 2026-06-11 | CSH834 | BKK → PVG | Jun 11, 11:25 UTC | Jun 12, 10:55 UTC | 23h 31m |
| 2026-06-11 | CSH834 | BKK → PVG | Jun 11, 10:00 UTC | Jun 11, 12:50 UTC | 2h 50m |
| 2026-06-10 | CSH833 | PVG → BKK | Jun 10, 20:10 UTC | Jun 11, 08:20 UTC | 12h 10m |
| 2026-06-10 | CSH9255 | PVG → HAK | Jun 10, 03:10 UTC | Jun 10, 17:50 UTC | 14h 40m |
| 2026-06-07 | CSH862 | KUL → PVG | Jun 7, 18:10 UTC | Jun 8, 08:10 UTC | 14h 0m |
| 2026-06-07 | CSH861 | PVG → KUL | Jun 7, 05:10 UTC | Jun 7, 16:15 UTC | 11h 5m |
| 2026-06-06 | CSH841 | CGQ → PVG | Jun 6, 10:20 UTC | Jun 6, 17:49 UTC | 7h 30m |
| 2026-06-05 | CSH841 | CGQ → PVG | Jun 5, 19:20 UTC | Jun 6, 17:49 UTC | 22h 30m |
| 2026-06-05 | CSH858 | HKT → PVG | Jun 5, 17:20 UTC | Jun 6, 17:15 UTC | 23h 55m |
| 2026-06-05 | CSH858 | HKT → PVG | Jun 5, 16:40 UTC | Jun 6, 11:00 UTC | 18h 20m |
| 2026-06-05 | CSH858 | HKT → PVG | Jun 5, 13:20 UTC | Jun 6, 11:00 UTC | 21h 40m |
| 2026-06-05 | CSH857 | PVG → HKT | Jun 5, 11:35 UTC | Jun 6, 11:00 UTC | 23h 25m |
| 2026-06-03 | CSH840 | BKK → PVG | Jun 3, 18:50 UTC | Jun 3, 21:00 UTC | 2h 10m |
| 2026-06-02 | CSH839 | PVG → BKK | Jun 2, 19:35 UTC | Jun 3, 13:40 UTC | 18h 5m |
| 2026-05-31 | CSH866 | KUL → PVG | May 31, 12:45 UTC | Jun 1, 05:00 UTC | 16h 15m |
| 2026-05-30 | CSH865 | PVG → KUL | May 30, 23:15 UTC | May 31, 11:00 UTC | 11h 45m |
| 2026-05-30 | CSH863 | PVG → KUL | May 30, 21:05 UTC | May 30, 21:20 UTC | 15m |
| 2026-05-30 | CSH834 | BKK → PVG | May 30, 10:10 UTC | May 30, 18:15 UTC | 8h 5m |
| 2026-05-29 | CSH833 | PVG → BKK | May 29, 13:20 UTC | May 30, 07:55 UTC | 18h 35m |
| 2026-05-29 | CSH833 | PVG → BKK | May 29, 12:40 UTC | May 30, 07:55 UTC | 19h 15m |
| 2026-05-28 | CSH865 | PVG → KUL | May 28, 23:10 UTC | May 29, 11:05 UTC | 11h 55m |
| 2026-05-28 | CSH863 | PVG → KUL | May 28, 21:15 UTC | May 28, 21:30 UTC | 15m |
| 2026-05-28 | CSH863 | PVG → KUL | May 28, 17:05 UTC | May 28, 18:10 UTC | 1h 5m |
| 2026-05-28 | CSH9136 | BAV → PVG | May 28, 12:40 UTC | May 28, 13:05 UTC | 25m |
| 2026-05-23 | CSH854 | BKK → PVG | May 23, 05:00 UTC | May 23, 07:20 UTC | 2h 20m |
| 2026-05-22 | CSH841 | CGQ → PVG | May 22, 16:15 UTC | May 22, 18:20 UTC | 2h 5m |
| 2026-05-21 | CSH9540 | SYX → PVG | May 21, 08:50 UTC | May 21, 09:15 UTC | 25m |
| 2026-05-19 | CSH9539 | PVG → SYX | May 19, 03:45 UTC | May 19, 08:05 UTC | 4h 20m |
| 2026-05-17 | CSH9253 | SHA → HAK | May 17, 10:35 UTC | May 17, 14:30 UTC | 3h 55m |
| 2026-05-12 | CSH848 | BKK → PVG | May 12, 22:25 UTC | May 13, 11:20 UTC | 12h 55m |
| 2026-05-12 | CSH847 | PVG → BKK | May 12, 03:10 UTC | May 12, 20:30 UTC | 17h 20m |
| 2026-05-11 | CSH9256 | HAK → PVG | May 11, 06:25 UTC | May 12, 03:10 UTC | 20h 45m |
| 2026-05-11 | CSH9255 | PVG → HAK | May 11, 03:25 UTC | May 12, 03:10 UTC | 23h 46m |
| 2026-05-10 | CSH840 | BKK → PVG | May 10, 15:09 UTC | May 11, 06:35 UTC | 15h 25m |
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-226F page for operator, model, and routing details .