sensors Mode-S transponder
781373
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1263 · BOEING 737 MAX 8
- Hex
- 781373
- Octal
- 36011563
- Decimal
- 7,869,299
- Country
- CN
- Tail
- B-1263
- Type
- B38M
- Flights observed
- 96
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 781373 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 |
|---|---|---|---|
| CSH811 | - | 9 | 2026-07-02 |
| CSH833 | - | 6 | 2026-06-26 |
| CSH812 | - | 6 | 2026-07-02 |
| CSH9255 | - | 5 | 2026-07-15 |
| CSH841 | - | 5 | 2026-07-13 |
| CSH868 | Shanghai Airlines | 4 | 2026-06-14 |
| CSH867 | Shanghai Airlines | 4 | 2026-06-14 |
| CSH857 | Shanghai Airlines | 4 | 2026-05-01 |
| CSH847 | Shanghai Airlines | 4 | 2026-04-16 |
| CSH843 | Shanghai Airlines | 4 | 2026-07-10 |
| CSH839 | - | 4 | 2026-07-16 |
| CSH834 | - | 4 | 2026-06-27 |
| CSH9539 | - | 3 | 2026-06-12 |
| CSH863 | Shanghai Airlines | 3 | 2026-05-12 |
| CSH842 | - | 3 | 2026-07-04 |
| CSH9253 | Shanghai Airlines | 2 | 2026-06-08 |
| CSH877 | - | 2 | 2026-06-30 |
| CSH865 | Shanghai Airlines | 2 | 2026-05-16 |
| CSH864 | Shanghai Airlines | 2 | 2026-05-12 |
| CSH861 | - | 2 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CSH7222 | - | Jul 17, 06:10 UTC | Jul 17, 10:15 UTC | 4h 5m |
| 2026-07-17 | CSH7221 | - | Jul 17, 04:14 UTC | Jul 17, 04:35 UTC | 20m |
| 2026-07-16 | CSH7221 | - | Jul 16, 17:25 UTC | Jul 17, 01:25 UTC | 8h 0m |
| 2026-07-16 | CSH840 | - | Jul 16, 15:14 UTC | Jul 16, 15:25 UTC | 10m |
| 2026-07-16 | CSH839 | - | Jul 16, 13:25 UTC | Jul 16, 13:45 UTC | 20m |
| 2026-07-15 | CSH9255 | - | Jul 15, 03:20 UTC | Jul 15, 04:30 UTC | 1h 10m |
| 2026-07-14 | CSH9255 | - | Jul 14, 07:20 UTC | Jul 15, 04:30 UTC | 21h 9m |
| 2026-07-14 | CSH854 | - | Jul 14, 05:00 UTC | Jul 14, 05:10 UTC | 10m |
| 2026-07-13 | CSH841 | - | Jul 13, 06:35 UTC | Jul 13, 16:25 UTC | 9h 50m |
| 2026-07-12 | CSH841 | - | Jul 12, 10:10 UTC | Jul 13, 06:35 UTC | 20h 25m |
| 2026-07-10 | CSH844 | - | Jul 10, 19:45 UTC | Jul 10, 23:40 UTC | 3h 55m |
| 2026-07-10 | CSH843 | PVG → SIN | Jul 10, 14:10 UTC | Jul 10, 18:20 UTC | 4h 10m |
| 2026-07-08 | CSH854 | - | Jul 8, 05:10 UTC | Jul 8, 05:35 UTC | 25m |
| 2026-07-07 | CSH841 | - | Jul 7, 17:15 UTC | Jul 7, 18:50 UTC | 1h 35m |
| 2026-07-04 | CSH842 | - | Jul 4, 03:10 UTC | Jul 4, 04:50 UTC | 1h 40m |
| 2026-07-02 | CSH853 | - | Jul 2, 21:15 UTC | Jul 3, 16:05 UTC | 18h 50m |
| 2026-07-02 | CSH853 | - | Jul 2, 18:15 UTC | Jul 3, 16:05 UTC | 21h 50m |
| 2026-07-02 | CSH861 | - | Jul 2, 12:15 UTC | Jul 2, 16:30 UTC | 4h 15m |
| 2026-07-02 | CSH812 | - | Jul 2, 06:41 UTC | Jul 2, 07:00 UTC | 19m |
| 2026-07-02 | CSH811 | - | Jul 2, 04:50 UTC | Jul 2, 05:15 UTC | 25m |
| 2026-07-01 | CSH811 | - | Jul 1, 17:20 UTC | Jul 2, 04:05 UTC | 10h 45m |
| 2026-07-01 | CSH839 | - | Jul 1, 11:25 UTC | Jul 1, 12:20 UTC | 55m |
| 2026-07-01 | CSH878 | - | Jul 1, 00:50 UTC | Jul 1, 01:00 UTC | 10m |
| 2026-06-30 | CSH877 | - | Jun 30, 22:45 UTC | Jun 30, 23:00 UTC | 15m |
| 2026-06-30 | CSH877 | - | Jun 30, 19:45 UTC | Jun 30, 20:35 UTC | 50m |
| 2026-06-28 | CSH844 | SIN → PVG | Jun 28, 19:55 UTC | Jun 29, 00:10 UTC | 4h 15m |
| 2026-06-28 | CSH843 | PVG → SIN | Jun 28, 14:04 UTC | Jun 28, 18:14 UTC | 4h 10m |
| 2026-06-27 | CSH834 | - | Jun 27, 10:14 UTC | Jun 27, 12:29 UTC | 2h 15m |
| 2026-06-26 | CSH833 | - | Jun 26, 20:00 UTC | Jun 27, 08:14 UTC | 12h 15m |
| 2026-06-26 | CSH843 | PVG → SIN | Jun 26, 14:25 UTC | Jun 26, 18:24 UTC | 4h 0m |
| 2026-06-23 | CSH812 | - | Jun 23, 06:29 UTC | Jun 23, 06:44 UTC | 15m |
| 2026-06-23 | CSH811 | - | Jun 23, 03:54 UTC | Jun 23, 04:09 UTC | 15m |
| 2026-06-22 | CSH831 | - | Jun 22, 12:05 UTC | Jun 23, 03:04 UTC | 15h 0m |
| 2026-06-20 | CSH840 | - | Jun 20, 15:39 UTC | Jun 20, 18:34 UTC | 2h 55m |
| 2026-06-20 | CSH839 | - | Jun 20, 11:49 UTC | Jun 20, 14:05 UTC | 2h 15m |
| 2026-06-16 | CSH9255 | - | Jun 16, 03:35 UTC | Jun 16, 06:50 UTC | 3h 15m |
| 2026-06-14 | CSH868 | BKI → PVG | Jun 14, 17:40 UTC | Jun 14, 20:10 UTC | 2h 30m |
| 2026-06-14 | CSH867 | PVG → BKI | Jun 14, 13:05 UTC | Jun 14, 16:15 UTC | 3h 10m |
| 2026-06-12 | CSH9539 | - | Jun 12, 19:55 UTC | Jun 13, 09:15 UTC | 13h 19m |
| 2026-06-12 | CSH843 | PVG → SIN | Jun 12, 03:20 UTC | Jun 12, 18:15 UTC | 14h 55m |
| 2026-06-11 | CSH812 | HKG → PVG | Jun 11, 06:20 UTC | Jun 12, 03:35 UTC | 21h 16m |
| 2026-06-11 | CSH811 | PVG → HKG | Jun 11, 04:15 UTC | Jun 11, 04:35 UTC | 20m |
| 2026-06-11 | CSH811 | PVG → HKG | Jun 11, 03:10 UTC | Jun 11, 03:25 UTC | 15m |
| 2026-06-08 | CSH9253 | SHA → HAK | Jun 8, 10:45 UTC | Jun 8, 14:50 UTC | 4h 5m |
| 2026-06-07 | CSH9254 | HAK → SHA | Jun 7, 14:35 UTC | Jun 8, 10:50 UTC | 20h 15m |
| 2026-06-07 | CSH9253 | SHA → HAK | Jun 7, 10:50 UTC | Jun 8, 10:45 UTC | 23h 55m |
| 2026-06-04 | CSH9255 | PVG → HAK | Jun 4, 20:10 UTC | Jun 5, 03:45 UTC | 7h 35m |
| 2026-06-04 | CSH868 | BKI → PVG | Jun 4, 17:50 UTC | Jun 4, 18:05 UTC | 15m |
| 2026-06-04 | CSH812 | HKG → PVG | Jun 4, 06:15 UTC | Jun 4, 16:40 UTC | 10h 25m |
| 2026-06-04 | CSH811 | PVG → HKG | Jun 4, 04:05 UTC | Jun 4, 04:15 UTC | 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-1263 page for operator, model, and routing details .