sensors Mode-S transponder
780F93
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7633 · BOEING 737-800
- Hex
- 780F93
- Octal
- 36007623
- Decimal
- 7,868,307
- Country
- CN
- Tail
- B-7633
- Type
- B738
- Flights observed
- 50
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 780F93 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 |
|---|---|---|---|
| CSH801 | Shanghai Airlines | 5 | 2026-06-07 |
| CSH802 | Shanghai Airlines | 4 | 2026-06-07 |
| CSH9435 | - | 3 | 2026-06-21 |
| CSH847 | - | 3 | 2026-07-01 |
| CSH9362 | Shanghai Airlines | 2 | 2026-05-23 |
| CSH9361 | Shanghai Airlines | 2 | 2026-05-23 |
| CSH9358 | Shanghai Airlines | 2 | 2026-04-30 |
| CSH9357 | Shanghai Airlines | 2 | 2026-04-30 |
| CSH9064 | - | 2 | 2026-06-20 |
| CSH866 | Shanghai Airlines | 2 | 2026-07-02 |
| CSH848 | - | 2 | 2026-06-26 |
| CSH830 | - | 2 | 2026-07-14 |
| CSH820 | Shanghai Airlines | 2 | 2026-05-09 |
| CSH819 | Shanghai Airlines | 2 | 2026-05-08 |
| CSH818 | Shanghai Airlines | 2 | 2026-05-23 |
| CSH817 | Shanghai Airlines | 2 | 2026-05-23 |
| CSH9486 | - | 1 | 2026-05-30 |
| CSH9477 | - | 1 | 2026-07-09 |
| CSH9469 | - | 1 | 2026-04-21 |
| CSH9334 | Shanghai Airlines | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CSH830 | - | Jul 14, 08:50 UTC | Jul 14, 09:10 UTC | 20m |
| 2026-07-14 | CSH830 | - | Jul 14, 06:45 UTC | Jul 14, 07:00 UTC | 15m |
| 2026-07-09 | CSH9477 | - | Jul 9, 09:05 UTC | Jul 9, 09:20 UTC | 15m |
| 2026-07-05 | CSH9130 | - | Jul 5, 11:35 UTC | Jul 6, 03:55 UTC | 16h 20m |
| 2026-07-02 | CSH866 | KUL → PVG | Jul 2, 15:35 UTC | Jul 2, 16:15 UTC | 40m |
| 2026-07-02 | CSH866 | KUL → PVG | Jul 2, 13:05 UTC | Jul 2, 13:25 UTC | 20m |
| 2026-07-01 | CSH865 | - | Jul 1, 23:45 UTC | Jul 2, 11:40 UTC | 11h 55m |
| 2026-07-01 | CSH847 | - | Jul 1, 18:35 UTC | Jul 1, 19:30 UTC | 55m |
| 2026-06-27 | CSH856 | BKK → PVG | Jun 27, 12:29 UTC | Jun 27, 14:54 UTC | 2h 25m |
| 2026-06-27 | CSH855 | - | Jun 27, 10:10 UTC | Jun 27, 11:00 UTC | 50m |
| 2026-06-26 | CSH848 | - | Jun 26, 22:10 UTC | Jun 27, 09:15 UTC | 11h 5m |
| 2026-06-26 | CSH847 | - | Jun 26, 18:20 UTC | Jun 26, 20:20 UTC | 2h 0m |
| 2026-06-21 | CSH9435 | - | Jun 21, 10:04 UTC | Jun 22, 04:40 UTC | 18h 35m |
| 2026-06-20 | CSH9064 | - | Jun 20, 10:49 UTC | Jun 21, 10:34 UTC | 23h 45m |
| 2026-06-16 | CSH848 | - | Jun 16, 22:15 UTC | Jun 17, 11:45 UTC | 13h 30m |
| 2026-06-16 | CSH847 | - | Jun 16, 10:40 UTC | Jun 16, 20:05 UTC | 9h 26m |
| 2026-06-08 | CSH9435 | CGO → CGQ | Jun 8, 04:25 UTC | Jun 8, 04:35 UTC | 10m |
| 2026-06-07 | CSH802 | TSA → PVG | Jun 7, 04:50 UTC | Jun 8, 04:35 UTC | 23h 45m |
| 2026-06-07 | CSH801 | PVG → TSA | Jun 7, 03:00 UTC | Jun 7, 03:35 UTC | 35m |
| 2026-06-02 | CSH9435 | CGO → CGQ | Jun 2, 10:20 UTC | Jun 3, 04:40 UTC | 18h 20m |
| 2026-05-30 | CSH9486 | - | May 30, 12:00 UTC | May 30, 12:20 UTC | 20m |
| 2026-05-28 | CSH802 | TSA → PVG | May 28, 04:15 UTC | May 28, 04:40 UTC | 25m |
| 2026-05-27 | CSH801 | PVG → TSA | May 27, 10:40 UTC | May 28, 02:50 UTC | 16h 10m |
| 2026-05-23 | CSH9362 | ZUH → SHA | May 23, 13:35 UTC | May 23, 13:45 UTC | 10m |
| 2026-05-23 | CSH9361 | SHA → ZUH | May 23, 06:55 UTC | May 23, 11:45 UTC | 4h 50m |
| 2026-05-23 | CSH818 | MFM → SHA | May 23, 05:55 UTC | May 23, 06:05 UTC | 10m |
| 2026-05-23 | CSH817 | SHA → MFM | May 23, 03:35 UTC | May 23, 04:00 UTC | 25m |
| 2026-05-22 | CSH9362 | ZUH → SHA | May 22, 14:25 UTC | May 22, 14:45 UTC | 20m |
| 2026-05-22 | CSH9361 | SHA → ZUH | May 22, 13:00 UTC | May 22, 13:20 UTC | 20m |
| 2026-05-22 | CSH818 | MFM → SHA | May 22, 06:00 UTC | May 22, 06:20 UTC | 20m |
| 2026-05-22 | CSH817 | SHA → MFM | May 22, 03:50 UTC | May 22, 04:10 UTC | 20m |
| 2026-05-18 | CSH9064 | HRB → PVG | May 18, 10:35 UTC | May 18, 10:50 UTC | 15m |
| 2026-05-14 | CSH802 | TSA → PVG | May 14, 04:15 UTC | May 14, 04:45 UTC | 30m |
| 2026-05-13 | CSH801 | PVG → TSA | May 13, 09:00 UTC | May 14, 02:55 UTC | 17h 55m |
| 2026-05-09 | CSH820 | TSA → PVG | May 9, 06:00 UTC | May 9, 06:35 UTC | 35m |
| 2026-05-08 | CSH819 | PVG → TSA | May 8, 09:04 UTC | May 9, 04:25 UTC | 19h 20m |
| 2026-04-30 | CSH9358 | ZUH → PVG | Apr 30, 12:00 UTC | Apr 30, 12:15 UTC | 15m |
| 2026-04-30 | CSH9357 | PVG → ZUH | Apr 30, 09:55 UTC | Apr 30, 10:10 UTC | 15m |
| 2026-04-27 | CSH828 | ICN → PVG | Apr 27, 09:40 UTC | Apr 28, 04:40 UTC | 19h 0m |
| 2026-04-27 | CSH827 | PVG → ICN | Apr 27, 07:35 UTC | Apr 27, 08:15 UTC | 40m |
| 2026-04-25 | CSH820 | TSA → PVG | Apr 25, 06:00 UTC | Apr 25, 06:30 UTC | 30m |
| 2026-04-25 | CSH819 | PVG → TSA | Apr 25, 04:20 UTC | Apr 25, 04:50 UTC | 30m |
| 2026-04-21 | CSH9469 | - | Apr 21, 08:55 UTC | Apr 21, 11:10 UTC | 2h 15m |
| 2026-04-18 | CSH9334 | SZX → SHA | Apr 18, 11:15 UTC | Apr 18, 11:25 UTC | 10m |
| 2026-04-18 | CSH9333 | SHA → SZX | Apr 18, 07:05 UTC | Apr 18, 07:20 UTC | 15m |
| 2026-04-15 | CSH9358 | ZUH → PVG | Apr 15, 12:01 UTC | Apr 15, 12:10 UTC | 10m |
| 2026-04-15 | CSH9357 | PVG → ZUH | Apr 15, 10:05 UTC | Apr 15, 10:20 UTC | 15m |
| 2026-04-15 | CSH802 | TSA → PVG | Apr 15, 04:30 UTC | Apr 15, 04:45 UTC | 15m |
| 2026-04-15 | CSH801 | PVG → TSA | Apr 15, 02:55 UTC | Apr 15, 03:05 UTC | 10m |
| 2026-04-15 | CSH801 | PVG → TSA | Apr 15, 02:35 UTC | Apr 15, 02:50 UTC | 15m |
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-7633 page for operator, model, and routing details .