sensors Mode-S transponder
780695
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5545 · BOEING 737-800
- Hex
- 780695
- Octal
- 36003225
- Decimal
- 7,866,005
- Country
- CN
- Tail
- B-5545
- Type
- B738
- Flights observed
- 39
- Distinct callsigns
- 13
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 780695 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSH9269 | - | 11 | 2026-06-22 |
| CSH9251 | - | 7 | 2026-07-06 |
| CSH9333 | - | 5 | 2026-07-09 |
| CSH9331 | Shanghai Airlines | 3 | 2026-06-07 |
| CSH9334 | - | 2 | 2026-07-09 |
| CSH9270 | Shanghai Airlines | 2 | 2026-05-28 |
| CSH818 | - | 2 | 2026-07-10 |
| CSH817 | - | 2 | 2026-07-08 |
| CSH9362 | - | 1 | 2026-07-10 |
| CSH9332 | Shanghai Airlines | 1 | 2026-06-07 |
| CSH9252 | - | 1 | 2026-07-06 |
| CSH7202 | - | 1 | 2026-07-06 |
| CES5346 | China Eastern Airlines | 1 | 2026-06-06 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | CSH9362 | - | Jul 10, 13:45 UTC | Jul 10, 14:00 UTC | 15m |
| 2026-07-10 | CSH818 | - | Jul 10, 05:55 UTC | Jul 10, 06:55 UTC | 1h 0m |
| 2026-07-09 | CSH9334 | - | Jul 9, 12:25 UTC | Jul 10, 04:15 UTC | 15h 50m |
| 2026-07-09 | CSH9333 | - | Jul 9, 04:15 UTC | Jul 9, 10:50 UTC | 6h 35m |
| 2026-07-08 | CSH9333 | - | Jul 8, 11:35 UTC | Jul 9, 10:50 UTC | 23h 15m |
| 2026-07-08 | CSH818 | - | Jul 8, 10:20 UTC | Jul 9, 04:15 UTC | 17h 55m |
| 2026-07-08 | CSH817 | - | Jul 8, 04:40 UTC | Jul 8, 05:30 UTC | 50m |
| 2026-07-06 | CSH7202 | - | Jul 6, 15:00 UTC | Jul 6, 15:25 UTC | 25m |
| 2026-07-06 | CSH9252 | - | Jul 6, 07:10 UTC | Jul 6, 07:30 UTC | 20m |
| 2026-07-06 | CSH9251 | - | Jul 6, 03:15 UTC | Jul 6, 03:30 UTC | 15m |
| 2026-07-04 | CSH9251 | - | Jul 4, 03:10 UTC | Jul 4, 03:30 UTC | 20m |
| 2026-07-03 | CSH9251 | - | Jul 3, 07:20 UTC | Jul 4, 03:30 UTC | 20h 10m |
| 2026-07-03 | CSH9251 | - | Jul 3, 03:30 UTC | Jul 4, 03:15 UTC | 23h 45m |
| 2026-07-02 | CSH9251 | - | Jul 2, 06:35 UTC | Jul 3, 03:40 UTC | 21h 5m |
| 2026-07-02 | CSH9251 | - | Jul 2, 03:10 UTC | Jul 2, 06:45 UTC | 3h 35m |
| 2026-07-01 | CSH9251 | - | Jul 1, 03:25 UTC | Jul 1, 07:00 UTC | 3h 35m |
| 2026-06-22 | CSH9269 | - | Jun 22, 04:30 UTC | Jun 22, 07:54 UTC | 3h 25m |
| 2026-06-19 | CSH9269 | - | Jun 19, 04:29 UTC | Jun 19, 04:44 UTC | 15m |
| 2026-06-14 | CSH9334 | - | Jun 14, 10:20 UTC | Jun 14, 10:30 UTC | 10m |
| 2026-06-14 | CSH9333 | - | Jun 14, 06:30 UTC | Jun 14, 07:30 UTC | 1h 0m |
| 2026-06-13 | CSH9333 | - | Jun 13, 09:10 UTC | Jun 14, 07:15 UTC | 22h 5m |
| 2026-06-13 | CSH9269 | JGS → HAK | Jun 13, 04:35 UTC | Jun 13, 04:50 UTC | 15m |
| 2026-06-11 | CSH9269 | JGS → HAK | Jun 11, 04:30 UTC | Jun 11, 08:05 UTC | 3h 35m |
| 2026-06-08 | CSH9333 | SHA → SZX | Jun 8, 07:40 UTC | Jun 8, 08:00 UTC | 20m |
| 2026-06-07 | CSH9332 | SZX → SHA | Jun 7, 04:40 UTC | Jun 7, 04:50 UTC | 10m |
| 2026-06-07 | CSH9331 | SHA → SZX | Jun 7, 01:50 UTC | Jun 7, 02:10 UTC | 20m |
| 2026-06-06 | CES5346 | SZX → SHA | Jun 6, 08:55 UTC | Jun 6, 09:04 UTC | 10m |
| 2026-06-05 | CSH9331 | SHA → SZX | Jun 5, 01:40 UTC | Jun 5, 02:30 UTC | 50m |
| 2026-06-04 | CSH9331 | SHA → SZX | Jun 4, 06:05 UTC | Jun 5, 02:30 UTC | 20h 25m |
| 2026-06-04 | CSH817 | SHA → MFM | Jun 4, 03:50 UTC | Jun 4, 04:15 UTC | 25m |
| 2026-06-02 | CSH9269 | JGS → HAK | Jun 2, 04:40 UTC | Jun 2, 07:45 UTC | 3h 5m |
| 2026-06-01 | CSH9269 | JGS → HAK | Jun 1, 08:20 UTC | Jun 2, 04:55 UTC | 20h 35m |
| 2026-06-01 | CSH9269 | JGS → HAK | Jun 1, 04:30 UTC | Jun 1, 08:30 UTC | 4h 0m |
| 2026-05-30 | CSH9269 | JGS → HAK | May 30, 04:30 UTC | May 30, 07:50 UTC | 3h 20m |
| 2026-05-28 | CSH9270 | HAK → JGS | May 28, 07:45 UTC | May 28, 07:55 UTC | 10m |
| 2026-05-28 | CSH9269 | JGS → HAK | May 28, 04:40 UTC | May 28, 05:00 UTC | 20m |
| 2026-05-26 | CSH9269 | JGS → HAK | May 26, 04:39 UTC | May 26, 07:55 UTC | 3h 15m |
| 2026-05-23 | CSH9269 | JGS → HAK | May 23, 09:25 UTC | May 24, 04:55 UTC | 19h 31m |
| 2026-05-23 | CSH9270 | HAK → JGS | May 23, 04:40 UTC | May 23, 09:35 UTC | 4h 55m |
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-5545 page for operator, model, and routing details .