sensors Mode-S transponder
7805D3
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5462 · BOEING 737-800
- Hex
- 7805D3
- Octal
- 36002723
- Decimal
- 7,865,811
- Country
- CN
- Tail
- B-5462
- Type
- B738
- Flights observed
- 62
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 20h ago
Last known position
Country allocation
The ICAO 24-bit address 7805D3 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 |
|---|---|---|---|
| CHH7468 | Hainan Airlines | 3 | 2026-04-20 |
| CHH7386 | - | 3 | 2026-06-25 |
| CHH7120 | - | 3 | 2026-07-08 |
| CHH7016 | Hainan Airlines | 3 | 2026-04-21 |
| CHH7982 | Hainan Airlines | 2 | 2026-05-05 |
| CHH7803 | - | 2 | 2026-07-16 |
| CHH7776 | Hainan Airlines | 2 | 2026-06-28 |
| CHH7654 | Hainan Airlines | 2 | 2026-05-08 |
| CHH7371 | Hainan Airlines | 2 | 2026-06-20 |
| CHH7304 | Hainan Airlines | 2 | 2026-06-24 |
| CHH7037 | Hainan Airlines | 2 | 2026-04-28 |
| CHH7015 | Hainan Airlines | 2 | 2026-04-19 |
| CHH6394 | - | 2 | 2026-06-19 |
| CHH7981 | Hainan Airlines | 1 | 2026-05-05 |
| CHH7810 | - | 1 | 2026-07-16 |
| CHH7809 | - | 1 | 2026-07-15 |
| CHH7773 | - | 1 | 2026-06-29 |
| CHH7737 | - | 1 | 2026-06-29 |
| CHH7732 | - | 1 | 2026-06-29 |
| CHH7731 | - | 1 | 2026-06-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CHH6383 | - | Jul 17, 02:05 UTC | Jul 17, 02:25 UTC | 20m |
| 2026-07-16 | CHH7134 | - | Jul 16, 15:19 UTC | Jul 16, 15:40 UTC | 20m |
| 2026-07-16 | CHH7133 | - | Jul 16, 12:20 UTC | Jul 16, 12:44 UTC | 25m |
| 2026-07-16 | CHH7810 | - | Jul 16, 10:00 UTC | Jul 16, 10:10 UTC | 10m |
| 2026-07-16 | CHH7803 | - | Jul 16, 01:50 UTC | Jul 16, 02:10 UTC | 20m |
| 2026-07-15 | CHH7809 | - | Jul 15, 07:05 UTC | Jul 15, 07:20 UTC | 15m |
| 2026-07-13 | CHH748 | - | Jul 13, 04:15 UTC | Jul 13, 14:20 UTC | 10h 5m |
| 2026-07-13 | CHH747 | - | Jul 13, 02:05 UTC | Jul 13, 02:30 UTC | 25m |
| 2026-07-12 | CHH722 | - | Jul 12, 12:25 UTC | Jul 12, 12:40 UTC | 15m |
| 2026-07-12 | CHH721 | - | Jul 12, 10:40 UTC | Jul 12, 11:01 UTC | 20m |
| 2026-07-08 | CHH7120 | - | Jul 8, 12:30 UTC | Jul 8, 12:45 UTC | 15m |
| 2026-07-07 | CHH7803 | - | Jul 7, 01:50 UTC | Jul 7, 02:10 UTC | 20m |
| 2026-07-06 | CHH7193 | - | Jul 6, 12:20 UTC | Jul 6, 12:30 UTC | 10m |
| 2026-07-05 | CHH7125 | - | Jul 5, 15:25 UTC | Jul 5, 15:35 UTC | 10m |
| 2026-06-30 | CHH7375 | - | Jun 30, 06:35 UTC | Jun 30, 06:50 UTC | 15m |
| 2026-06-29 | CHH7737 | - | Jun 29, 22:49 UTC | Jun 29, 22:59 UTC | 10m |
| 2026-06-29 | CHH7773 | - | Jun 29, 12:00 UTC | Jun 29, 12:14 UTC | 15m |
| 2026-06-29 | CHH7732 | - | Jun 29, 10:29 UTC | Jun 29, 10:44 UTC | 15m |
| 2026-06-28 | CHH7731 | - | Jun 28, 23:54 UTC | Jun 29, 00:05 UTC | 10m |
| 2026-06-28 | CHH7776 | TYN → SZX | Jun 28, 18:40 UTC | Jun 28, 18:59 UTC | 20m |
| 2026-06-28 | CHH7776 | TYN → SZX | Jun 28, 13:45 UTC | Jun 28, 13:55 UTC | 10m |
| 2026-06-27 | CHH7730 | - | Jun 27, 17:44 UTC | Jun 27, 17:55 UTC | 10m |
| 2026-06-27 | CHH7726 | - | Jun 27, 02:29 UTC | Jun 27, 02:55 UTC | 25m |
| 2026-06-25 | CHH7386 | - | Jun 25, 09:40 UTC | Jun 26, 04:24 UTC | 18h 45m |
| 2026-06-25 | CHH7386 | - | Jun 25, 05:15 UTC | Jun 26, 04:24 UTC | 23h 10m |
| 2026-06-25 | CHH7386 | - | Jun 25, 04:40 UTC | Jun 25, 10:20 UTC | 5h 40m |
| 2026-06-24 | CHH7304 | TFU → SYX | Jun 24, 05:29 UTC | Jun 25, 04:40 UTC | 23h 10m |
| 2026-06-24 | CHH7304 | TFU → SYX | Jun 24, 00:40 UTC | Jun 24, 05:59 UTC | 5h 20m |
| 2026-06-23 | CHH7388 | KHN → SYX | Jun 23, 16:05 UTC | Jun 23, 16:29 UTC | 25m |
| 2026-06-22 | CHH7322 | - | Jun 22, 11:44 UTC | Jun 23, 01:10 UTC | 13h 25m |
| 2026-06-22 | CHH7572 | CKG → HAK | Jun 22, 01:55 UTC | Jun 22, 09:00 UTC | 7h 5m |
| 2026-06-20 | CHH7371 | HAK → CKG | Jun 20, 01:05 UTC | Jun 20, 06:54 UTC | 5h 50m |
| 2026-06-19 | CHH6394 | - | Jun 19, 14:24 UTC | Jun 19, 14:39 UTC | 15m |
| 2026-06-19 | CHH7371 | HAK → CKG | Jun 19, 06:49 UTC | Jun 19, 06:59 UTC | 10m |
| 2026-06-18 | CHH7272 | KWE → CAN | Jun 18, 15:10 UTC | Jun 18, 15:20 UTC | 10m |
| 2026-06-18 | CHH7271 | CAN → KWE | Jun 18, 05:05 UTC | Jun 18, 05:15 UTC | 10m |
| 2026-05-16 | CHH7306 | TFU → SYX | May 16, 01:00 UTC | May 16, 07:11 UTC | 6h 11m |
| 2026-05-09 | CHH7135 | PEK → CSX | May 9, 23:15 UTC | May 9, 23:30 UTC | 15m |
| 2026-05-08 | CHH7654 | JUH → TYN | May 8, 14:40 UTC | May 9, 08:40 UTC | 18h 0m |
| 2026-05-08 | CHH7653 | TYN → KWE | May 8, 04:25 UTC | May 8, 12:34 UTC | 8h 10m |
| 2026-05-05 | CHH7982 | TPE → CAN | May 5, 05:45 UTC | May 5, 05:55 UTC | 10m |
| 2026-05-05 | CHH7982 | TPE → CAN | May 5, 04:15 UTC | May 5, 04:50 UTC | 35m |
| 2026-05-05 | CHH7981 | CAN → TPE | May 5, 00:10 UTC | May 5, 01:40 UTC | 1h 30m |
| 2026-05-02 | CHH7654 | JUH → TYN | May 2, 12:35 UTC | May 2, 15:40 UTC | 3h 5m |
| 2026-05-02 | CHH7216 | NKG → HAK | May 2, 04:15 UTC | May 2, 09:30 UTC | 5h 15m |
| 2026-05-01 | CHH7120 | PVG → HAK | May 1, 05:10 UTC | May 1, 10:30 UTC | 5h 20m |
| 2026-04-29 | CHH7535 | PEK → CSX | Apr 29, 15:10 UTC | Apr 29, 15:25 UTC | 15m |
| 2026-04-29 | CHH7163 | - | Apr 29, 08:20 UTC | Apr 29, 08:34 UTC | 15m |
| 2026-04-28 | CHH7037 | HAK → HFE | Apr 28, 10:15 UTC | Apr 29, 08:34 UTC | 22h 20m |
| 2026-04-27 | CHH7037 | HAK → HFE | Apr 27, 23:40 UTC | Apr 28, 10:35 UTC | 10h 55m |
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-5462 page for operator, model, and routing details .