sensors Mode-S transponder
7809B7
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5706 · BOEING 737-800
- Hex
- 7809B7
- Octal
- 36004667
- Decimal
- 7,866,807
- Country
- CN
- Tail
- B-5706
- Type
- B738
- Flights observed
- 57
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 7809B7 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 |
|---|---|---|---|
| CXA8687 | Xiamen Airlines | 4 | 2026-05-29 |
| CXA8688 | Xiamen Airlines | 3 | 2026-05-30 |
| CXA8624 | - | 3 | 2026-04-25 |
| CXA8872 | - | 2 | 2026-04-25 |
| CXA8871 | - | 2 | 2026-04-24 |
| CXA8701 | Xiamen Airlines | 2 | 2026-04-26 |
| CXA8669 | - | 2 | 2026-05-29 |
| CXA8385 | - | 2 | 2026-05-13 |
| CXA8346 | Xiamen Airlines | 2 | 2026-04-25 |
| CXA8345 | Xiamen Airlines | 2 | 2026-04-26 |
| CXA817 | - | 2 | 2026-05-10 |
| CXA8060 | Xiamen Airlines | 2 | 2026-05-24 |
| CXA8882 | Xiamen Airlines | 1 | 2026-05-17 |
| CXA8881 | Xiamen Airlines | 1 | 2026-05-17 |
| CXA884 | Xiamen Airlines | 1 | 2026-05-21 |
| CXA883 | Xiamen Airlines | 1 | 2026-05-21 |
| CXA882 | - | 1 | 2026-04-21 |
| CXA8812 | Xiamen Airlines | 1 | 2026-04-17 |
| CXA881 | - | 1 | 2026-04-21 |
| CXA8791 | Xiamen Airlines | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | CXA8688 | KUL → CKG | May 30, 07:05 UTC | May 30, 08:55 UTC | 1h 50m |
| 2026-05-30 | CXA8688 | KUL → CKG | May 30, 05:55 UTC | May 30, 06:10 UTC | 15m |
| 2026-05-29 | CXA8687 | CKG → KUL | May 29, 09:50 UTC | May 30, 04:15 UTC | 18h 25m |
| 2026-05-29 | CXA8687 | CKG → KUL | May 29, 09:35 UTC | May 30, 04:15 UTC | 18h 40m |
| 2026-05-29 | CXA8669 | - | May 29, 04:00 UTC | May 30, 01:45 UTC | 21h 45m |
| 2026-05-28 | CXA8669 | - | May 28, 14:10 UTC | May 29, 13:45 UTC | 23h 35m |
| 2026-05-28 | CXA8413 | XMN → CKG | May 28, 06:35 UTC | May 29, 04:05 UTC | 21h 30m |
| 2026-05-27 | CXA816 | NRT → XMN | May 27, 06:04 UTC | May 27, 07:35 UTC | 1h 30m |
| 2026-05-27 | CXA815 | XMN → NRT | May 27, 01:24 UTC | May 27, 04:34 UTC | 3h 10m |
| 2026-05-26 | CXA858 | - | May 26, 18:59 UTC | May 26, 22:29 UTC | 3h 30m |
| 2026-05-26 | CXA857 | - | May 26, 06:04 UTC | May 26, 17:39 UTC | 11h 35m |
| 2026-05-24 | CXA8060 | SHE → HGH | May 24, 12:10 UTC | May 24, 12:45 UTC | 35m |
| 2026-05-21 | CXA884 | TSA → FOC | May 21, 12:40 UTC | May 21, 13:05 UTC | 25m |
| 2026-05-21 | CXA883 | FOC → TSA | May 21, 11:00 UTC | May 21, 11:30 UTC | 30m |
| 2026-05-18 | CXA8060 | SHE → HGH | May 18, 10:45 UTC | May 18, 11:25 UTC | 40m |
| 2026-05-17 | CXA8882 | ZUH → SHA | May 17, 11:35 UTC | May 17, 11:45 UTC | 10m |
| 2026-05-17 | CXA8881 | SHA → ZUH | May 17, 09:20 UTC | May 17, 09:45 UTC | 25m |
| 2026-05-17 | CXA8372 | SZX → SHA | May 17, 04:20 UTC | May 17, 04:35 UTC | 15m |
| 2026-05-17 | CXA8371 | SHA → SZX | May 17, 02:20 UTC | May 17, 02:40 UTC | 20m |
| 2026-05-13 | CXA8513 | - | May 13, 05:35 UTC | May 13, 05:45 UTC | 10m |
| 2026-05-13 | CXA8385 | - | May 13, 01:05 UTC | May 13, 01:15 UTC | 10m |
| 2026-05-11 | CXA8020 | - | May 11, 06:50 UTC | May 12, 03:55 UTC | 21h 6m |
| 2026-05-10 | CXA818 | - | May 10, 10:05 UTC | May 11, 04:35 UTC | 18h 30m |
| 2026-05-10 | CXA817 | - | May 10, 07:34 UTC | May 10, 08:10 UTC | 35m |
| 2026-05-10 | CXA817 | - | May 10, 06:15 UTC | May 10, 06:50 UTC | 35m |
| 2026-05-06 | CXA8397 | - | May 6, 00:46 UTC | May 6, 04:30 UTC | 3h 45m |
| 2026-05-05 | CXA8688 | KUL → CKG | May 5, 06:00 UTC | May 5, 06:10 UTC | 10m |
| 2026-05-05 | CXA8687 | CKG → KUL | May 5, 04:10 UTC | May 5, 04:35 UTC | 25m |
| 2026-05-02 | CXA8687 | CKG → KUL | May 2, 04:05 UTC | May 2, 04:35 UTC | 30m |
| 2026-04-28 | CXA8720 | MFM → HGH | Apr 28, 10:30 UTC | Apr 28, 11:00 UTC | 30m |
| 2026-04-28 | CXA8719 | HGH → MFM | Apr 28, 08:35 UTC | Apr 28, 09:20 UTC | 45m |
| 2026-04-26 | CXA8345 | HGH → SZX | Apr 26, 14:05 UTC | Apr 26, 14:25 UTC | 20m |
| 2026-04-26 | CXA8702 | SGN → HGH | Apr 26, 08:25 UTC | Apr 26, 09:05 UTC | 40m |
| 2026-04-26 | CXA8701 | HGH → SGN | Apr 26, 04:55 UTC | Apr 26, 05:10 UTC | 15m |
| 2026-04-26 | CXA8701 | HGH → SGN | Apr 26, 02:55 UTC | Apr 26, 03:05 UTC | 10m |
| 2026-04-25 | CXA8346 | SZX → HGH | Apr 25, 14:50 UTC | Apr 25, 15:00 UTC | 10m |
| 2026-04-25 | CXA8872 | - | Apr 25, 12:45 UTC | Apr 25, 12:55 UTC | 10m |
| 2026-04-25 | CXA8624 | - | Apr 25, 06:30 UTC | Apr 25, 06:40 UTC | 10m |
| 2026-04-24 | CXA8872 | - | Apr 24, 15:55 UTC | Apr 24, 16:05 UTC | 10m |
| 2026-04-24 | CXA8871 | - | Apr 24, 11:15 UTC | Apr 24, 11:25 UTC | 10m |
| 2026-04-24 | CXA8624 | - | Apr 24, 09:25 UTC | Apr 24, 09:35 UTC | 10m |
| 2026-04-24 | CXA8623 | - | Apr 24, 01:30 UTC | Apr 24, 01:40 UTC | 10m |
| 2026-04-23 | CXA8389 | CKG → SZX | Apr 23, 16:45 UTC | Apr 23, 16:55 UTC | 10m |
| 2026-04-23 | CXA8385 | - | Apr 23, 01:25 UTC | Apr 23, 02:00 UTC | 35m |
| 2026-04-21 | CXA882 | - | Apr 21, 11:45 UTC | Apr 21, 12:15 UTC | 30m |
| 2026-04-21 | CXA881 | - | Apr 21, 09:45 UTC | Apr 21, 10:20 UTC | 35m |
| 2026-04-20 | CXA848 | KUL → XMN | Apr 20, 07:00 UTC | Apr 20, 08:35 UTC | 1h 35m |
| 2026-04-19 | CXA847 | XMN → KUL | Apr 19, 12:30 UTC | Apr 20, 05:30 UTC | 17h 0m |
| 2026-04-19 | CXA8665 | XMN → KHH | Apr 19, 11:05 UTC | Apr 19, 11:25 UTC | 20m |
| 2026-04-17 | CXA8791 | FOC → HAK | Apr 17, 12:50 UTC | Apr 17, 13:15 UTC | 25m |
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-5706 page for operator, model, and routing details .