sensors Mode-S transponder
7800F6
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5833 · BOEING 737-800
- Hex
- 7800F6
- Octal
- 36000366
- Decimal
- 7,864,566
- Country
- CN
- Tail
- B-5833
- Type
- B738
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 7800F6 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 |
|---|---|---|---|
| CSH9068 | Shanghai Airlines | 4 | 2026-06-07 |
| CSH9358 | Shanghai Airlines | 2 | 2026-06-10 |
| CSH9252 | Shanghai Airlines | 2 | 2026-06-12 |
| CSH9251 | Shanghai Airlines | 2 | 2026-05-09 |
| CSH9084 | Shanghai Airlines | 2 | 2026-06-08 |
| CSH818 | - | 2 | 2026-06-21 |
| CSH817 | - | 2 | 2026-06-21 |
| CSH9535 | - | 1 | 2026-07-11 |
| CSH9374 | - | 1 | 2026-07-13 |
| CSH9373 | Shanghai Airlines | 1 | 2026-04-14 |
| CSH9362 | Shanghai Airlines | 1 | 2026-06-21 |
| CSH9361 | Shanghai Airlines | 1 | 2026-06-21 |
| CSH9357 | Shanghai Airlines | 1 | 2026-06-10 |
| CSH9305 | - | 1 | 2026-07-14 |
| CSH9293 | - | 1 | 2026-06-24 |
| CSH9290 | - | 1 | 2026-05-08 |
| CSH9282 | Shanghai Airlines | 1 | 2026-05-17 |
| CSH9257 | - | 1 | 2026-06-28 |
| CSH9253 | Shanghai Airlines | 1 | 2026-05-09 |
| CSH9130 | Shanghai Airlines | 1 | 2026-05-19 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CSH9305 | - | Jul 14, 03:20 UTC | Jul 14, 03:30 UTC | 10m |
| 2026-07-13 | CSH9374 | - | Jul 13, 14:40 UTC | Jul 13, 16:00 UTC | 1h 20m |
| 2026-07-11 | CSH9535 | - | Jul 11, 05:55 UTC | Jul 11, 10:15 UTC | 4h 20m |
| 2026-06-28 | CSH9257 | - | Jun 28, 10:19 UTC | Jun 28, 10:35 UTC | 15m |
| 2026-06-27 | CSH9088 | - | Jun 27, 03:15 UTC | Jun 27, 03:30 UTC | 15m |
| 2026-06-25 | - | - | Jun 25, 23:39 UTC | Jun 26, 00:20 UTC | 40m |
| 2026-06-24 | CSH9293 | - | Jun 24, 00:40 UTC | Jun 24, 00:49 UTC | 10m |
| 2026-06-21 | CSH9362 | ZUH → SHA | Jun 21, 13:39 UTC | Jun 21, 13:50 UTC | 10m |
| 2026-06-21 | CSH9361 | SHA → ZUH | Jun 21, 11:15 UTC | Jun 21, 11:40 UTC | 25m |
| 2026-06-21 | CSH818 | - | Jun 21, 06:10 UTC | Jun 21, 07:14 UTC | 1h 5m |
| 2026-06-21 | CSH817 | - | Jun 21, 03:40 UTC | Jun 21, 04:04 UTC | 25m |
| 2026-06-20 | CSH818 | - | Jun 20, 05:39 UTC | Jun 21, 03:05 UTC | 21h 25m |
| 2026-06-20 | CSH817 | - | Jun 20, 03:14 UTC | Jun 20, 04:09 UTC | 55m |
| 2026-06-12 | CSH9252 | HAK → SHA | Jun 12, 04:45 UTC | Jun 12, 07:55 UTC | 3h 10m |
| 2026-06-10 | CSH9358 | ZUH → PVG | Jun 10, 11:00 UTC | Jun 10, 11:50 UTC | 50m |
| 2026-06-10 | CSH9357 | PVG → ZUH | Jun 10, 09:10 UTC | Jun 10, 09:30 UTC | 20m |
| 2026-06-08 | CSH9084 | SHE → PVG | Jun 8, 10:20 UTC | Jun 8, 10:35 UTC | 15m |
| 2026-06-07 | CSH9068 | CGQ → PVG | Jun 7, 13:40 UTC | Jun 8, 10:35 UTC | 20h 55m |
| 2026-06-07 | CSH9068 | CGQ → PVG | Jun 7, 13:20 UTC | Jun 8, 10:35 UTC | 21h 15m |
| 2026-06-07 | CSH9068 | CGQ → PVG | Jun 7, 06:00 UTC | Jun 7, 14:05 UTC | 8h 5m |
| 2026-06-04 | - | - | Jun 4, 02:15 UTC | Jun 4, 02:25 UTC | 10m |
| 2026-06-03 | CSH9358 | ZUH → PVG | Jun 3, 11:05 UTC | Jun 3, 12:20 UTC | 1h 15m |
| 2026-06-02 | CSH9080 | CGQ → PVG | Jun 2, 23:55 UTC | Jun 3, 09:45 UTC | 9h 50m |
| 2026-05-30 | CSH806 | MFM → PVG | May 30, 05:40 UTC | May 30, 06:35 UTC | 55m |
| 2026-05-30 | CSH805 | PVG → MFM | May 30, 02:45 UTC | May 30, 04:00 UTC | 1h 15m |
| 2026-05-27 | CSH9084 | SHE → PVG | May 27, 10:10 UTC | May 27, 10:40 UTC | 30m |
| 2026-05-19 | CSH9130 | HLD → PVG | May 19, 11:05 UTC | May 19, 11:55 UTC | 50m |
| 2026-05-17 | CSH9282 | SHE → PVG | May 17, 13:55 UTC | May 17, 14:30 UTC | 35m |
| 2026-05-09 | CSH9251 | PVG → HAK | May 9, 14:20 UTC | May 10, 08:45 UTC | 18h 25m |
| 2026-05-09 | CSH9253 | SHA → HAK | May 9, 10:40 UTC | May 9, 11:00 UTC | 20m |
| 2026-05-08 | CSH9290 | - | May 8, 05:24 UTC | May 8, 05:44 UTC | 20m |
| 2026-04-29 | CSH9124 | TVS → PVG | Apr 29, 04:05 UTC | Apr 29, 04:20 UTC | 15m |
| 2026-04-25 | CSH9064 | HRB → PVG | Apr 25, 10:50 UTC | Apr 25, 11:25 UTC | 35m |
| 2026-04-19 | CSH9068 | CGQ → PVG | Apr 19, 13:10 UTC | Apr 19, 13:45 UTC | 35m |
| 2026-04-16 | CSH828 | ICN → PVG | Apr 16, 10:19 UTC | Apr 16, 10:49 UTC | 30m |
| 2026-04-16 | CSH827 | PVG → ICN | Apr 16, 08:35 UTC | Apr 16, 09:05 UTC | 30m |
| 2026-04-14 | CSH9373 | PVG → ZHA | Apr 14, 12:30 UTC | Apr 14, 12:45 UTC | 15m |
| 2026-04-13 | CSH9252 | - | Apr 13, 08:45 UTC | Apr 13, 09:30 UTC | 45m |
| 2026-04-13 | CSH9251 | PVG → HAK | Apr 13, 05:40 UTC | Apr 13, 06:00 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-5833 page for operator, model, and routing details .