sensors Mode-S transponder
78030C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5316 · BOEING 737-800
- Hex
- 78030C
- Octal
- 36001414
- Decimal
- 7,865,100
- Country
- CN
- Tail
- B-5316
- Type
- B738
- Flights observed
- 38
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 78030C 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSH818 | - | 7 | 2026-06-14 |
| CSH817 | - | 7 | 2026-06-14 |
| CSH9536 | - | 3 | 2026-07-13 |
| CSH9537 | - | 2 | 2026-06-20 |
| CSH9531 | - | 2 | 2026-07-01 |
| CSH9362 | - | 2 | 2026-07-04 |
| CSH9253 | - | 2 | 2026-06-26 |
| CSH9251 | Shanghai Airlines | 2 | 2026-06-08 |
| CSH9540 | - | 1 | 2026-07-12 |
| CSH9532 | - | 1 | 2026-07-01 |
| CSH9373 | Shanghai Airlines | 1 | 2026-05-03 |
| CSH9361 | - | 1 | 2026-07-04 |
| CSH9296 | - | 1 | 2026-04-22 |
| CSH9290 | - | 1 | 2026-07-19 |
| CSH9278 | - | 1 | 2026-07-14 |
| CSH9130 | - | 1 | 2026-07-09 |
| CSH9080 | Shanghai Airlines | 1 | 2026-05-04 |
| CSH9068 | - | 1 | 2026-07-10 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | CSH9290 | - | Jul 19, 06:50 UTC | Jul 19, 07:30 UTC | 40m |
| 2026-07-14 | CSH9278 | - | Jul 14, 02:05 UTC | Jul 14, 02:40 UTC | 35m |
| 2026-07-13 | CSH9536 | - | Jul 13, 06:05 UTC | Jul 13, 11:10 UTC | 5h 5m |
| 2026-07-12 | CSH9540 | - | Jul 12, 08:15 UTC | Jul 13, 06:35 UTC | 22h 20m |
| 2026-07-10 | CSH9068 | - | Jul 10, 13:15 UTC | Jul 11, 04:15 UTC | 15h 0m |
| 2026-07-09 | CSH9130 | - | Jul 9, 13:55 UTC | Jul 9, 14:35 UTC | 40m |
| 2026-07-07 | - | - | Jul 7, 05:25 UTC | Jul 7, 05:55 UTC | 30m |
| 2026-07-05 | CSH9536 | - | Jul 5, 06:35 UTC | Jul 5, 11:30 UTC | 4h 55m |
| 2026-07-04 | CSH9362 | - | Jul 4, 16:15 UTC | Jul 4, 16:25 UTC | 10m |
| 2026-07-04 | CSH9361 | - | Jul 4, 14:30 UTC | Jul 4, 14:55 UTC | 25m |
| 2026-07-01 | CSH9532 | - | Jul 1, 08:35 UTC | Jul 1, 08:45 UTC | 10m |
| 2026-07-01 | CSH9531 | - | Jul 1, 05:40 UTC | Jul 1, 05:55 UTC | 15m |
| 2026-06-30 | CSH9531 | - | Jun 30, 09:25 UTC | Jul 1, 05:55 UTC | 20h 30m |
| 2026-06-28 | CSH9536 | - | Jun 28, 06:00 UTC | Jun 28, 11:50 UTC | 5h 50m |
| 2026-06-26 | CSH9253 | - | Jun 26, 11:40 UTC | Jun 26, 14:44 UTC | 3h 5m |
| 2026-06-20 | CSH9537 | - | Jun 20, 00:44 UTC | Jun 20, 04:20 UTC | 3h 35m |
| 2026-06-14 | CSH818 | - | Jun 14, 06:05 UTC | Jun 14, 06:50 UTC | 45m |
| 2026-06-14 | CSH817 | - | Jun 14, 03:00 UTC | Jun 14, 04:10 UTC | 1h 10m |
| 2026-06-11 | CSH9253 | SHA → HAK | Jun 11, 10:35 UTC | Jun 11, 14:45 UTC | 4h 10m |
| 2026-06-10 | CSH818 | MFM → SHA | Jun 10, 06:00 UTC | Jun 10, 06:55 UTC | 55m |
| 2026-06-10 | CSH817 | SHA → MFM | Jun 10, 03:55 UTC | Jun 10, 04:05 UTC | 10m |
| 2026-06-09 | CSH818 | MFM → SHA | Jun 9, 06:05 UTC | Jun 9, 07:10 UTC | 1h 5m |
| 2026-06-09 | CSH817 | SHA → MFM | Jun 9, 03:20 UTC | Jun 9, 04:00 UTC | 40m |
| 2026-06-08 | CSH817 | SHA → MFM | Jun 8, 07:25 UTC | Jun 9, 04:00 UTC | 20h 35m |
| 2026-06-08 | CSH9251 | PVG → HAK | Jun 8, 04:40 UTC | Jun 8, 05:00 UTC | 20m |
| 2026-06-07 | CSH9251 | PVG → HAK | Jun 7, 05:40 UTC | Jun 8, 05:00 UTC | 23h 20m |
| 2026-06-02 | CSH818 | MFM → SHA | Jun 2, 05:45 UTC | Jun 2, 06:40 UTC | 55m |
| 2026-06-02 | CSH817 | SHA → MFM | Jun 2, 03:55 UTC | Jun 2, 04:10 UTC | 15m |
| 2026-05-04 | CSH9080 | CGQ → PVG | May 4, 23:40 UTC | May 5, 00:10 UTC | 30m |
| 2026-05-03 | CSH9373 | PVG → ZHA | May 3, 12:25 UTC | May 3, 15:50 UTC | 3h 25m |
| 2026-04-22 | CSH9296 | - | Apr 22, 08:25 UTC | Apr 22, 08:40 UTC | 15m |
| 2026-04-20 | CSH818 | MFM → SHA | Apr 20, 07:40 UTC | Apr 20, 07:50 UTC | 10m |
| 2026-04-20 | CSH818 | MFM → SHA | Apr 20, 06:45 UTC | Apr 20, 07:05 UTC | 20m |
| 2026-04-20 | CSH817 | SHA → MFM | Apr 20, 04:05 UTC | Apr 20, 04:35 UTC | 30m |
| 2026-04-18 | CSH9537 | SHA → SYX | Apr 18, 00:45 UTC | Apr 18, 01:05 UTC | 20m |
| 2026-04-17 | CSH9362 | - | Apr 17, 14:05 UTC | Apr 17, 14:15 UTC | 10m |
| 2026-04-17 | CSH818 | MFM → SHA | Apr 17, 06:05 UTC | Apr 17, 07:05 UTC | 1h 0m |
| 2026-04-17 | CSH817 | SHA → MFM | Apr 17, 03:25 UTC | Apr 17, 04:25 UTC | 1h 0m |
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-5316 page for operator, model, and routing details .