sensors Mode-S transponder
7817FE
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-20DU · BOEING 737 MAX 8
- Hex
- 7817FE
- Octal
- 36013776
- Decimal
- 7,870,462
- Country
- CN
- Tail
- B-20DU
- Type
- B38M
- Flights observed
- 79
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 7817FE 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 |
|---|---|---|---|
| CXA868 | Xiamen Airlines | 9 | 2026-05-06 |
| CXA867 | Xiamen Airlines | 7 | 2026-05-06 |
| CXA848 | Xiamen Airlines | 7 | 2026-05-21 |
| CXA847 | Xiamen Airlines | 7 | 2026-05-21 |
| CXA838 | - | 5 | 2026-05-19 |
| CXA8371 | Xiamen Airlines | 5 | 2026-05-04 |
| CXA837 | - | 5 | 2026-05-19 |
| CXA897 | Xiamen Airlines | 4 | 2026-05-24 |
| CXA892 | Xiamen Airlines | 4 | 2026-05-12 |
| CXA8882 | Xiamen Airlines | 4 | 2026-04-23 |
| CXA898 | Xiamen Airlines | 3 | 2026-05-24 |
| CXA8881 | Xiamen Airlines | 3 | 2026-04-22 |
| CXA8372 | Xiamen Airlines | 3 | 2026-04-23 |
| CXA824 | Xiamen Airlines | 3 | 2026-05-18 |
| CXA823 | Xiamen Airlines | 3 | 2026-05-17 |
| CXA8705 | Xiamen Airlines | 2 | 2026-04-19 |
| CXA8032 | Xiamen Airlines | 2 | 2026-05-19 |
| CXA891 | Xiamen Airlines | 1 | 2026-04-17 |
| CXA8022 | Xiamen Airlines | 1 | 2026-05-15 |
| CXA8021 | Xiamen Airlines | 1 | 2026-05-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-24 | CXA898 | KUL → FOC | May 24, 13:10 UTC | May 24, 13:20 UTC | 10m |
| 2026-05-24 | CXA898 | KUL → FOC | May 24, 09:55 UTC | May 24, 10:20 UTC | 25m |
| 2026-05-24 | CXA897 | FOC → KUL | May 24, 05:00 UTC | May 24, 08:20 UTC | 3h 20m |
| 2026-05-23 | CXA897 | FOC → KUL | May 23, 10:20 UTC | May 24, 08:20 UTC | 22h 1m |
| 2026-05-23 | CXA897 | FOC → KUL | May 23, 08:25 UTC | May 23, 08:45 UTC | 20m |
| 2026-05-21 | CXA848 | KUL → XMN | May 21, 06:50 UTC | May 21, 07:10 UTC | 20m |
| 2026-05-21 | CXA847 | XMN → KUL | May 21, 01:50 UTC | May 21, 05:20 UTC | 3h 30m |
| 2026-05-19 | CXA838 | - | May 19, 16:45 UTC | May 19, 18:15 UTC | 1h 30m |
| 2026-05-19 | CXA837 | - | May 19, 12:35 UTC | May 19, 13:20 UTC | 45m |
| 2026-05-19 | CXA8032 | SHE → XMN | May 19, 06:10 UTC | May 19, 08:10 UTC | 2h 0m |
| 2026-05-18 | CXA824 | KUL → XMN | May 18, 00:35 UTC | May 18, 00:50 UTC | 15m |
| 2026-05-17 | CXA823 | XMN → KUL | May 17, 12:20 UTC | May 17, 15:55 UTC | 3h 35m |
| 2026-05-15 | CXA8022 | CGQ → FOC | May 15, 23:40 UTC | May 16, 10:31 UTC | 10h 51m |
| 2026-05-13 | CXA8021 | SZX → FOC | May 13, 23:50 UTC | May 14, 10:40 UTC | 10h 50m |
| 2026-05-12 | CXA892 | DPS → XMN | May 12, 12:20 UTC | May 12, 21:30 UTC | 9h 10m |
| 2026-05-07 | CXA898 | KUL → FOC | May 7, 10:20 UTC | May 7, 10:50 UTC | 30m |
| 2026-05-07 | CXA897 | FOC → KUL | May 7, 08:15 UTC | May 7, 08:45 UTC | 30m |
| 2026-05-06 | CXA868 | CGK → XMN | May 6, 08:25 UTC | May 6, 08:45 UTC | 20m |
| 2026-05-06 | CXA868 | CGK → XMN | May 6, 07:15 UTC | May 6, 07:25 UTC | 10m |
| 2026-05-06 | CXA867 | XMN → CGK | May 6, 04:40 UTC | May 6, 04:55 UTC | 15m |
| 2026-05-05 | CXA838 | - | May 5, 17:20 UTC | May 6, 03:10 UTC | 9h 50m |
| 2026-05-05 | CXA837 | - | May 5, 13:30 UTC | May 5, 14:20 UTC | 50m |
| 2026-05-04 | CXA8371 | SHA → SZX | May 4, 02:19 UTC | May 4, 02:45 UTC | 25m |
| 2026-05-02 | CXA868 | CGK → XMN | May 2, 07:35 UTC | May 2, 08:00 UTC | 25m |
| 2026-05-02 | CXA868 | CGK → XMN | May 2, 06:30 UTC | May 2, 06:40 UTC | 10m |
| 2026-05-02 | CXA867 | XMN → CGK | May 2, 05:00 UTC | May 2, 05:10 UTC | 10m |
| 2026-05-01 | CXA867 | XMN → CGK | May 1, 17:40 UTC | May 2, 03:25 UTC | 9h 45m |
| 2026-05-01 | CXA837 | - | May 1, 05:45 UTC | May 1, 13:55 UTC | 8h 10m |
| 2026-04-30 | CXA848 | KUL → XMN | Apr 30, 07:05 UTC | Apr 30, 07:40 UTC | 35m |
| 2026-04-29 | CXA838 | - | Apr 29, 18:15 UTC | Apr 30, 05:35 UTC | 11h 19m |
| 2026-04-29 | CXA837 | - | Apr 29, 12:30 UTC | Apr 29, 15:00 UTC | 2h 30m |
| 2026-04-28 | CXA868 | CGK → XMN | Apr 28, 08:30 UTC | Apr 28, 08:55 UTC | 25m |
| 2026-04-28 | CXA868 | CGK → XMN | Apr 28, 07:25 UTC | Apr 28, 07:35 UTC | 10m |
| 2026-04-28 | CXA867 | XMN → CGK | Apr 28, 05:35 UTC | Apr 28, 05:50 UTC | 15m |
| 2026-04-28 | CXA867 | XMN → CGK | Apr 28, 01:25 UTC | Apr 28, 03:50 UTC | 2h 25m |
| 2026-04-26 | CXA824 | KUL → XMN | Apr 26, 23:55 UTC | Apr 27, 00:25 UTC | 30m |
| 2026-04-26 | CXA823 | XMN → KUL | Apr 26, 14:40 UTC | Apr 26, 17:55 UTC | 3h 15m |
| 2026-04-26 | CXA848 | KUL → XMN | Apr 26, 07:05 UTC | Apr 26, 08:35 UTC | 1h 30m |
| 2026-04-26 | CXA847 | XMN → KUL | Apr 26, 03:40 UTC | Apr 26, 05:10 UTC | 1h 30m |
| 2026-04-23 | CXA8882 | ZUH → SHA | Apr 23, 14:00 UTC | Apr 23, 14:10 UTC | 10m |
| 2026-04-23 | CXA8372 | SZX → SHA | Apr 23, 06:35 UTC | Apr 23, 07:20 UTC | 45m |
| 2026-04-23 | CXA8371 | SHA → SZX | Apr 23, 02:25 UTC | Apr 23, 02:45 UTC | 20m |
| 2026-04-22 | CXA8882 | ZUH → SHA | Apr 22, 12:35 UTC | Apr 22, 12:50 UTC | 15m |
| 2026-04-22 | CXA8881 | SHA → ZUH | Apr 22, 09:50 UTC | Apr 22, 10:40 UTC | 50m |
| 2026-04-22 | CXA8372 | SZX → SHA | Apr 22, 05:10 UTC | Apr 22, 05:20 UTC | 10m |
| 2026-04-22 | CXA8371 | SHA → SZX | Apr 22, 03:30 UTC | Apr 22, 03:45 UTC | 15m |
| 2026-04-21 | CXA8882 | ZUH → SHA | Apr 21, 11:35 UTC | Apr 21, 11:45 UTC | 10m |
| 2026-04-21 | CXA8881 | SHA → ZUH | Apr 21, 09:35 UTC | Apr 21, 09:50 UTC | 15m |
| 2026-04-21 | CXA8372 | SZX → SHA | Apr 21, 04:05 UTC | Apr 21, 04:20 UTC | 15m |
| 2026-04-21 | CXA8371 | SHA → SZX | Apr 21, 02:40 UTC | Apr 21, 02:50 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-20DU page for operator, model, and routing details .