sensors Mode-S transponder
78083F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5637 · BOEING 737-800
- Hex
- 78083F
- Octal
- 36004077
- Decimal
- 7,866,431
- Country
- CN
- Tail
- B-5637
- Type
- B738
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 78083F 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 |
|---|---|---|---|
| CHH7746 | - | 4 | 2026-06-09 |
| CHH7210 | Hainan Airlines | 4 | 2026-06-11 |
| CHH7851 | Hainan Airlines | 2 | 2026-05-08 |
| CHH7834 | Hainan Airlines | 2 | 2026-06-03 |
| CHH7833 | Hainan Airlines | 2 | 2026-06-03 |
| CHH7280 | Hainan Airlines | 2 | 2026-06-12 |
| CHH7179 | Hainan Airlines | 2 | 2026-06-14 |
| CHH7774 | Hainan Airlines | 1 | 2026-05-07 |
| CHH7773 | Hainan Airlines | 1 | 2026-05-07 |
| CHH7765 | Hainan Airlines | 1 | 2026-06-09 |
| CHH7760 | Hainan Airlines | 1 | 2026-06-06 |
| CHH7759 | Hainan Airlines | 1 | 2026-06-06 |
| CHH7745 | - | 1 | 2026-06-05 |
| CHH7744 | Hainan Airlines | 1 | 2026-05-08 |
| CHH7743 | Hainan Airlines | 1 | 2026-05-07 |
| CHH7735 | Hainan Airlines | 1 | 2026-05-12 |
| CHH7725 | - | 1 | 2026-06-19 |
| CHH7579 | Hainan Airlines | 1 | 2026-06-12 |
| CHH7522 | - | 1 | 2026-06-18 |
| CHH7304 | Hainan Airlines | 1 | 2026-06-11 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | CHH7725 | - | Jun 19, 05:59 UTC | Jun 19, 06:10 UTC | 10m |
| 2026-06-18 | CHH7522 | - | Jun 18, 15:35 UTC | Jun 18, 15:50 UTC | 15m |
| 2026-06-14 | CHH7179 | PEK → SYX | Jun 14, 04:30 UTC | Jun 14, 04:45 UTC | 15m |
| 2026-06-13 | CHH7179 | PEK → SYX | Jun 13, 06:50 UTC | Jun 14, 04:45 UTC | 21h 55m |
| 2026-06-12 | CHH7579 | PEK → SYX | Jun 12, 13:25 UTC | Jun 13, 06:50 UTC | 17h 24m |
| 2026-06-12 | CHH7280 | SYX → PEK | Jun 12, 11:50 UTC | Jun 12, 12:00 UTC | 10m |
| 2026-06-12 | CHH7280 | SYX → PEK | Jun 12, 08:30 UTC | Jun 12, 08:45 UTC | 15m |
| 2026-06-11 | CHH7304 | TFU → SYX | Jun 11, 15:30 UTC | Jun 12, 06:10 UTC | 14h 41m |
| 2026-06-11 | CHH7210 | TNA → CAN | Jun 11, 09:50 UTC | Jun 12, 06:10 UTC | 20h 20m |
| 2026-06-11 | CHH7210 | TNA → CAN | Jun 11, 09:35 UTC | Jun 12, 06:10 UTC | 20h 36m |
| 2026-06-11 | CHH7210 | TNA → CAN | Jun 11, 04:25 UTC | Jun 12, 01:55 UTC | 21h 31m |
| 2026-06-10 | CHH7210 | TNA → CAN | Jun 10, 16:05 UTC | Jun 11, 15:30 UTC | 23h 25m |
| 2026-06-09 | CHH7765 | SZX → FUG | Jun 9, 23:00 UTC | Jun 9, 23:10 UTC | 10m |
| 2026-06-09 | CHH7746 | - | Jun 9, 08:30 UTC | Jun 9, 08:55 UTC | 25m |
| 2026-06-08 | CHH7023 | SYX → NKG | Jun 8, 23:30 UTC | Jun 8, 23:45 UTC | 15m |
| 2026-06-07 | CHH7026 | SZX → HAK | Jun 7, 17:35 UTC | Jun 7, 17:50 UTC | 15m |
| 2026-06-07 | CHH7746 | - | Jun 7, 15:35 UTC | Jun 7, 15:45 UTC | 10m |
| 2026-06-06 | CHH7760 | TNA → SZX | Jun 6, 19:30 UTC | Jun 6, 19:40 UTC | 10m |
| 2026-06-06 | CHH7759 | SZX → TNA | Jun 6, 12:54 UTC | Jun 6, 17:05 UTC | 4h 10m |
| 2026-06-06 | CHH7175 | SZX → TFU | Jun 6, 00:05 UTC | Jun 6, 00:15 UTC | 10m |
| 2026-06-05 | CHH7746 | - | Jun 5, 15:00 UTC | Jun 5, 15:10 UTC | 10m |
| 2026-06-05 | CHH7746 | - | Jun 5, 08:35 UTC | Jun 5, 08:55 UTC | 20m |
| 2026-06-05 | CHH7745 | - | Jun 5, 02:45 UTC | Jun 5, 03:00 UTC | 15m |
| 2026-06-03 | CHH7834 | TSN → URC | Jun 3, 11:20 UTC | Jun 3, 11:30 UTC | 10m |
| 2026-06-03 | CHH7833 | URC → TSN | Jun 3, 08:55 UTC | Jun 3, 09:20 UTC | 25m |
| 2026-05-23 | CHH7051 | HAK → HGH | May 23, 01:15 UTC | May 23, 06:05 UTC | 4h 49m |
| 2026-05-22 | CHH7209 | TNA → HRB | May 22, 04:15 UTC | May 22, 04:30 UTC | 15m |
| 2026-05-13 | CHH7275 | SZX → TFU | May 13, 06:30 UTC | May 13, 06:40 UTC | 10m |
| 2026-05-12 | CHH7735 | SZX → CGO | May 12, 22:15 UTC | May 12, 22:25 UTC | 10m |
| 2026-05-10 | CHH7079 | PEK → SYX | May 10, 00:39 UTC | May 10, 01:04 UTC | 25m |
| 2026-05-09 | CHH7146 | URC → PEK | May 9, 09:05 UTC | May 9, 09:20 UTC | 15m |
| 2026-05-08 | CHH7851 | URC → LHW | May 8, 23:05 UTC | May 8, 23:15 UTC | 10m |
| 2026-05-08 | CHH7744 | SZX → LIY | May 8, 12:55 UTC | May 8, 13:10 UTC | 15m |
| 2026-05-07 | CHH7743 | NGB → CGQ | May 7, 23:55 UTC | May 8, 00:09 UTC | 15m |
| 2026-05-07 | CHH7774 | KWE → SZX | May 7, 17:00 UTC | May 7, 17:15 UTC | 15m |
| 2026-05-07 | CHH7773 | SZX → KWE | May 7, 13:00 UTC | May 7, 13:10 UTC | 10m |
| 2026-05-07 | CHH7025 | HAK → SZX | May 7, 10:00 UTC | May 7, 10:15 UTC | 15m |
| 2026-05-01 | CHH7851 | URC → LHW | May 1, 23:20 UTC | May 1, 23:30 UTC | 10m |
| 2026-04-30 | CHH7834 | TSN → URC | Apr 30, 11:15 UTC | Apr 30, 11:35 UTC | 20m |
| 2026-04-30 | CHH7833 | URC → TSN | Apr 30, 09:15 UTC | Apr 30, 09:35 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-5637 page for operator, model, and routing details .