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