sensors Mode-S transponder
781300
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1382 · BOEING 737 MAX 8
- Hex
- 781300
- Octal
- 36011400
- Decimal
- 7,869,184
- Country
- CN
- Tail
- B-1382
- Type
- B38M
- Flights observed
- 165
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 17:40 UTC
Last known position
Country allocation
The ICAO 24-bit address 781300 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 |
|---|---|---|---|
| CSH841 | Shanghai Airlines | 13 | 2026-07-23 |
| CSH862 | - | 10 | 2026-07-04 |
| CSH842 | Shanghai Airlines | 9 | 2026-07-19 |
| CSH855 | - | 8 | 2026-07-14 |
| CSH811 | Shanghai Airlines | 8 | 2026-07-18 |
| CSH866 | Shanghai Airlines | 7 | 2026-07-01 |
| CSH863 | - | 7 | 2026-07-22 |
| CSH861 | - | 7 | 2026-07-04 |
| CSH858 | Shanghai Airlines | 7 | 2026-05-17 |
| CSH857 | Shanghai Airlines | 7 | 2026-05-17 |
| CSH856 | Shanghai Airlines | 6 | 2026-07-23 |
| CSH853 | - | 6 | 2026-07-07 |
| CSH831 | - | 6 | 2026-07-19 |
| CSH877 | Shanghai Airlines | 5 | 2026-07-25 |
| CSH865 | - | 5 | 2026-06-30 |
| CSH834 | - | 5 | 2026-06-16 |
| CSH812 | - | 4 | 2026-07-18 |
| CSH9136 | - | 3 | 2026-07-17 |
| CSH878 | Shanghai Airlines | 3 | 2026-07-26 |
| CSH868 | Shanghai Airlines | 3 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CSH868 | BKI → PVG | Jul 26, 17:30 UTC | Jul 26, 17:40 UTC | 10m |
| 2026-07-26 | CSH868 | BKI → PVG | Jul 26, 15:55 UTC | Jul 26, 16:15 UTC | 20m |
| 2026-07-26 | CSH867 | PVG → BKI | Jul 26, 05:00 UTC | Jul 26, 13:55 UTC | 8h 56m |
| 2026-07-26 | CSH878 | PEN → PVG | Jul 26, 00:40 UTC | Jul 26, 00:50 UTC | 10m |
| 2026-07-25 | CSH877 | PVG → PEN | Jul 25, 22:30 UTC | Jul 25, 22:45 UTC | 15m |
| 2026-07-25 | CSH7222 | KUL → PVG | Jul 25, 09:20 UTC | Jul 25, 19:45 UTC | 10h 25m |
| 2026-07-25 | CSH7222 | KUL → PVG | Jul 25, 06:50 UTC | Jul 25, 07:05 UTC | 15m |
| 2026-07-25 | CSH7221 | PVG → KUL | Jul 25, 04:55 UTC | Jul 25, 05:05 UTC | 10m |
| 2026-07-24 | CSH7221 | PVG → KUL | Jul 24, 11:10 UTC | Jul 25, 02:00 UTC | 14h 50m |
| 2026-07-23 | CSH841 | CGQ → PVG | Jul 23, 16:05 UTC | Jul 24, 11:55 UTC | 19h 50m |
| 2026-07-23 | CSH841 | CGQ → PVG | Jul 23, 14:05 UTC | Jul 24, 11:55 UTC | 21h 50m |
| 2026-07-23 | CSH856 | BKK → PVG | Jul 23, 13:50 UTC | Jul 24, 11:55 UTC | 22h 5m |
| 2026-07-22 | CSH864 | KUL → PVG | Jul 22, 23:45 UTC | Jul 23, 12:35 UTC | 12h 50m |
| 2026-07-22 | CSH863 | - | Jul 22, 21:55 UTC | Jul 22, 22:15 UTC | 20m |
| 2026-07-22 | CSH863 | - | Jul 22, 10:20 UTC | Jul 22, 18:55 UTC | 8h 35m |
| 2026-07-21 | CSH7221 | PVG → KUL | Jul 21, 17:05 UTC | Jul 22, 05:10 UTC | 12h 5m |
| 2026-07-21 | CSH7265 | PVG → KUL | Jul 21, 15:20 UTC | Jul 21, 15:30 UTC | 10m |
| 2026-07-21 | CSH7265 | PVG → KUL | Jul 21, 11:15 UTC | Jul 21, 12:15 UTC | 1h 0m |
| 2026-07-19 | CSH832 | - | Jul 19, 17:50 UTC | Jul 19, 20:25 UTC | 2h 35m |
| 2026-07-19 | CSH831 | - | Jul 19, 13:25 UTC | Jul 19, 15:50 UTC | 2h 25m |
| 2026-07-19 | CSH842 | BKK → PVG | Jul 19, 03:05 UTC | Jul 19, 03:15 UTC | 10m |
| 2026-07-18 | CSH812 | - | Jul 18, 07:20 UTC | Jul 18, 15:40 UTC | 8h 20m |
| 2026-07-18 | CSH811 | PVG → HKG | Jul 18, 03:50 UTC | Jul 18, 05:05 UTC | 1h 15m |
| 2026-07-17 | CSH9136 | - | Jul 17, 13:25 UTC | Jul 17, 13:45 UTC | 20m |
| 2026-07-16 | CSH831 | - | Jul 16, 07:05 UTC | Jul 16, 21:25 UTC | 14h 20m |
| 2026-07-15 | CSH9256 | - | Jul 15, 12:55 UTC | Jul 16, 07:50 UTC | 18h 55m |
| 2026-07-14 | CSH9136 | - | Jul 14, 14:45 UTC | Jul 15, 13:15 UTC | 22h 29m |
| 2026-07-14 | CSH856 | - | Jul 14, 12:30 UTC | Jul 14, 12:40 UTC | 10m |
| 2026-07-14 | CSH855 | - | Jul 14, 10:50 UTC | Jul 14, 11:10 UTC | 20m |
| 2026-07-13 | CSH7224 | - | Jul 13, 16:00 UTC | Jul 14, 09:40 UTC | 17h 40m |
| 2026-07-13 | CSH7223 | - | Jul 13, 14:35 UTC | Jul 13, 14:50 UTC | 15m |
| 2026-07-13 | CSH7223 | - | Jul 13, 11:05 UTC | Jul 13, 13:10 UTC | 2h 5m |
| 2026-07-09 | CSH814 | - | Jul 9, 19:35 UTC | Jul 10, 09:05 UTC | 13h 30m |
| 2026-07-09 | CSH813 | - | Jul 9, 16:45 UTC | Jul 9, 17:00 UTC | 15m |
| 2026-07-08 | CSH842 | - | Jul 8, 03:00 UTC | Jul 8, 14:45 UTC | 11h 45m |
| 2026-07-07 | CSH853 | - | Jul 7, 14:00 UTC | Jul 7, 14:30 UTC | 30m |
| 2026-07-06 | CSH9068 | - | Jul 6, 15:25 UTC | Jul 7, 14:00 UTC | 22h 35m |
| 2026-07-06 | CSH842 | - | Jul 6, 03:10 UTC | Jul 6, 15:35 UTC | 12h 25m |
| 2026-07-05 | CSH853 | - | Jul 5, 12:25 UTC | Jul 5, 14:35 UTC | 2h 10m |
| 2026-07-05 | CSH812 | - | Jul 5, 06:20 UTC | Jul 5, 06:35 UTC | 15m |
| 2026-07-05 | CSH811 | - | Jul 5, 04:05 UTC | Jul 5, 04:15 UTC | 10m |
| 2026-07-04 | CSH862 | - | Jul 4, 19:20 UTC | Jul 5, 03:05 UTC | 7h 45m |
| 2026-07-04 | CSH861 | - | Jul 4, 06:15 UTC | Jul 4, 17:50 UTC | 11h 35m |
| 2026-07-03 | CSH861 | - | Jul 3, 14:05 UTC | Jul 4, 13:50 UTC | 23h 45m |
| 2026-07-03 | CSH878 | - | Jul 3, 03:50 UTC | Jul 3, 14:10 UTC | 10h 20m |
| 2026-07-03 | CSH878 | - | Jul 3, 00:50 UTC | Jul 3, 01:00 UTC | 10m |
| 2026-07-02 | CSH877 | - | Jul 2, 23:15 UTC | Jul 2, 23:30 UTC | 15m |
| 2026-07-02 | CSH877 | - | Jul 2, 13:35 UTC | Jul 2, 20:50 UTC | 7h 15m |
| 2026-07-01 | CSH866 | KUL → PVG | Jul 1, 16:10 UTC | Jul 2, 13:50 UTC | 21h 40m |
| 2026-07-01 | CSH866 | KUL → PVG | Jul 1, 13:00 UTC | Jul 1, 17:05 UTC | 4h 5m |
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-1382 page for operator, model, and routing details .