sensors Mode-S transponder
780F94
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7635 · BOEING 737-800
- Hex
- 780F94
- Octal
- 36007624
- Decimal
- 7,868,308
- Country
- CN
- Tail
- B-7635
- Type
- B738
- Flights observed
- 51
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 780F94 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 |
|---|---|---|---|
| CSH9487 | - | 5 | 2026-07-11 |
| CSH9469 | - | 3 | 2026-07-09 |
| CSH9358 | - | 3 | 2026-06-25 |
| CSH9357 | - | 3 | 2026-06-25 |
| CSH9539 | - | 2 | 2026-07-10 |
| CSH9535 | Shanghai Airlines | 2 | 2026-05-16 |
| CSH9486 | - | 2 | 2026-07-14 |
| CSH9477 | - | 2 | 2026-05-06 |
| CSH9373 | Shanghai Airlines | 2 | 2026-05-20 |
| CSH9130 | Shanghai Airlines | 2 | 2026-05-31 |
| CSH9080 | - | 2 | 2026-06-14 |
| CSH820 | Shanghai Airlines | 2 | 2026-05-23 |
| CSH819 | Shanghai Airlines | 2 | 2026-05-23 |
| CSH7246 | - | 2 | 2026-07-13 |
| CSH9559 | - | 1 | 2026-05-19 |
| CSH9540 | Shanghai Airlines | 1 | 2026-04-28 |
| CSH9536 | Shanghai Airlines | 1 | 2026-04-15 |
| CSH9503 | Shanghai Airlines | 1 | 2026-06-12 |
| CSH9478 | - | 1 | 2026-05-07 |
| CSH9435 | Shanghai Airlines | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CSH9486 | - | Jul 14, 01:25 UTC | Jul 14, 12:25 UTC | 11h 0m |
| 2026-07-13 | CSH9486 | - | Jul 13, 14:00 UTC | Jul 14, 12:25 UTC | 22h 25m |
| 2026-07-13 | CSH7246 | - | Jul 13, 05:35 UTC | Jul 14, 01:40 UTC | 20h 5m |
| 2026-07-11 | CSH9487 | - | Jul 11, 02:20 UTC | Jul 11, 03:05 UTC | 45m |
| 2026-07-10 | CSH9487 | - | Jul 10, 08:00 UTC | Jul 11, 03:05 UTC | 19h 5m |
| 2026-07-10 | CSH9539 | - | Jul 10, 03:30 UTC | Jul 11, 02:30 UTC | 23h 0m |
| 2026-07-09 | CSH9539 | - | Jul 9, 13:05 UTC | Jul 10, 08:10 UTC | 19h 5m |
| 2026-07-09 | CSH9469 | - | Jul 9, 12:50 UTC | Jul 10, 08:10 UTC | 19h 20m |
| 2026-07-09 | CSH9469 | - | Jul 9, 10:25 UTC | Jul 10, 08:10 UTC | 21h 45m |
| 2026-07-08 | CSH7246 | - | Jul 8, 05:55 UTC | Jul 8, 06:15 UTC | 20m |
| 2026-07-07 | CSH9487 | - | Jul 7, 02:30 UTC | Jul 7, 02:40 UTC | 10m |
| 2026-07-06 | CSH9487 | - | Jul 6, 03:05 UTC | Jul 7, 02:40 UTC | 23h 35m |
| 2026-07-06 | CSH9487 | - | Jul 6, 02:30 UTC | Jul 6, 03:20 UTC | 50m |
| 2026-07-02 | - | - | Jul 2, 03:45 UTC | Jul 2, 03:55 UTC | 10m |
| 2026-06-25 | CSH9358 | - | Jun 25, 11:10 UTC | Jun 25, 11:25 UTC | 15m |
| 2026-06-25 | CSH9357 | - | Jun 25, 08:09 UTC | Jun 25, 09:25 UTC | 1h 15m |
| 2026-06-19 | CSH9064 | - | Jun 19, 10:44 UTC | Jun 19, 11:34 UTC | 50m |
| 2026-06-15 | CSH9469 | - | Jun 15, 11:24 UTC | Jun 16, 03:35 UTC | 16h 10m |
| 2026-06-14 | CSH9080 | - | Jun 14, 23:50 UTC | Jun 15, 08:10 UTC | 8h 20m |
| 2026-06-12 | CSH9503 | CGO → CGQ | Jun 12, 15:10 UTC | Jun 13, 01:30 UTC | 10h 20m |
| 2026-06-11 | CSH9358 | ZUH → PVG | Jun 11, 11:50 UTC | Jun 11, 12:45 UTC | 55m |
| 2026-06-11 | CSH9357 | PVG → ZUH | Jun 11, 09:00 UTC | Jun 11, 09:20 UTC | 20m |
| 2026-06-10 | CSH840 | BKK → PVG | Jun 10, 15:20 UTC | Jun 10, 17:40 UTC | 2h 20m |
| 2026-06-10 | CSH839 | PVG → BKK | Jun 10, 11:15 UTC | Jun 10, 13:40 UTC | 2h 25m |
| 2026-06-07 | CSH9080 | CGQ → PVG | Jun 7, 23:50 UTC | Jun 8, 00:35 UTC | 45m |
| 2026-05-31 | CSH9130 | HLD → PVG | May 31, 11:40 UTC | May 31, 11:55 UTC | 15m |
| 2026-05-27 | CSH9256 | HAK → PVG | May 27, 06:20 UTC | May 27, 06:34 UTC | 15m |
| 2026-05-27 | CSH9255 | PVG → HAK | May 27, 03:09 UTC | May 27, 03:24 UTC | 15m |
| 2026-05-24 | CSH9130 | HLD → PVG | May 24, 11:50 UTC | May 24, 12:35 UTC | 45m |
| 2026-05-23 | CSH820 | TSA → PVG | May 23, 05:55 UTC | May 23, 06:25 UTC | 30m |
| 2026-05-23 | CSH819 | PVG → TSA | May 23, 03:55 UTC | May 23, 04:30 UTC | 35m |
| 2026-05-20 | CSH9373 | PVG → ZHA | May 20, 12:30 UTC | May 20, 12:40 UTC | 10m |
| 2026-05-19 | CSH9559 | - | May 19, 06:20 UTC | May 19, 10:10 UTC | 3h 50m |
| 2026-05-16 | CSH9535 | PVG → SYX | May 16, 05:51 UTC | May 16, 10:11 UTC | 4h 20m |
| 2026-05-07 | CSH9478 | - | May 7, 05:50 UTC | May 7, 08:50 UTC | 3h 0m |
| 2026-05-06 | CSH9477 | - | May 6, 08:45 UTC | May 7, 05:50 UTC | 21h 4m |
| 2026-05-05 | CSH9477 | - | May 5, 11:45 UTC | May 6, 08:55 UTC | 21h 10m |
| 2026-05-01 | CSH9435 | CGO → CGQ | May 1, 04:40 UTC | May 1, 04:55 UTC | 15m |
| 2026-04-28 | CSH9540 | SYX → PVG | Apr 28, 03:45 UTC | Apr 28, 09:40 UTC | 5h 55m |
| 2026-04-27 | CSH820 | TSA → PVG | Apr 27, 05:50 UTC | Apr 28, 04:05 UTC | 22h 15m |
| 2026-04-27 | CSH819 | PVG → TSA | Apr 27, 04:00 UTC | Apr 27, 04:25 UTC | 25m |
| 2026-04-24 | CSH877 | PVG → PEN | Apr 24, 13:05 UTC | Apr 25, 05:00 UTC | 15h 55m |
| 2026-04-24 | CSH855 | PVG → BKK | Apr 24, 08:45 UTC | Apr 24, 11:25 UTC | 2h 40m |
| 2026-04-22 | CSH9310 | CAN → PVG | Apr 22, 14:50 UTC | Apr 23, 08:45 UTC | 17h 55m |
| 2026-04-22 | CSH9373 | PVG → ZHA | Apr 22, 12:25 UTC | Apr 22, 12:40 UTC | 15m |
| 2026-04-15 | CSH9536 | SYX → PVG | Apr 15, 10:20 UTC | Apr 15, 10:30 UTC | 10m |
| 2026-04-15 | CSH9535 | PVG → SYX | Apr 15, 06:10 UTC | Apr 15, 06:35 UTC | 25m |
| 2026-04-13 | CSH9358 | - | Apr 13, 12:10 UTC | Apr 13, 12:20 UTC | 10m |
| 2026-04-13 | CSH9357 | - | Apr 13, 09:40 UTC | Apr 13, 10:05 UTC | 25m |
| 2026-04-13 | CSH802 | TSA → PVG | Apr 13, 04:20 UTC | Apr 13, 04:40 UTC | 20m |
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-7635 page for operator, model, and routing details .