sensors Mode-S transponder
7805E0
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5499 · BOEING 737-800
- Hex
- 7805E0
- Octal
- 36002740
- Decimal
- 7,865,824
- Country
- CN
- Tail
- B-5499
- Type
- B738
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 7805E0 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 |
|---|---|---|---|
| CXA8212 | - | 11 | 2026-06-29 |
| CXA8703 | Xiamen Airlines | 4 | 2026-04-27 |
| CXA857 | - | 3 | 2026-07-05 |
| CXA880 | Xiamen Airlines | 2 | 2026-05-12 |
| CXA872 | - | 2 | 2026-07-07 |
| CXA871 | - | 2 | 2026-07-07 |
| CXA8704 | Xiamen Airlines | 2 | 2026-04-28 |
| CXA8702 | Xiamen Airlines | 2 | 2026-04-29 |
| CXA8682 | Xiamen Airlines | 2 | 2026-06-05 |
| CXA8681 | Xiamen Airlines | 2 | 2026-06-05 |
| CXA864 | Xiamen Airlines | 2 | 2026-04-30 |
| CXA858 | - | 2 | 2026-07-05 |
| CXA8871 | - | 1 | 2026-04-13 |
| CXA886 | Xiamen Airlines | 1 | 2026-04-23 |
| CXA885 | Xiamen Airlines | 1 | 2026-04-22 |
| CXA8827 | - | 1 | 2026-07-02 |
| CXA879 | Xiamen Airlines | 1 | 2026-04-18 |
| CXA8726 | - | 1 | 2026-07-10 |
| CXA8725 | - | 1 | 2026-07-10 |
| CXA8719 | Xiamen Airlines | 1 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | CXA8726 | - | Jul 10, 05:15 UTC | Jul 10, 05:50 UTC | 35m |
| 2026-07-10 | CXA8725 | - | Jul 10, 00:55 UTC | Jul 10, 02:40 UTC | 1h 45m |
| 2026-07-07 | CXA872 | - | Jul 7, 04:45 UTC | Jul 7, 05:25 UTC | 40m |
| 2026-07-07 | CXA871 | - | Jul 7, 02:30 UTC | Jul 7, 03:15 UTC | 45m |
| 2026-07-06 | CXA820 | - | Jul 6, 14:10 UTC | Jul 6, 15:50 UTC | 1h 40m |
| 2026-07-06 | CXA819 | - | Jul 6, 10:35 UTC | Jul 6, 12:30 UTC | 1h 55m |
| 2026-07-05 | CXA858 | - | Jul 5, 18:35 UTC | Jul 5, 19:05 UTC | 30m |
| 2026-07-05 | CXA857 | - | Jul 5, 14:05 UTC | Jul 5, 17:05 UTC | 3h 0m |
| 2026-07-04 | CXA8696 | - | Jul 4, 08:15 UTC | Jul 4, 13:20 UTC | 5h 5m |
| 2026-07-04 | CXA8410 | - | Jul 4, 05:00 UTC | Jul 4, 05:10 UTC | 10m |
| 2026-07-03 | CXA818 | - | Jul 3, 11:15 UTC | Jul 3, 12:25 UTC | 1h 10m |
| 2026-07-03 | CXA817 | - | Jul 3, 08:20 UTC | Jul 3, 09:25 UTC | 1h 5m |
| 2026-07-02 | CXA8344 | - | Jul 2, 15:40 UTC | Jul 2, 15:50 UTC | 10m |
| 2026-07-02 | CXA8827 | - | Jul 2, 13:50 UTC | Jul 2, 14:15 UTC | 25m |
| 2026-07-02 | CXA824 | - | Jul 2, 00:10 UTC | Jul 2, 00:30 UTC | 20m |
| 2026-07-01 | CXA823 | - | Jul 1, 09:25 UTC | Jul 1, 15:55 UTC | 6h 30m |
| 2026-06-29 | CXA8212 | - | Jun 29, 07:15 UTC | Jun 29, 07:34 UTC | 20m |
| 2026-06-28 | CXA8212 | - | Jun 28, 10:04 UTC | Jun 29, 07:34 UTC | 21h 30m |
| 2026-06-27 | CXA8212 | - | Jun 27, 07:19 UTC | Jun 27, 07:30 UTC | 10m |
| 2026-06-26 | CXA8212 | - | Jun 26, 07:20 UTC | Jun 26, 07:35 UTC | 15m |
| 2026-06-20 | CXA8212 | - | Jun 20, 07:09 UTC | Jun 20, 07:24 UTC | 15m |
| 2026-06-13 | CXA8211 | PKX → JGN | Jun 13, 01:30 UTC | Jun 13, 01:40 UTC | 10m |
| 2026-06-12 | CXA8212 | JGN → PKX | Jun 12, 07:45 UTC | Jun 12, 08:00 UTC | 15m |
| 2026-06-11 | CXA8212 | JGN → PKX | Jun 11, 07:15 UTC | Jun 11, 07:30 UTC | 15m |
| 2026-06-10 | CXA8212 | JGN → PKX | Jun 10, 07:30 UTC | Jun 10, 07:40 UTC | 10m |
| 2026-06-09 | CXA872 | ICN → XMN | Jun 9, 04:35 UTC | Jun 9, 05:05 UTC | 30m |
| 2026-06-09 | CXA871 | - | Jun 9, 00:50 UTC | Jun 9, 02:55 UTC | 2h 5m |
| 2026-06-06 | CXA8692 | - | Jun 6, 06:50 UTC | Jun 6, 07:10 UTC | 20m |
| 2026-06-06 | CXA8691 | - | Jun 6, 04:45 UTC | Jun 6, 04:50 UTC | 5m |
| 2026-06-05 | CXA8682 | MFM → XMN | Jun 5, 08:15 UTC | Jun 5, 08:25 UTC | 10m |
| 2026-06-05 | CXA8681 | XMN → MFM | Jun 5, 06:10 UTC | Jun 5, 07:05 UTC | 55m |
| 2026-05-12 | CXA880 | TPE → FOC | May 12, 03:40 UTC | May 12, 04:10 UTC | 30m |
| 2026-05-09 | CXA8212 | JGN → PKX | May 9, 07:10 UTC | May 9, 07:25 UTC | 15m |
| 2026-05-08 | CXA8212 | JGN → PKX | May 8, 07:34 UTC | May 8, 07:50 UTC | 15m |
| 2026-05-07 | CXA8212 | JGN → PKX | May 7, 07:50 UTC | May 7, 08:05 UTC | 15m |
| 2026-05-03 | CXA8318 | SZX → SHA | May 3, 13:35 UTC | May 3, 13:50 UTC | 15m |
| 2026-04-30 | CXA864 | SIN → HGH | Apr 30, 15:35 UTC | Apr 30, 15:55 UTC | 20m |
| 2026-04-30 | CXA864 | SIN → HGH | Apr 30, 13:40 UTC | Apr 30, 13:50 UTC | 10m |
| 2026-04-30 | CXA863 | HGH → SIN | Apr 30, 09:20 UTC | Apr 30, 12:10 UTC | 2h 50m |
| 2026-04-29 | CXA8702 | SGN → HGH | Apr 29, 03:10 UTC | Apr 29, 09:00 UTC | 5h 51m |
| 2026-04-28 | CXA8702 | SGN → HGH | Apr 28, 10:40 UTC | Apr 29, 09:00 UTC | 22h 20m |
| 2026-04-28 | CXA8704 | SIN → HGH | Apr 28, 07:25 UTC | Apr 29, 03:15 UTC | 19h 50m |
| 2026-04-27 | CXA8703 | HGH → SIN | Apr 27, 10:30 UTC | Apr 28, 05:50 UTC | 19h 20m |
| 2026-04-27 | CXA8703 | HGH → SIN | Apr 27, 07:25 UTC | Apr 28, 05:50 UTC | 22h 25m |
| 2026-04-26 | CXA8703 | HGH → SIN | Apr 26, 10:35 UTC | Apr 27, 05:40 UTC | 19h 5m |
| 2026-04-26 | CXA8719 | HGH → MFM | Apr 26, 08:40 UTC | Apr 26, 08:50 UTC | 10m |
| 2026-04-25 | CXA8704 | SIN → HGH | Apr 25, 07:20 UTC | Apr 25, 10:25 UTC | 3h 5m |
| 2026-04-25 | CXA8703 | HGH → SIN | Apr 25, 04:00 UTC | Apr 25, 05:30 UTC | 1h 30m |
| 2026-04-23 | CXA886 | SIN → XMN | Apr 23, 01:25 UTC | Apr 23, 02:35 UTC | 1h 10m |
| 2026-04-22 | CXA885 | XMN → SIN | Apr 22, 11:00 UTC | Apr 22, 14:05 UTC | 3h 5m |
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-5499 page for operator, model, and routing details .