sensors Mode-S transponder
7808D3
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5653 · BOEING 737-800
- Hex
- 7808D3
- Octal
- 36004323
- Decimal
- 7,866,579
- Country
- CN
- Tail
- B-5653
- Type
- B738
- Flights observed
- 69
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 7808D3 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 |
|---|---|---|---|
| CXA8703 | - | 8 | 2026-07-04 |
| CXA8719 | - | 6 | 2026-07-07 |
| CXA8704 | Xiamen Airlines | 6 | 2026-06-09 |
| CXA8720 | - | 4 | 2026-07-07 |
| CXA8023 | Xiamen Airlines | 4 | 2026-05-07 |
| CXA8816 | Xiamen Airlines | 2 | 2026-05-24 |
| CXA8726 | - | 2 | 2026-07-12 |
| CXA8725 | - | 2 | 2026-07-12 |
| CXA8678 | - | 2 | 2026-07-06 |
| CXA8677 | - | 2 | 2026-07-06 |
| CXA8658 | Xiamen Airlines | 2 | 2026-05-27 |
| CXA8657 | Xiamen Airlines | 2 | 2026-05-27 |
| CXA8650 | Xiamen Airlines | 2 | 2026-04-25 |
| CXA886 | Xiamen Airlines | 1 | 2026-04-28 |
| CXA885 | Xiamen Airlines | 1 | 2026-04-27 |
| CXA884 | - | 1 | 2026-04-13 |
| CXA883 | Xiamen Airlines | 1 | 2026-04-13 |
| CXA8828 | - | 1 | 2026-07-02 |
| CXA8825 | Xiamen Airlines | 1 | 2026-04-23 |
| CXA8792 | Xiamen Airlines | 1 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | CXA8726 | - | Jul 12, 04:40 UTC | Jul 12, 05:10 UTC | 30m |
| 2026-07-12 | CXA8725 | - | Jul 12, 02:05 UTC | Jul 12, 02:40 UTC | 35m |
| 2026-07-09 | CXA8384 | - | Jul 9, 00:00 UTC | Jul 9, 00:10 UTC | 10m |
| 2026-07-08 | CXA8345 | - | Jul 8, 15:55 UTC | Jul 8, 16:15 UTC | 20m |
| 2026-07-07 | CXA8720 | - | Jul 7, 13:00 UTC | Jul 7, 13:45 UTC | 45m |
| 2026-07-07 | CXA8719 | - | Jul 7, 10:15 UTC | Jul 7, 10:25 UTC | 10m |
| 2026-07-07 | CXA8719 | - | Jul 7, 09:15 UTC | Jul 7, 09:25 UTC | 10m |
| 2026-07-06 | CXA8678 | - | Jul 6, 11:10 UTC | Jul 7, 09:25 UTC | 22h 15m |
| 2026-07-06 | CXA8678 | - | Jul 6, 07:50 UTC | Jul 6, 12:00 UTC | 4h 10m |
| 2026-07-06 | CXA8677 | - | Jul 6, 02:40 UTC | Jul 6, 06:25 UTC | 3h 45m |
| 2026-07-05 | CXA8677 | - | Jul 5, 07:00 UTC | Jul 6, 06:25 UTC | 23h 25m |
| 2026-07-04 | CXA8703 | - | Jul 4, 12:40 UTC | Jul 5, 04:45 UTC | 16h 5m |
| 2026-07-04 | CXA8719 | - | Jul 4, 10:55 UTC | Jul 4, 11:05 UTC | 10m |
| 2026-07-02 | CXA8828 | - | Jul 2, 15:20 UTC | Jul 2, 15:30 UTC | 10m |
| 2026-07-02 | CXA8343 | - | Jul 2, 13:25 UTC | Jul 2, 13:45 UTC | 20m |
| 2026-07-02 | CXA8726 | - | Jul 2, 04:55 UTC | Jul 2, 05:25 UTC | 30m |
| 2026-07-02 | CXA8725 | - | Jul 2, 01:55 UTC | Jul 2, 03:15 UTC | 1h 20m |
| 2026-06-29 | CXA8375 | - | Jun 29, 23:49 UTC | Jun 30, 03:05 UTC | 3h 15m |
| 2026-06-10 | CXA834 | BKK → XMN | Jun 10, 11:00 UTC | Jun 10, 13:30 UTC | 2h 30m |
| 2026-06-10 | CXA833 | XMN → BKK | Jun 10, 07:00 UTC | Jun 10, 09:35 UTC | 2h 35m |
| 2026-06-09 | CXA8704 | SIN → HGH | Jun 9, 07:05 UTC | Jun 9, 11:05 UTC | 4h 0m |
| 2026-06-09 | CXA8703 | HGH → SIN | Jun 9, 05:00 UTC | Jun 9, 05:10 UTC | 10m |
| 2026-06-08 | CXA8704 | SIN → HGH | Jun 8, 07:05 UTC | Jun 9, 02:15 UTC | 19h 10m |
| 2026-06-07 | CXA8703 | HGH → SIN | Jun 7, 10:55 UTC | Jun 8, 04:55 UTC | 18h 0m |
| 2026-06-07 | CXA8703 | HGH → SIN | Jun 7, 10:10 UTC | Jun 8, 04:55 UTC | 18h 45m |
| 2026-06-07 | CXA8704 | SIN → HGH | Jun 7, 07:00 UTC | Jun 8, 04:55 UTC | 21h 55m |
| 2026-06-07 | CXA8703 | HGH → SIN | Jun 7, 01:45 UTC | Jun 7, 04:55 UTC | 3h 10m |
| 2026-06-06 | CXA8704 | SIN → HGH | Jun 6, 06:55 UTC | Jun 7, 04:55 UTC | 22h 0m |
| 2026-06-05 | CXA8703 | HGH → SIN | Jun 5, 10:50 UTC | Jun 6, 04:50 UTC | 18h 0m |
| 2026-06-05 | CXA8704 | SIN → HGH | Jun 5, 07:10 UTC | Jun 6, 04:50 UTC | 21h 40m |
| 2026-06-04 | CXA8703 | HGH → SIN | Jun 4, 10:50 UTC | Jun 5, 04:55 UTC | 18h 5m |
| 2026-06-04 | CXA8703 | HGH → SIN | Jun 4, 10:15 UTC | Jun 5, 04:55 UTC | 18h 40m |
| 2026-06-04 | CXA8704 | SIN → HGH | Jun 4, 07:05 UTC | Jun 5, 04:55 UTC | 21h 50m |
| 2026-06-01 | CXA8720 | MFM → HGH | Jun 1, 10:25 UTC | Jun 1, 10:40 UTC | 15m |
| 2026-06-01 | CXA8719 | HGH → MFM | Jun 1, 08:45 UTC | Jun 1, 09:10 UTC | 25m |
| 2026-05-29 | CXA8792 | HAK → FOC | May 29, 15:40 UTC | May 29, 15:50 UTC | 10m |
| 2026-05-29 | CXA8791 | FOC → HAK | May 29, 11:35 UTC | May 29, 12:20 UTC | 45m |
| 2026-05-27 | CXA8658 | MNL → HGH | May 27, 13:30 UTC | May 27, 15:25 UTC | 1h 55m |
| 2026-05-27 | CXA8657 | HGH → MNL | May 27, 11:35 UTC | May 27, 12:15 UTC | 40m |
| 2026-05-24 | CXA8816 | SYX → XMN | May 24, 13:05 UTC | May 25, 06:30 UTC | 17h 25m |
| 2026-05-24 | CXA8816 | SYX → XMN | May 24, 04:20 UTC | May 24, 13:50 UTC | 9h 30m |
| 2026-05-22 | CXA8720 | MFM → HGH | May 22, 11:10 UTC | May 22, 11:25 UTC | 15m |
| 2026-05-22 | CXA8719 | HGH → MFM | May 22, 09:20 UTC | May 22, 09:35 UTC | 15m |
| 2026-05-21 | CXA8720 | MFM → HGH | May 21, 10:40 UTC | May 21, 10:55 UTC | 15m |
| 2026-05-21 | CXA8719 | HGH → MFM | May 21, 08:40 UTC | May 21, 08:50 UTC | 10m |
| 2026-05-20 | CXA8658 | MNL → HGH | May 20, 13:10 UTC | May 20, 15:00 UTC | 1h 50m |
| 2026-05-20 | CXA8657 | HGH → MNL | May 20, 10:15 UTC | May 20, 11:30 UTC | 1h 15m |
| 2026-05-19 | CXA828 | MNL → XMN | May 19, 04:10 UTC | May 19, 04:35 UTC | 25m |
| 2026-05-19 | CXA827 | XMN → MNL | May 19, 01:00 UTC | May 19, 02:20 UTC | 1h 20m |
| 2026-05-15 | CXA818 | - | May 15, 10:10 UTC | May 15, 11:15 UTC | 1h 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-5653 page for operator, model, and routing details .