sensors Mode-S transponder
780FBC
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-7396 · BOEING 737-800
- Hex
- 780FBC
- Octal
- 36007674
- Decimal
- 7,868,348
- Country
- CN
- Tail
- B-7396
- Type
- B738
- Flights observed
- 40
- Distinct callsigns
- 15
- Country
- CN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 780FBC 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSH818 | Shanghai Airlines | 10 | 2026-06-13 |
| CSH817 | - | 8 | 2026-06-13 |
| CSH9535 | Shanghai Airlines | 4 | 2026-06-10 |
| CSH9536 | Shanghai Airlines | 2 | 2026-06-03 |
| CSH9362 | Shanghai Airlines | 2 | 2026-05-19 |
| CSH9334 | Shanghai Airlines | 2 | 2026-06-11 |
| CSH852 | Shanghai Airlines | 2 | 2026-06-12 |
| CSH851 | Shanghai Airlines | 2 | 2026-06-12 |
| CSH810 | Shanghai Airlines | 2 | 2026-06-12 |
| CSH9361 | Shanghai Airlines | 1 | 2026-05-19 |
| CSH9333 | Shanghai Airlines | 1 | 2026-06-11 |
| CSH9260 | - | 1 | 2026-04-24 |
| CSH9253 | Shanghai Airlines | 1 | 2026-05-21 |
| CSH809 | - | 1 | 2026-06-12 |
| CES5349 | China Eastern Airlines | 1 | 2026-04-22 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-13 | CSH818 | MFM → SHA | Jun 13, 06:05 UTC | Jun 13, 06:15 UTC | 10m |
| 2026-06-13 | CSH817 | - | Jun 13, 04:15 UTC | Jun 13, 04:40 UTC | 25m |
| 2026-06-12 | CSH810 | HKG → SHA | Jun 12, 11:15 UTC | Jun 12, 12:05 UTC | 50m |
| 2026-06-12 | CSH809 | - | Jun 12, 09:00 UTC | Jun 12, 09:20 UTC | 20m |
| 2026-06-12 | CSH852 | TSA → SHA | Jun 12, 03:55 UTC | Jun 12, 08:20 UTC | 4h 25m |
| 2026-06-12 | CSH851 | SHA → TSA | Jun 12, 01:45 UTC | Jun 12, 02:40 UTC | 55m |
| 2026-06-11 | CSH9334 | SZX → SHA | Jun 11, 09:45 UTC | Jun 11, 09:55 UTC | 10m |
| 2026-06-11 | CSH9333 | SHA → SZX | Jun 11, 06:25 UTC | Jun 11, 07:10 UTC | 45m |
| 2026-06-10 | CSH9535 | PVG → SYX | Jun 10, 05:50 UTC | Jun 10, 09:45 UTC | 3h 55m |
| 2026-06-07 | CSH810 | HKG → SHA | Jun 7, 11:15 UTC | Jun 7, 12:20 UTC | 1h 5m |
| 2026-06-07 | CSH852 | TSA → SHA | Jun 7, 03:40 UTC | Jun 7, 09:30 UTC | 5h 50m |
| 2026-06-06 | CSH851 | SHA → TSA | Jun 6, 07:45 UTC | Jun 7, 02:25 UTC | 18h 40m |
| 2026-06-03 | CSH9536 | SYX → PVG | Jun 3, 09:05 UTC | Jun 4, 04:25 UTC | 19h 20m |
| 2026-06-03 | CSH9536 | SYX → PVG | Jun 3, 05:45 UTC | Jun 4, 04:25 UTC | 22h 40m |
| 2026-06-02 | CSH9535 | PVG → SYX | Jun 2, 09:40 UTC | Jun 3, 06:25 UTC | 20h 45m |
| 2026-06-02 | CSH9535 | PVG → SYX | Jun 2, 05:45 UTC | Jun 2, 06:35 UTC | 50m |
| 2026-05-21 | CSH9253 | SHA → HAK | May 21, 10:50 UTC | May 21, 11:05 UTC | 15m |
| 2026-05-19 | CSH9362 | ZUH → SHA | May 19, 14:15 UTC | May 19, 14:25 UTC | 10m |
| 2026-05-19 | CSH9361 | SHA → ZUH | May 19, 12:35 UTC | May 19, 12:55 UTC | 20m |
| 2026-05-17 | CSH818 | MFM → SHA | May 17, 06:00 UTC | May 17, 07:05 UTC | 1h 5m |
| 2026-05-17 | CSH817 | SHA → MFM | May 17, 03:40 UTC | May 17, 03:50 UTC | 10m |
| 2026-05-14 | CSH818 | MFM → SHA | May 14, 06:35 UTC | May 14, 06:55 UTC | 20m |
| 2026-05-14 | CSH817 | SHA → MFM | May 14, 04:45 UTC | May 14, 05:10 UTC | 25m |
| 2026-05-13 | CSH818 | MFM → SHA | May 13, 07:05 UTC | May 13, 07:20 UTC | 15m |
| 2026-05-13 | CSH818 | MFM → SHA | May 13, 06:10 UTC | May 13, 06:30 UTC | 20m |
| 2026-05-13 | CSH817 | SHA → MFM | May 13, 04:05 UTC | May 13, 04:30 UTC | 25m |
| 2026-05-12 | CSH818 | MFM → SHA | May 12, 06:50 UTC | May 12, 07:00 UTC | 10m |
| 2026-05-12 | CSH818 | MFM → SHA | May 12, 05:55 UTC | May 12, 06:15 UTC | 20m |
| 2026-05-12 | CSH817 | SHA → MFM | May 12, 03:35 UTC | May 12, 03:50 UTC | 15m |
| 2026-05-11 | CSH818 | MFM → SHA | May 11, 05:50 UTC | May 11, 06:10 UTC | 20m |
| 2026-05-11 | CSH817 | SHA → MFM | May 11, 03:55 UTC | May 11, 04:10 UTC | 15m |
| 2026-05-10 | CSH818 | MFM → SHA | May 10, 05:55 UTC | May 10, 06:55 UTC | 1h 0m |
| 2026-05-10 | CSH817 | SHA → MFM | May 10, 03:40 UTC | May 10, 04:00 UTC | 20m |
| 2026-05-03 | CSH9362 | ZUH → SHA | May 3, 14:00 UTC | May 3, 14:10 UTC | 10m |
| 2026-05-03 | CSH818 | MFM → SHA | May 3, 06:35 UTC | May 3, 07:35 UTC | 1h 0m |
| 2026-05-03 | CSH817 | SHA → MFM | May 3, 03:50 UTC | May 3, 04:15 UTC | 25m |
| 2026-04-26 | CSH9535 | PVG → SYX | Apr 26, 05:55 UTC | Apr 26, 09:50 UTC | 3h 55m |
| 2026-04-24 | CSH9260 | - | Apr 24, 11:15 UTC | Apr 24, 11:35 UTC | 20m |
| 2026-04-22 | CES5349 | SHA → SZX | Apr 22, 10:10 UTC | Apr 22, 11:05 UTC | 55m |
| 2026-04-19 | CSH9334 | SZX → SHA | Apr 19, 10:00 UTC | Apr 19, 10:10 UTC | 10m |
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-7396 page for operator, model, and routing details .