sensors Mode-S transponder
7808BC
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1995 · BOEING 737-800
- Hex
- 7808BC
- Octal
- 36004274
- Decimal
- 7,866,556
- Country
- CN
- Tail
- B-1995
- Type
- B738
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 7808BC 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 |
|---|---|---|---|
| CHH7528 | - | 3 | 2026-06-27 |
| CHH7301 | Hainan Airlines | 3 | 2026-06-15 |
| CHH7987 | Hainan Airlines | 2 | 2026-05-10 |
| CHH7809 | - | 2 | 2026-07-08 |
| CHH7773 | - | 2 | 2026-07-15 |
| CHH7732 | Hainan Airlines | 2 | 2026-05-06 |
| CHH7731 | Hainan Airlines | 2 | 2026-05-06 |
| CHH7613 | Hainan Airlines | 2 | 2026-07-07 |
| CHH7386 | - | 2 | 2026-06-16 |
| CHH7384 | - | 2 | 2026-06-26 |
| CHH7988 | Hainan Airlines | 1 | 2026-05-10 |
| CHH7982 | Hainan Airlines | 1 | 2026-04-21 |
| CHH7981 | Hainan Airlines | 1 | 2026-04-21 |
| CHH7815 | Hainan Airlines | 1 | 2026-06-20 |
| CHH7814 | - | 1 | 2026-07-07 |
| CHH7811 | Hainan Airlines | 1 | 2026-04-20 |
| CHH7803 | - | 1 | 2026-06-20 |
| CHH7777 | Hainan Airlines | 1 | 2026-04-19 |
| CHH7775 | Hainan Airlines | 1 | 2026-05-07 |
| CHH7774 | - | 1 | 2026-07-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | CHH6354 | - | Jul 18, 17:25 UTC | Jul 18, 17:45 UTC | 20m |
| 2026-07-18 | CHH6353 | - | Jul 18, 09:30 UTC | Jul 18, 09:40 UTC | 10m |
| 2026-07-18 | CHH7147 | - | Jul 18, 00:35 UTC | Jul 18, 00:55 UTC | 20m |
| 2026-07-17 | CHH7109 | - | Jul 17, 09:30 UTC | Jul 17, 09:45 UTC | 15m |
| 2026-07-16 | CHH7375 | - | Jul 16, 06:10 UTC | Jul 16, 06:20 UTC | 10m |
| 2026-07-15 | CHH7737 | - | Jul 15, 23:10 UTC | Jul 15, 23:20 UTC | 10m |
| 2026-07-15 | CHH7774 | - | Jul 15, 19:10 UTC | Jul 15, 19:45 UTC | 35m |
| 2026-07-15 | CHH7773 | - | Jul 15, 13:50 UTC | Jul 15, 14:00 UTC | 10m |
| 2026-07-14 | CHH7765 | - | Jul 14, 23:00 UTC | Jul 14, 23:15 UTC | 15m |
| 2026-07-10 | CHH7482 | - | Jul 10, 01:30 UTC | Jul 10, 10:05 UTC | 8h 35m |
| 2026-07-09 | CHH7644 | - | Jul 9, 08:40 UTC | Jul 9, 08:50 UTC | 10m |
| 2026-07-08 | CHH7105 | - | Jul 8, 23:15 UTC | Jul 8, 23:25 UTC | 10m |
| 2026-07-08 | CHH7809 | - | Jul 8, 07:50 UTC | Jul 8, 08:10 UTC | 20m |
| 2026-07-07 | CHH7613 | PEK → PVG | Jul 7, 23:50 UTC | Jul 8, 00:00 UTC | 10m |
| 2026-07-07 | CHH7814 | - | Jul 7, 16:20 UTC | Jul 7, 16:40 UTC | 20m |
| 2026-07-04 | CHH7668 | - | Jul 4, 09:00 UTC | Jul 4, 09:20 UTC | 20m |
| 2026-07-02 | CHH7308 | - | Jul 2, 00:40 UTC | Jul 2, 16:15 UTC | 15h 35m |
| 2026-06-27 | CHH7528 | - | Jun 27, 05:35 UTC | Jun 27, 12:55 UTC | 7h 20m |
| 2026-06-26 | CHH7528 | - | Jun 26, 15:10 UTC | Jun 27, 12:55 UTC | 21h 45m |
| 2026-06-26 | CHH7528 | - | Jun 26, 14:35 UTC | Jun 27, 12:55 UTC | 22h 20m |
| 2026-06-26 | CHH7384 | - | Jun 26, 10:44 UTC | Jun 27, 05:49 UTC | 19h 5m |
| 2026-06-26 | CHH7384 | - | Jun 26, 05:19 UTC | Jun 26, 15:10 UTC | 9h 50m |
| 2026-06-23 | CHH7809 | - | Jun 23, 06:49 UTC | Jun 23, 07:05 UTC | 15m |
| 2026-06-20 | CHH7815 | PEK → CAN | Jun 20, 12:39 UTC | Jun 20, 12:59 UTC | 20m |
| 2026-06-20 | CHH7803 | - | Jun 20, 01:34 UTC | Jun 20, 01:55 UTC | 20m |
| 2026-06-16 | CHH7386 | - | Jun 16, 01:55 UTC | Jun 16, 09:55 UTC | 8h 0m |
| 2026-06-15 | CHH7386 | - | Jun 15, 13:05 UTC | Jun 16, 09:55 UTC | 20h 50m |
| 2026-06-15 | CHH7301 | SYX → TFU | Jun 15, 12:35 UTC | Jun 16, 09:55 UTC | 21h 20m |
| 2026-06-15 | CHH7301 | SYX → TFU | Jun 15, 05:30 UTC | Jun 16, 02:09 UTC | 20h 40m |
| 2026-06-15 | CHH7301 | SYX → TFU | Jun 15, 01:45 UTC | Jun 15, 13:05 UTC | 11h 20m |
| 2026-06-05 | CHH7535 | PEK → CSX | Jun 5, 15:15 UTC | Jun 5, 15:30 UTC | 15m |
| 2026-06-05 | CHH7338 | XIY → PEK | Jun 5, 11:35 UTC | Jun 5, 12:00 UTC | 25m |
| 2026-06-03 | CHH7137 | PEK → XIY | Jun 3, 23:00 UTC | Jun 3, 23:20 UTC | 20m |
| 2026-05-23 | CHH7044 | TNA → HAK | May 23, 02:10 UTC | May 23, 08:05 UTC | 5h 54m |
| 2026-05-21 | CHH7016 | SZX → HAK | May 21, 10:55 UTC | May 21, 11:15 UTC | 20m |
| 2026-05-20 | CHH7015 | HAK → SZX | May 20, 08:55 UTC | May 20, 12:00 UTC | 3h 5m |
| 2026-05-18 | CHH7054 | HGH → HAK | May 18, 02:35 UTC | May 18, 06:10 UTC | 3h 35m |
| 2026-05-17 | CHH7725 | SZX → PVG | May 17, 06:00 UTC | May 17, 06:10 UTC | 10m |
| 2026-05-17 | CHH7726 | PVG → SZX | May 17, 01:15 UTC | May 17, 01:45 UTC | 30m |
| 2026-05-10 | CHH7988 | TPE → PEK | May 10, 05:10 UTC | May 10, 05:40 UTC | 30m |
| 2026-05-10 | CHH7987 | PEK → TPE | May 10, 01:50 UTC | May 10, 02:30 UTC | 40m |
| 2026-05-09 | CHH7987 | PEK → TPE | May 9, 23:44 UTC | May 9, 23:55 UTC | 10m |
| 2026-05-09 | CHH7706 | SZX → PEK | May 9, 05:25 UTC | May 9, 05:35 UTC | 10m |
| 2026-05-09 | CHH7701 | PEK → SZX | May 9, 00:50 UTC | May 9, 01:10 UTC | 20m |
| 2026-05-08 | CHH7710 | SZX → PEK | May 8, 09:19 UTC | May 8, 09:30 UTC | 10m |
| 2026-05-08 | CHH7762 | NGB → SZX | May 8, 04:19 UTC | May 8, 04:39 UTC | 20m |
| 2026-05-07 | CHH7761 | SZX → NGB | May 7, 22:30 UTC | May 7, 22:45 UTC | 15m |
| 2026-05-07 | CHH7775 | SZX → TYN | May 7, 05:40 UTC | May 7, 05:50 UTC | 10m |
| 2026-05-06 | CHH7732 | SZX → SYX | May 6, 15:00 UTC | May 6, 15:20 UTC | 20m |
| 2026-05-06 | CHH7731 | SYX → SZX | May 6, 00:01 UTC | May 6, 00:15 UTC | 15m |
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-1995 page for operator, model, and routing details .