sensors Mode-S transponder
78000A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6103 · BOEING 737-800
- Hex
- 78000A
- Octal
- 36000012
- Decimal
- 7,864,330
- Country
- CN
- Tail
- B-6103
- Type
- B738
- Flights observed
- 97
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 78000A 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 |
|---|---|---|---|
| CHH7322 | - | 10 | 2026-07-11 |
| CHH7987 | - | 5 | 2026-06-15 |
| CHH7988 | - | 4 | 2026-06-15 |
| CHH7370 | - | 3 | 2026-05-03 |
| CHH7745 | - | 2 | 2026-05-22 |
| CHH7713 | Hainan Airlines | 2 | 2026-05-20 |
| CHH7547 | - | 2 | 2026-06-30 |
| CHH7291 | - | 2 | 2026-06-29 |
| CHH720 | Hainan Airlines | 2 | 2026-06-03 |
| CHH7120 | Hainan Airlines | 2 | 2026-05-14 |
| CHH7070 | Hainan Airlines | 2 | 2026-05-17 |
| CHH706 | Hainan Airlines | 2 | 2026-06-03 |
| CHH705 | Hainan Airlines | 2 | 2026-06-03 |
| CHH7869 | - | 1 | 2026-07-09 |
| CHH7803 | - | 1 | 2026-07-04 |
| CHH7801 | Hainan Airlines | 1 | 2026-06-08 |
| CHH7777 | Hainan Airlines | 1 | 2026-06-06 |
| CHH7767 | Hainan Airlines | 1 | 2026-05-19 |
| CHH7765 | Hainan Airlines | 1 | 2026-04-18 |
| CHH7763 | Hainan Airlines | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CHH7475 | - | Jul 13, 08:01 UTC | Jul 13, 08:10 UTC | 10m |
| 2026-07-11 | CHH7322 | - | Jul 11, 00:35 UTC | Jul 11, 00:50 UTC | 15m |
| 2026-07-10 | CHH7725 | - | Jul 10, 05:05 UTC | Jul 10, 05:15 UTC | 10m |
| 2026-07-09 | CHH7759 | - | Jul 9, 10:35 UTC | Jul 9, 10:55 UTC | 20m |
| 2026-07-09 | CHH7869 | - | Jul 9, 06:05 UTC | Jul 9, 06:15 UTC | 10m |
| 2026-07-08 | CHH7137 | - | Jul 8, 23:05 UTC | Jul 8, 23:25 UTC | 20m |
| 2026-07-07 | CHH6394 | - | Jul 7, 17:00 UTC | Jul 7, 17:10 UTC | 10m |
| 2026-07-06 | CHH7744 | - | Jul 6, 16:40 UTC | Jul 6, 16:50 UTC | 10m |
| 2026-07-06 | CHH7743 | NGB → CGQ | Jul 6, 00:45 UTC | Jul 6, 00:55 UTC | 10m |
| 2026-07-05 | CHH7748 | TYN → SZX | Jul 5, 17:35 UTC | Jul 5, 18:00 UTC | 25m |
| 2026-07-05 | CHH7747 | - | Jul 5, 09:15 UTC | Jul 5, 09:25 UTC | 10m |
| 2026-07-05 | CHH7175 | - | Jul 5, 02:15 UTC | Jul 5, 02:25 UTC | 10m |
| 2026-07-04 | CHH7021 | - | Jul 4, 23:10 UTC | Jul 4, 23:25 UTC | 15m |
| 2026-07-04 | CHH7803 | - | Jul 4, 01:40 UTC | Jul 4, 01:55 UTC | 15m |
| 2026-07-03 | CHH7481 | - | Jul 3, 06:05 UTC | Jul 3, 06:15 UTC | 10m |
| 2026-07-02 | CHH7369 | - | Jul 2, 00:25 UTC | Jul 2, 10:05 UTC | 9h 40m |
| 2026-07-01 | CHH7084 | - | Jul 1, 02:25 UTC | Jul 1, 15:20 UTC | 12h 55m |
| 2026-06-30 | CHH7547 | - | Jun 30, 13:05 UTC | Jul 1, 02:35 UTC | 13h 30m |
| 2026-06-30 | CHH6215 | - | Jun 30, 02:35 UTC | Jun 30, 02:50 UTC | 15m |
| 2026-06-29 | CHH7164 | - | Jun 29, 05:09 UTC | Jun 29, 08:50 UTC | 3h 40m |
| 2026-06-29 | CHH7291 | - | Jun 29, 00:05 UTC | Jun 29, 00:20 UTC | 15m |
| 2026-06-28 | CHH7638 | - | Jun 28, 07:34 UTC | Jun 28, 07:44 UTC | 10m |
| 2026-06-27 | CHH7103 | - | Jun 27, 15:10 UTC | Jun 27, 15:19 UTC | 10m |
| 2026-06-27 | CHH7291 | - | Jun 27, 00:05 UTC | Jun 27, 05:29 UTC | 5h 25m |
| 2026-06-20 | CHH7322 | - | Jun 20, 23:29 UTC | Jun 21, 11:34 UTC | 12h 5m |
| 2026-06-20 | CHH7322 | - | Jun 20, 04:20 UTC | Jun 21, 00:45 UTC | 20h 25m |
| 2026-06-19 | CHH7322 | - | Jun 19, 23:39 UTC | Jun 20, 04:29 UTC | 4h 50m |
| 2026-06-19 | CHH7322 | - | Jun 19, 00:49 UTC | Jun 20, 00:04 UTC | 23h 15m |
| 2026-06-18 | CHH7322 | - | Jun 18, 23:50 UTC | Jun 19, 01:04 UTC | 1h 14m |
| 2026-06-18 | CHH7322 | - | Jun 18, 05:35 UTC | Jun 19, 01:04 UTC | 19h 29m |
| 2026-06-18 | CHH7322 | - | Jun 18, 01:20 UTC | Jun 19, 00:20 UTC | 22h 59m |
| 2026-06-15 | CHH7988 | - | Jun 15, 05:30 UTC | Jun 15, 05:55 UTC | 25m |
| 2026-06-15 | CHH7987 | - | Jun 15, 02:20 UTC | Jun 15, 03:35 UTC | 1h 15m |
| 2026-06-11 | CHH7322 | PVG → SYX | Jun 11, 23:45 UTC | Jun 12, 04:25 UTC | 4h 41m |
| 2026-06-11 | CHH7322 | PVG → SYX | Jun 11, 00:35 UTC | Jun 12, 00:15 UTC | 23h 40m |
| 2026-06-11 | CHH7613 | PEK → PVG | Jun 11, 00:25 UTC | Jun 11, 00:40 UTC | 15m |
| 2026-06-10 | CHH7247 | PEK → TFU | Jun 10, 05:15 UTC | Jun 10, 05:30 UTC | 15m |
| 2026-06-09 | CHH7547 | PEK → TFU | Jun 9, 12:15 UTC | Jun 9, 12:30 UTC | 15m |
| 2026-06-09 | CHH440 | NRT → PEK | Jun 9, 05:30 UTC | Jun 9, 07:50 UTC | 2h 20m |
| 2026-06-08 | CHH439 | PEK → NRT | Jun 8, 23:30 UTC | Jun 9, 02:15 UTC | 2h 45m |
| 2026-06-08 | CHH7134 | - | Jun 8, 15:25 UTC | Jun 8, 15:45 UTC | 20m |
| 2026-06-08 | CHH7133 | - | Jun 8, 12:10 UTC | Jun 8, 12:35 UTC | 25m |
| 2026-06-08 | CHH7801 | PEK → CAN | Jun 8, 00:50 UTC | Jun 8, 01:05 UTC | 15m |
| 2026-06-07 | CHH7125 | PEK → DOY | Jun 7, 12:20 UTC | Jun 7, 12:30 UTC | 10m |
| 2026-06-07 | CHH7988 | TPE → PEK | Jun 7, 05:15 UTC | Jun 7, 05:35 UTC | 20m |
| 2026-06-06 | CHH7987 | PEK → TPE | Jun 6, 23:55 UTC | Jun 7, 02:40 UTC | 2h 45m |
| 2026-06-06 | CHH7777 | PEK → BAR | Jun 6, 06:10 UTC | Jun 6, 09:04 UTC | 2h 55m |
| 2026-06-06 | CHH7198 | LHW → PEK | Jun 6, 03:40 UTC | Jun 6, 04:00 UTC | 20m |
| 2026-06-05 | CHH7297 | CAN → TYN | Jun 5, 12:50 UTC | Jun 5, 13:15 UTC | 25m |
| 2026-06-05 | CHH7238 | XIY → PEK | Jun 5, 03:15 UTC | Jun 5, 08:20 UTC | 5h 5m |
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-6103 page for operator, model, and routing details .