sensors Mode-S transponder
780BE3
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1929 · BOEING 737-800
- Hex
- 780BE3
- Octal
- 36005743
- Decimal
- 7,867,363
- Country
- CN
- Tail
- B-1929
- Type
- B738
- Flights observed
- 64
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 780BE3 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 |
|---|---|---|---|
| CHH7328 | Hainan Airlines | 6 | 2026-06-22 |
| CHH7390 | Hainan Airlines | 5 | 2026-06-21 |
| CHH7698 | - | 4 | 2026-07-08 |
| CHH7119 | - | 3 | 2026-07-14 |
| CHH7777 | - | 2 | 2026-06-26 |
| CHH7697 | - | 2 | 2026-07-09 |
| CHH7648 | - | 2 | 2026-07-10 |
| CHH7555 | - | 2 | 2026-04-24 |
| CHH7386 | - | 2 | 2026-07-13 |
| CHH7308 | - | 2 | 2026-07-01 |
| CHH7305 | - | 2 | 2026-06-21 |
| CHH7185 | - | 2 | 2026-07-02 |
| CHH7897 | - | 1 | 2026-07-06 |
| CHH7851 | Hainan Airlines | 1 | 2026-05-15 |
| CHH7813 | - | 1 | 2026-07-04 |
| CHH7735 | Hainan Airlines | 1 | 2026-05-09 |
| CHH7654 | Hainan Airlines | 1 | 2026-04-21 |
| CHH7647 | - | 1 | 2026-07-09 |
| CHH7572 | Hainan Airlines | 1 | 2026-06-15 |
| CHH7564 | Hainan Airlines | 1 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CHH7119 | - | Jul 14, 02:40 UTC | Jul 14, 06:00 UTC | 3h 20m |
| 2026-07-13 | CHH7119 | - | Jul 13, 09:30 UTC | Jul 14, 06:00 UTC | 20h 30m |
| 2026-07-13 | CHH7386 | - | Jul 13, 05:15 UTC | Jul 14, 02:50 UTC | 21h 35m |
| 2026-07-12 | CHH7247 | - | Jul 12, 05:10 UTC | Jul 12, 05:30 UTC | 20m |
| 2026-07-11 | CHH7216 | - | Jul 11, 04:40 UTC | Jul 11, 09:35 UTC | 4h 55m |
| 2026-07-10 | CHH7648 | - | Jul 10, 11:35 UTC | Jul 11, 09:35 UTC | 22h 0m |
| 2026-07-10 | CHH7648 | - | Jul 10, 07:50 UTC | Jul 11, 04:40 UTC | 20h 50m |
| 2026-07-09 | CHH7647 | - | Jul 9, 08:55 UTC | Jul 10, 08:05 UTC | 23h 10m |
| 2026-07-09 | CHH7697 | - | Jul 9, 05:00 UTC | Jul 9, 09:10 UTC | 4h 10m |
| 2026-07-08 | CHH7698 | - | Jul 8, 09:10 UTC | Jul 9, 05:05 UTC | 19h 55m |
| 2026-07-08 | CHH7697 | - | Jul 8, 08:25 UTC | Jul 9, 05:05 UTC | 20h 40m |
| 2026-07-08 | CHH7698 | - | Jul 8, 05:15 UTC | Jul 8, 09:10 UTC | 3h 55m |
| 2026-07-06 | CHH7897 | - | Jul 6, 15:30 UTC | Jul 6, 15:45 UTC | 15m |
| 2026-07-05 | CHH7528 | - | Jul 5, 06:35 UTC | Jul 5, 13:50 UTC | 7h 15m |
| 2026-07-04 | CHH7813 | - | Jul 4, 13:15 UTC | Jul 5, 11:00 UTC | 21h 45m |
| 2026-07-04 | CHH6216 | - | Jul 4, 09:20 UTC | Jul 4, 09:30 UTC | 10m |
| 2026-07-04 | CHH6215 | - | Jul 4, 02:25 UTC | Jul 4, 02:45 UTC | 20m |
| 2026-07-02 | CHH7185 | - | Jul 2, 23:05 UTC | Jul 2, 23:25 UTC | 20m |
| 2026-07-01 | CHH7308 | - | Jul 1, 00:50 UTC | Jul 1, 23:20 UTC | 22h 30m |
| 2026-07-01 | CHH7308 | - | Jul 1, 00:10 UTC | Jul 1, 00:50 UTC | 40m |
| 2026-06-27 | CHH7079 | PEK → SYX | Jun 27, 00:44 UTC | Jun 27, 09:15 UTC | 8h 30m |
| 2026-06-26 | CHH7777 | - | Jun 26, 06:00 UTC | Jun 26, 11:34 UTC | 5h 35m |
| 2026-06-23 | CHH7564 | CGO → SYX | Jun 23, 00:19 UTC | Jun 23, 13:19 UTC | 13h 0m |
| 2026-06-22 | CHH7328 | CTU → SZX | Jun 22, 15:54 UTC | Jun 23, 13:19 UTC | 21h 25m |
| 2026-06-22 | CHH7328 | CTU → SZX | Jun 22, 11:00 UTC | Jun 23, 07:40 UTC | 20h 40m |
| 2026-06-22 | CHH7328 | CTU → SZX | Jun 22, 07:10 UTC | Jun 23, 04:19 UTC | 21h 10m |
| 2026-06-22 | CHH7328 | CTU → SZX | Jun 22, 01:00 UTC | Jun 23, 00:30 UTC | 23h 30m |
| 2026-06-22 | CHH7328 | CTU → SZX | Jun 22, 00:29 UTC | Jun 22, 16:34 UTC | 16h 5m |
| 2026-06-21 | CHH7305 | - | Jun 21, 15:15 UTC | Jun 22, 11:14 UTC | 20h 0m |
| 2026-06-21 | CHH7305 | - | Jun 21, 10:25 UTC | Jun 22, 07:19 UTC | 20h 55m |
| 2026-06-21 | CHH7390 | HGH → SZX | Jun 21, 06:50 UTC | Jun 22, 01:15 UTC | 18h 25m |
| 2026-06-21 | CHH7390 | HGH → SZX | Jun 21, 06:44 UTC | Jun 22, 01:15 UTC | 18h 30m |
| 2026-06-21 | CHH7390 | HGH → SZX | Jun 21, 00:40 UTC | Jun 21, 15:44 UTC | 15h 5m |
| 2026-06-20 | CHH7390 | HGH → SZX | Jun 20, 14:19 UTC | Jun 21, 10:34 UTC | 20h 15m |
| 2026-06-20 | CHH7390 | HGH → SZX | Jun 20, 09:34 UTC | Jun 21, 07:04 UTC | 21h 30m |
| 2026-06-20 | CHH7698 | - | Jun 20, 04:49 UTC | Jun 21, 00:49 UTC | 20h 0m |
| 2026-06-20 | CHH7698 | - | Jun 20, 04:44 UTC | Jun 20, 14:35 UTC | 9h 50m |
| 2026-06-15 | CHH7572 | CKG → HAK | Jun 15, 09:10 UTC | Jun 15, 09:20 UTC | 10m |
| 2026-06-04 | CHH7182 | PEK → HAK | Jun 4, 05:25 UTC | Jun 4, 08:15 UTC | 2h 50m |
| 2026-05-27 | CHH7235 | CAN → CGO | May 27, 03:24 UTC | May 27, 03:39 UTC | 15m |
| 2026-05-22 | CHH7070 | KHN → HAK | May 22, 15:40 UTC | May 22, 15:55 UTC | 15m |
| 2026-05-22 | CHH7006 | CAN → HAK | May 22, 01:55 UTC | May 22, 02:10 UTC | 15m |
| 2026-05-21 | CHH7386 | HGH → SYX | May 21, 05:30 UTC | May 21, 10:25 UTC | 4h 55m |
| 2026-05-15 | CHH7851 | URC → LHW | May 15, 23:05 UTC | May 15, 23:20 UTC | 15m |
| 2026-05-13 | CHH7045 | ZUH → TYN | May 13, 05:20 UTC | May 13, 05:35 UTC | 15m |
| 2026-05-12 | CHH7004 | CAN → HAK | May 12, 23:50 UTC | May 13, 00:05 UTC | 15m |
| 2026-05-10 | CHH7557 | SZX → CKG | May 10, 14:34 UTC | May 10, 14:45 UTC | 10m |
| 2026-05-09 | CHH7735 | SZX → CGO | May 9, 22:25 UTC | May 9, 22:34 UTC | 10m |
| 2026-04-29 | CHH7245 | PEK → URC | Apr 29, 06:15 UTC | Apr 29, 06:25 UTC | 10m |
| 2026-04-28 | CHH7185 | PEK → YIH | Apr 28, 23:10 UTC | Apr 28, 23:20 UTC | 10m |
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-1929 page for operator, model, and routing details .