sensors Mode-S transponder
7809B5
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5708 · BOEING 737-800
- Hex
- 7809B5
- Octal
- 36004665
- Decimal
- 7,866,805
- Country
- CN
- Tail
- B-5708
- Type
- B738
- Flights observed
- 56
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 7809B5 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 |
|---|---|---|---|
| CXA8704 | Xiamen Airlines | 7 | 2026-05-09 |
| CXA8703 | Xiamen Airlines | 5 | 2026-04-22 |
| CXA8714 | Xiamen Airlines | 2 | 2026-04-14 |
| CXA8678 | Xiamen Airlines | 2 | 2026-05-04 |
| CXA8383 | Xiamen Airlines | 2 | 2026-05-02 |
| CXA8378 | Xiamen Airlines | 2 | 2026-05-02 |
| CXA8377 | Xiamen Airlines | 2 | 2026-05-02 |
| CXA8343 | - | 2 | 2026-05-25 |
| CXA8331 | Xiamen Airlines | 2 | 2026-05-02 |
| CXA816 | Xiamen Airlines | 2 | 2026-05-15 |
| CXA815 | Xiamen Airlines | 2 | 2026-05-15 |
| CXA8871 | - | 1 | 2026-05-03 |
| CXA886 | Xiamen Airlines | 1 | 2026-05-01 |
| CXA885 | Xiamen Airlines | 1 | 2026-04-30 |
| CXA8828 | Xiamen Airlines | 1 | 2026-05-25 |
| CXA8740 | Xiamen Airlines | 1 | 2026-05-20 |
| CXA8739 | Xiamen Airlines | 1 | 2026-05-20 |
| CXA8720 | Xiamen Airlines | 1 | 2026-05-06 |
| CXA8719 | Xiamen Airlines | 1 | 2026-05-06 |
| CXA8713 | Xiamen Airlines | 1 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | CXA8317 | SHA → SZX | May 29, 09:45 UTC | May 29, 10:10 UTC | 25m |
| 2026-05-25 | CXA8828 | ZUH → XMN | May 25, 15:45 UTC | May 25, 16:20 UTC | 35m |
| 2026-05-25 | CXA8343 | - | May 25, 14:00 UTC | May 25, 14:20 UTC | 20m |
| 2026-05-24 | CXA818 | - | May 24, 10:15 UTC | May 24, 11:15 UTC | 1h 0m |
| 2026-05-24 | CXA817 | - | May 24, 07:05 UTC | May 24, 08:10 UTC | 1h 5m |
| 2026-05-22 | CXA8344 | SZX → HGH | May 22, 16:50 UTC | May 22, 17:00 UTC | 10m |
| 2026-05-22 | CXA8343 | - | May 22, 15:15 UTC | May 22, 15:35 UTC | 20m |
| 2026-05-20 | CXA8740 | CSX → HGH | May 20, 05:00 UTC | May 20, 05:25 UTC | 25m |
| 2026-05-20 | CXA8739 | HGH → CSX | May 20, 01:25 UTC | May 20, 02:55 UTC | 1h 30m |
| 2026-05-18 | CXA8409 | - | May 18, 00:25 UTC | May 18, 05:35 UTC | 5h 10m |
| 2026-05-15 | CXA816 | NRT → XMN | May 15, 06:25 UTC | May 15, 07:40 UTC | 1h 15m |
| 2026-05-15 | CXA815 | XMN → NRT | May 15, 03:25 UTC | May 15, 05:15 UTC | 1h 50m |
| 2026-05-11 | CXA816 | NRT → XMN | May 11, 06:15 UTC | May 11, 14:20 UTC | 8h 5m |
| 2026-05-11 | CXA815 | XMN → NRT | May 11, 03:10 UTC | May 11, 04:30 UTC | 1h 20m |
| 2026-05-09 | CXA8704 | SIN → HGH | May 9, 07:15 UTC | May 9, 10:40 UTC | 3h 25m |
| 2026-05-08 | CXA8704 | SIN → HGH | May 8, 07:29 UTC | May 9, 01:50 UTC | 18h 20m |
| 2026-05-07 | CXA8704 | SIN → HGH | May 7, 07:50 UTC | May 8, 01:55 UTC | 18h 5m |
| 2026-05-06 | CXA8720 | MFM → HGH | May 6, 10:30 UTC | May 7, 04:55 UTC | 18h 24m |
| 2026-05-06 | CXA8719 | HGH → MFM | May 6, 08:40 UTC | May 6, 08:55 UTC | 15m |
| 2026-05-05 | CXA8704 | SIN → HGH | May 5, 07:35 UTC | May 5, 10:40 UTC | 3h 5m |
| 2026-05-04 | CXA8678 | KUL → HGH | May 4, 12:50 UTC | May 5, 05:50 UTC | 17h 1m |
| 2026-05-04 | CXA8678 | KUL → HGH | May 4, 09:35 UTC | May 5, 05:50 UTC | 20h 16m |
| 2026-05-04 | CXA8677 | HGH → KUL | May 4, 03:09 UTC | May 4, 07:30 UTC | 4h 20m |
| 2026-05-03 | CXA8871 | - | May 3, 08:45 UTC | May 3, 08:55 UTC | 10m |
| 2026-05-03 | CXA8624 | - | May 3, 06:40 UTC | May 3, 07:00 UTC | 20m |
| 2026-05-03 | CXA8623 | - | May 3, 01:40 UTC | May 3, 01:50 UTC | 10m |
| 2026-05-02 | CXA8331 | SHA → SZX | May 2, 14:55 UTC | May 2, 15:15 UTC | 20m |
| 2026-05-02 | CXA8377 | SHA → SZX | May 2, 07:55 UTC | May 2, 08:15 UTC | 20m |
| 2026-05-02 | CXA8378 | SZX → SHA | May 2, 02:45 UTC | May 2, 02:55 UTC | 10m |
| 2026-05-02 | CXA8383 | KHN → SZX | May 2, 00:35 UTC | May 2, 00:55 UTC | 20m |
| 2026-05-01 | CXA886 | SIN → XMN | May 1, 01:15 UTC | May 1, 01:30 UTC | 15m |
| 2026-04-30 | CXA885 | XMN → SIN | Apr 30, 11:10 UTC | Apr 30, 14:25 UTC | 3h 15m |
| 2026-04-24 | CXA8688 | KUL → CKG | Apr 24, 06:15 UTC | Apr 24, 06:25 UTC | 10m |
| 2026-04-24 | CXA8687 | CKG → KUL | Apr 24, 04:20 UTC | Apr 24, 04:40 UTC | 20m |
| 2026-04-22 | CXA8704 | SIN → HGH | Apr 22, 07:20 UTC | Apr 22, 10:35 UTC | 3h 15m |
| 2026-04-22 | CXA8703 | HGH → SIN | Apr 22, 05:05 UTC | Apr 22, 05:25 UTC | 20m |
| 2026-04-21 | CXA8703 | HGH → SIN | Apr 21, 10:25 UTC | Apr 22, 04:05 UTC | 17h 40m |
| 2026-04-21 | CXA8704 | SIN → HGH | Apr 21, 07:20 UTC | Apr 22, 04:05 UTC | 20h 45m |
| 2026-04-21 | CXA8703 | HGH → SIN | Apr 21, 02:00 UTC | Apr 21, 05:05 UTC | 3h 5m |
| 2026-04-20 | CXA8703 | HGH → SIN | Apr 20, 07:20 UTC | Apr 21, 05:05 UTC | 21h 45m |
| 2026-04-20 | CXA810 | NRT → FOC | Apr 20, 06:50 UTC | Apr 21, 05:05 UTC | 22h 15m |
| 2026-04-20 | CXA809 | FOC → NRT | Apr 20, 03:35 UTC | Apr 20, 05:10 UTC | 1h 35m |
| 2026-04-18 | CXA858 | - | Apr 18, 19:20 UTC | Apr 18, 22:20 UTC | 3h 0m |
| 2026-04-18 | CXA857 | - | Apr 18, 16:25 UTC | Apr 18, 17:55 UTC | 1h 30m |
| 2026-04-17 | CXA8331 | SHA → SZX | Apr 17, 18:55 UTC | Apr 17, 19:05 UTC | 10m |
| 2026-04-17 | CXA8332 | SZX → SHA | Apr 17, 12:50 UTC | Apr 17, 13:00 UTC | 10m |
| 2026-04-17 | CXA8377 | SHA → SZX | Apr 17, 10:05 UTC | Apr 17, 10:25 UTC | 20m |
| 2026-04-17 | CXA8378 | SZX → SHA | Apr 17, 02:55 UTC | Apr 17, 03:05 UTC | 10m |
| 2026-04-17 | CXA8383 | KHN → SZX | Apr 17, 00:40 UTC | Apr 17, 01:04 UTC | 25m |
| 2026-04-15 | CXA8704 | SIN → HGH | Apr 15, 07:01 UTC | Apr 15, 07:20 UTC | 20m |
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-5708 page for operator, model, and routing details .