sensors Mode-S transponder
780BE1
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1927 · BOEING 737-800
- Hex
- 780BE1
- Octal
- 36005741
- Decimal
- 7,867,361
- Country
- CN
- Tail
- B-1927
- Type
- B738
- Flights observed
- 63
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 780BE1 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 |
|---|---|---|---|
| CHH7851 | Hainan Airlines | 3 | 2026-05-19 |
| CHH7648 | Hainan Airlines | 2 | 2026-05-01 |
| CHH7571 | Hainan Airlines | 2 | 2026-06-15 |
| CHH7370 | - | 2 | 2026-06-21 |
| CHH7338 | Hainan Airlines | 2 | 2026-05-25 |
| CHH7271 | Hainan Airlines | 2 | 2026-06-17 |
| CHH7220 | Hainan Airlines | 2 | 2026-05-02 |
| CHH7209 | - | 2 | 2026-06-28 |
| CHH7027 | Hainan Airlines | 2 | 2026-05-08 |
| CHH7988 | Hainan Airlines | 1 | 2026-04-15 |
| CHH7987 | Hainan Airlines | 1 | 2026-04-15 |
| CHH7872 | Hainan Airlines | 1 | 2026-05-25 |
| CHH7871 | Hainan Airlines | 1 | 2026-05-25 |
| CHH7834 | Hainan Airlines | 1 | 2026-05-28 |
| CHH7833 | Hainan Airlines | 1 | 2026-05-28 |
| CHH7807 | - | 1 | 2026-06-30 |
| CHH7805 | - | 1 | 2026-07-12 |
| CHH7776 | Hainan Airlines | 1 | 2026-07-17 |
| CHH7775 | - | 1 | 2026-07-17 |
| CHH7746 | - | 1 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | CHH7736 | - | Jul 18, 04:10 UTC | Jul 18, 04:20 UTC | 10m |
| 2026-07-17 | CHH7735 | - | Jul 17, 22:35 UTC | Jul 17, 22:49 UTC | 15m |
| 2026-07-17 | CHH7776 | TYN → SZX | Jul 17, 16:44 UTC | Jul 17, 17:09 UTC | 25m |
| 2026-07-17 | CHH7775 | - | Jul 17, 05:45 UTC | Jul 17, 05:55 UTC | 10m |
| 2026-07-16 | CHH7475 | - | Jul 16, 08:05 UTC | Jul 16, 08:15 UTC | 10m |
| 2026-07-16 | CHH7176 | - | Jul 16, 06:05 UTC | Jul 16, 06:25 UTC | 20m |
| 2026-07-16 | CHH7175 | - | Jul 16, 00:55 UTC | Jul 16, 01:05 UTC | 10m |
| 2026-07-13 | CHH7004 | - | Jul 13, 00:30 UTC | Jul 13, 00:40 UTC | 10m |
| 2026-07-12 | CHH7805 | - | Jul 12, 02:45 UTC | Jul 12, 03:10 UTC | 25m |
| 2026-07-08 | CHH7638 | - | Jul 8, 07:55 UTC | Jul 8, 08:05 UTC | 10m |
| 2026-07-01 | CHH7216 | - | Jul 1, 04:30 UTC | Jul 1, 09:45 UTC | 5h 15m |
| 2026-07-01 | CHH7006 | - | Jul 1, 01:25 UTC | Jul 1, 01:40 UTC | 15m |
| 2026-06-30 | CHH7807 | - | Jun 30, 04:35 UTC | Jun 30, 05:00 UTC | 25m |
| 2026-06-28 | CHH7209 | - | Jun 28, 15:20 UTC | Jun 29, 09:50 UTC | 18h 30m |
| 2026-06-28 | CHH7327 | - | Jun 28, 09:50 UTC | Jun 29, 04:45 UTC | 18h 55m |
| 2026-06-27 | CHH7306 | - | Jun 27, 15:45 UTC | Jun 28, 07:44 UTC | 16h 0m |
| 2026-06-27 | CHH7312 | - | Jun 27, 03:25 UTC | Jun 28, 00:20 UTC | 20h 55m |
| 2026-06-26 | CHH7311 | - | Jun 26, 15:49 UTC | Jun 27, 03:34 UTC | 11h 45m |
| 2026-06-24 | CHH7209 | - | Jun 24, 15:49 UTC | Jun 25, 05:35 UTC | 13h 45m |
| 2026-06-24 | CHH7741 | - | Jun 24, 04:05 UTC | Jun 24, 04:20 UTC | 15m |
| 2026-06-24 | CHH7742 | - | Jun 24, 02:30 UTC | Jun 24, 02:45 UTC | 15m |
| 2026-06-21 | CHH7654 | JUH → TYN | Jun 21, 15:15 UTC | Jun 21, 15:40 UTC | 25m |
| 2026-06-21 | CHH7370 | - | Jun 21, 00:29 UTC | Jun 21, 12:24 UTC | 11h 55m |
| 2026-06-17 | CHH7271 | CAN → KWE | Jun 17, 04:25 UTC | Jun 17, 14:40 UTC | 10h 15m |
| 2026-06-15 | CHH7571 | HAK → CKG | Jun 15, 12:05 UTC | Jun 16, 01:50 UTC | 13h 45m |
| 2026-06-14 | CHH7571 | HAK → CKG | Jun 14, 23:44 UTC | Jun 15, 12:19 UTC | 12h 35m |
| 2026-06-13 | CHH7271 | CAN → KWE | Jun 13, 04:25 UTC | Jun 13, 04:40 UTC | 15m |
| 2026-06-06 | CHH7101 | CKG → SHE | Jun 6, 09:34 UTC | Jun 6, 09:50 UTC | 15m |
| 2026-05-29 | CHH7517 | HAK → CSX | May 29, 09:00 UTC | May 29, 09:15 UTC | 15m |
| 2026-05-28 | CHH7834 | TSN → URC | May 28, 11:15 UTC | May 28, 11:30 UTC | 15m |
| 2026-05-28 | CHH7833 | URC → TSN | May 28, 08:55 UTC | May 28, 09:15 UTC | 20m |
| 2026-05-27 | CHH7182 | PEK → HAK | May 27, 05:49 UTC | May 27, 12:05 UTC | 6h 16m |
| 2026-05-25 | CHH7337 | PEK → XIY | May 25, 14:05 UTC | May 25, 14:20 UTC | 15m |
| 2026-05-25 | CHH7338 | XIY → PEK | May 25, 11:30 UTC | May 25, 12:05 UTC | 35m |
| 2026-05-25 | CHH7872 | SZX → XIY | May 25, 05:05 UTC | May 25, 05:15 UTC | 10m |
| 2026-05-25 | CHH7871 | XIY → SZX | May 25, 03:25 UTC | May 25, 03:35 UTC | 10m |
| 2026-05-19 | CHH7851 | URC → LHW | May 19, 23:00 UTC | May 19, 23:10 UTC | 10m |
| 2026-05-09 | CHH7851 | URC → LHW | May 9, 22:55 UTC | May 9, 23:05 UTC | 10m |
| 2026-05-09 | CHH7746 | - | May 9, 08:55 UTC | May 9, 09:20 UTC | 25m |
| 2026-05-09 | CHH7745 | - | May 9, 02:35 UTC | May 9, 02:45 UTC | 10m |
| 2026-05-08 | CHH7027 | HAK → SZX | May 8, 14:40 UTC | May 8, 15:00 UTC | 20m |
| 2026-05-06 | CHH7851 | URC → LHW | May 6, 23:25 UTC | May 6, 23:35 UTC | 10m |
| 2026-05-06 | CHH7027 | HAK → SZX | May 6, 14:10 UTC | May 6, 14:25 UTC | 15m |
| 2026-05-03 | CHH7688 | NGB → HAK | May 3, 14:25 UTC | May 4, 10:10 UTC | 19h 45m |
| 2026-05-03 | CHH7687 | NGB → TAO | May 3, 09:15 UTC | May 3, 23:50 UTC | 14h 35m |
| 2026-05-02 | CHH7219 | HAK → PVG | May 2, 14:20 UTC | May 3, 09:25 UTC | 19h 4m |
| 2026-05-02 | CHH7220 | PVG → HAK | May 2, 13:05 UTC | May 3, 09:25 UTC | 20h 19m |
| 2026-05-02 | CHH7220 | PVG → HAK | May 2, 08:55 UTC | May 2, 14:25 UTC | 5h 30m |
| 2026-05-01 | CHH7648 | SHE → HAK | May 1, 11:20 UTC | May 2, 09:05 UTC | 21h 45m |
| 2026-05-01 | CHH7648 | SHE → HAK | May 1, 07:50 UTC | May 1, 11:45 UTC | 3h 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-1927 page for operator, model, and routing details .