sensors Mode-S transponder
781452
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1149 · BOEING 737 MAX 8
- Hex
- 781452
- Octal
- 36012122
- Decimal
- 7,869,522
- Country
- CN
- Tail
- B-1149
- Type
- B38M
- Flights observed
- 84
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 781452 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 |
|---|---|---|---|
| CSH863 | - | 6 | 2026-07-01 |
| CSH831 | - | 5 | 2026-06-29 |
| CSH811 | Shanghai Airlines | 5 | 2026-05-28 |
| CSH877 | - | 4 | 2026-07-03 |
| CSH854 | - | 4 | 2026-06-26 |
| CSH853 | Shanghai Airlines | 4 | 2026-05-28 |
| CSH841 | - | 4 | 2026-06-25 |
| CSH834 | - | 4 | 2026-07-06 |
| CSH833 | - | 4 | 2026-07-05 |
| CSH832 | Shanghai Airlines | 4 | 2026-05-08 |
| CSH9255 | - | 2 | 2026-07-12 |
| CSH868 | Shanghai Airlines | 2 | 2026-06-02 |
| CSH867 | Shanghai Airlines | 2 | 2026-06-02 |
| CSH866 | Shanghai Airlines | 2 | 2026-05-19 |
| CSH865 | Shanghai Airlines | 2 | 2026-05-18 |
| CSH858 | Shanghai Airlines | 2 | 2026-06-06 |
| CSH847 | Shanghai Airlines | 2 | 2026-05-24 |
| CSH842 | Shanghai Airlines | 2 | 2026-06-08 |
| CSH839 | - | 2 | 2026-07-12 |
| CSH814 | Shanghai Airlines | 2 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | CSH7222 | - | Jul 16, 06:25 UTC | Jul 16, 10:15 UTC | 3h 50m |
| 2026-07-16 | CSH7221 | - | Jul 16, 00:40 UTC | Jul 16, 04:35 UTC | 3h 55m |
| 2026-07-12 | CSH9255 | - | Jul 12, 19:15 UTC | Jul 13, 05:01 UTC | 9h 45m |
| 2026-07-12 | CSH840 | - | Jul 12, 17:10 UTC | Jul 12, 17:20 UTC | 10m |
| 2026-07-12 | CSH839 | - | Jul 12, 15:25 UTC | Jul 12, 15:45 UTC | 20m |
| 2026-07-12 | CSH839 | - | Jul 12, 13:30 UTC | Jul 12, 13:40 UTC | 10m |
| 2026-07-06 | CSH834 | - | Jul 6, 10:10 UTC | Jul 6, 12:35 UTC | 2h 25m |
| 2026-07-05 | CSH833 | - | Jul 5, 19:40 UTC | Jul 6, 08:30 UTC | 12h 50m |
| 2026-07-05 | CSH843 | PVG → SIN | Jul 5, 13:55 UTC | Jul 5, 18:00 UTC | 4h 5m |
| 2026-07-03 | CSH877 | - | Jul 3, 23:25 UTC | Jul 3, 23:35 UTC | 10m |
| 2026-07-03 | CSH877 | - | Jul 3, 19:30 UTC | Jul 3, 19:45 UTC | 15m |
| 2026-07-02 | CSH856 | - | Jul 2, 12:40 UTC | Jul 2, 15:05 UTC | 2h 25m |
| 2026-07-01 | CSH855 | - | Jul 1, 23:25 UTC | Jul 2, 10:50 UTC | 11h 25m |
| 2026-07-01 | CSH863 | - | Jul 1, 21:05 UTC | Jul 1, 21:15 UTC | 10m |
| 2026-07-01 | CSH863 | - | Jul 1, 17:05 UTC | Jul 1, 18:15 UTC | 1h 10m |
| 2026-06-29 | CSH831 | - | Jun 29, 04:04 UTC | Jun 29, 18:30 UTC | 14h 25m |
| 2026-06-26 | CSH854 | - | Jun 26, 04:59 UTC | Jun 26, 07:14 UTC | 2h 15m |
| 2026-06-25 | CSH841 | - | Jun 25, 16:20 UTC | Jun 25, 18:29 UTC | 2h 10m |
| 2026-06-09 | CSH9134 | BAV → PVG | Jun 9, 07:25 UTC | Jun 9, 07:50 UTC | 25m |
| 2026-06-08 | CSH842 | BKK → PVG | Jun 8, 02:55 UTC | Jun 8, 04:55 UTC | 2h 0m |
| 2026-06-07 | CSH841 | CGQ → PVG | Jun 7, 16:05 UTC | Jun 7, 18:20 UTC | 2h 15m |
| 2026-06-06 | CSH841 | CGQ → PVG | Jun 6, 19:04 UTC | Jun 7, 18:20 UTC | 23h 15m |
| 2026-06-06 | CSH858 | HKT → PVG | Jun 6, 16:39 UTC | Jun 7, 16:15 UTC | 23h 35m |
| 2026-06-06 | CSH858 | HKT → PVG | Jun 6, 11:30 UTC | Jun 6, 19:19 UTC | 7h 50m |
| 2026-06-05 | CSH864 | KUL → PVG | Jun 5, 03:10 UTC | Jun 5, 06:35 UTC | 3h 25m |
| 2026-06-05 | CSH863 | PVG → KUL | Jun 5, 00:50 UTC | Jun 5, 01:25 UTC | 35m |
| 2026-06-04 | CSH863 | PVG → KUL | Jun 4, 17:15 UTC | Jun 4, 22:20 UTC | 5h 5m |
| 2026-06-02 | CSH868 | BKI → PVG | Jun 2, 20:15 UTC | Jun 3, 08:00 UTC | 11h 45m |
| 2026-06-02 | CSH868 | BKI → PVG | Jun 2, 18:00 UTC | Jun 2, 18:10 UTC | 10m |
| 2026-06-02 | CSH867 | PVG → BKI | Jun 2, 16:15 UTC | Jun 2, 16:50 UTC | 35m |
| 2026-06-02 | CSH867 | PVG → BKI | Jun 2, 13:15 UTC | Jun 2, 14:20 UTC | 1h 5m |
| 2026-06-01 | CSH9255 | PVG → HAK | Jun 1, 03:00 UTC | Jun 1, 06:50 UTC | 3h 50m |
| 2026-05-30 | CSH877 | PVG → PEN | May 30, 18:50 UTC | May 30, 19:55 UTC | 1h 5m |
| 2026-05-29 | CSH854 | BKK → PVG | May 29, 05:05 UTC | May 29, 07:25 UTC | 2h 20m |
| 2026-05-28 | CSH853 | PVG → BKK | May 28, 12:15 UTC | May 28, 14:20 UTC | 2h 5m |
| 2026-05-28 | CSH812 | HKG → PVG | May 28, 06:30 UTC | May 28, 06:45 UTC | 15m |
| 2026-05-28 | CSH811 | PVG → HKG | May 28, 03:50 UTC | May 28, 04:05 UTC | 15m |
| 2026-05-28 | CSH811 | PVG → HKG | May 28, 02:50 UTC | May 28, 03:15 UTC | 25m |
| 2026-05-27 | CSH811 | PVG → HKG | May 27, 04:34 UTC | May 28, 03:15 UTC | 22h 40m |
| 2026-05-26 | CSH877 | PVG → PEN | May 26, 19:30 UTC | May 27, 04:34 UTC | 9h 5m |
| 2026-05-25 | CSH834 | BKK → PVG | May 25, 09:55 UTC | May 25, 12:10 UTC | 2h 15m |
| 2026-05-25 | CSH833 | PVG → BKK | May 25, 07:35 UTC | May 25, 08:30 UTC | 55m |
| 2026-05-24 | CSH847 | PVG → BKK | May 24, 18:40 UTC | May 24, 20:55 UTC | 2h 15m |
| 2026-05-23 | CSH9540 | SYX → PVG | May 23, 07:50 UTC | May 23, 08:00 UTC | 10m |
| 2026-05-22 | CSH834 | BKK → PVG | May 22, 10:35 UTC | May 23, 08:00 UTC | 21h 24m |
| 2026-05-22 | CSH834 | BKK → PVG | May 22, 10:00 UTC | May 23, 08:00 UTC | 21h 59m |
| 2026-05-21 | CSH833 | PVG → BKK | May 21, 22:20 UTC | May 22, 08:10 UTC | 9h 50m |
| 2026-05-21 | CSH847 | PVG → BKK | May 21, 20:25 UTC | May 21, 20:50 UTC | 25m |
| 2026-05-21 | CSH9136 | BAV → PVG | May 21, 12:30 UTC | May 21, 12:50 UTC | 20m |
| 2026-05-19 | CSH866 | KUL → PVG | May 19, 13:05 UTC | May 20, 08:10 UTC | 19h 6m |
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-1149 page for operator, model, and routing details .