sensors Mode-S transponder
781750
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-20CR · BOEING 737 MAX 8
- Hex
- 781750
- Octal
- 36013520
- Decimal
- 7,870,288
- Country
- CN
- Tail
- B-20CR
- Type
- B38M
- Flights observed
- 62
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 781750 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 |
|---|---|---|---|
| CXA8674 | - | 10 | 2026-06-21 |
| CXA8359 | - | 10 | 2026-07-10 |
| CXA8673 | - | 9 | 2026-06-20 |
| CXA8693 | - | 7 | 2026-06-18 |
| CXA8694 | - | 4 | 2026-06-18 |
| CXA895 | Xiamen Airlines | 3 | 2026-06-12 |
| CXA8684 | - | 2 | 2026-06-20 |
| CXA8397 | - | 2 | 2026-07-01 |
| CXA8360 | Xiamen Airlines | 2 | 2026-05-02 |
| CXA8307 | - | 2 | 2026-06-23 |
| CXA8080 | Xiamen Airlines | 2 | 2026-04-23 |
| CXA8683 | Xiamen Airlines | 1 | 2026-06-14 |
| CXA864 | Xiamen Airlines | 1 | 2026-06-15 |
| CXA8375 | Xiamen Airlines | 1 | 2026-05-23 |
| CXA8370 | Xiamen Airlines | 1 | 2026-04-19 |
| CXA8369 | Xiamen Airlines | 1 | 2026-04-19 |
| CXA8366 | - | 1 | 2026-06-16 |
| CXA8342 | - | 1 | 2026-05-27 |
| CXA8230 | Xiamen Airlines | 1 | 2026-04-18 |
| CXA8229 | Xiamen Airlines | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | CXA8359 | - | Jul 10, 10:20 UTC | Jul 10, 14:30 UTC | 4h 10m |
| 2026-07-01 | CXA8397 | - | Jul 1, 00:40 UTC | Jul 1, 04:40 UTC | 4h 0m |
| 2026-06-24 | CXA8359 | - | Jun 24, 09:59 UTC | Jun 24, 10:19 UTC | 20m |
| 2026-06-23 | CXA8359 | - | Jun 23, 13:00 UTC | Jun 24, 10:19 UTC | 21h 20m |
| 2026-06-23 | CXA8307 | - | Jun 23, 09:20 UTC | Jun 23, 13:05 UTC | 3h 45m |
| 2026-06-22 | CXA8359 | - | Jun 22, 09:49 UTC | Jun 22, 14:19 UTC | 4h 30m |
| 2026-06-21 | CXA8674 | - | Jun 21, 16:34 UTC | Jun 21, 20:40 UTC | 4h 5m |
| 2026-06-20 | CXA8684 | - | Jun 20, 23:59 UTC | Jun 21, 10:19 UTC | 10h 20m |
| 2026-06-20 | CXA8673 | - | Jun 20, 17:14 UTC | Jun 20, 21:30 UTC | 4h 15m |
| 2026-06-18 | CXA8674 | - | Jun 18, 17:21 UTC | Jun 18, 20:45 UTC | 3h 24m |
| 2026-06-18 | CXA8674 | - | Jun 18, 16:35 UTC | Jun 18, 16:50 UTC | 15m |
| 2026-06-18 | CXA8693 | - | Jun 18, 14:25 UTC | Jun 18, 14:45 UTC | 20m |
| 2026-06-18 | CXA8694 | - | Jun 18, 00:10 UTC | Jun 18, 12:55 UTC | 12h 45m |
| 2026-06-17 | CXA8673 | - | Jun 17, 17:15 UTC | Jun 17, 21:25 UTC | 4h 10m |
| 2026-06-16 | CXA8366 | - | Jun 16, 14:55 UTC | Jun 16, 15:05 UTC | 10m |
| 2026-06-15 | CXA864 | SIN → HGH | Jun 15, 13:10 UTC | Jun 15, 15:25 UTC | 2h 15m |
| 2026-06-14 | CXA8674 | CGK → CKG | Jun 14, 16:25 UTC | Jun 15, 11:34 UTC | 19h 10m |
| 2026-06-14 | CXA8683 | WUH → CGK | Jun 14, 14:00 UTC | Jun 14, 14:20 UTC | 20m |
| 2026-06-14 | CXA8684 | - | Jun 14, 00:25 UTC | Jun 14, 10:05 UTC | 9h 40m |
| 2026-06-13 | CXA8673 | - | Jun 13, 18:50 UTC | Jun 13, 22:55 UTC | 4h 5m |
| 2026-06-12 | CXA895 | XMN → PNH | Jun 12, 07:40 UTC | Jun 12, 07:55 UTC | 15m |
| 2026-06-07 | CXA895 | XMN → PNH | Jun 7, 14:15 UTC | Jun 8, 08:00 UTC | 17h 45m |
| 2026-05-31 | CXA8359 | XMN → NNG | May 31, 10:00 UTC | May 31, 10:15 UTC | 15m |
| 2026-05-29 | CXA895 | XMN → PNH | May 29, 07:45 UTC | May 29, 08:00 UTC | 15m |
| 2026-05-29 | CXA8397 | - | May 29, 00:35 UTC | May 29, 04:40 UTC | 4h 5m |
| 2026-05-27 | CXA8342 | - | May 27, 08:45 UTC | May 27, 09:00 UTC | 15m |
| 2026-05-26 | CXA8674 | CGK → CKG | May 26, 16:30 UTC | May 27, 05:55 UTC | 13h 25m |
| 2026-05-25 | CXA8694 | CGK → NKG | May 25, 23:49 UTC | May 26, 12:40 UTC | 12h 50m |
| 2026-05-25 | CXA8673 | CKG → CGK | May 25, 19:54 UTC | May 25, 21:30 UTC | 1h 35m |
| 2026-05-23 | CXA8375 | XMN → NNG | May 23, 23:30 UTC | May 24, 03:20 UTC | 3h 50m |
| 2026-05-18 | CXA8359 | XMN → NNG | May 18, 10:45 UTC | May 18, 11:05 UTC | 20m |
| 2026-05-16 | CXA8674 | CGK → CKG | May 16, 16:35 UTC | May 17, 02:55 UTC | 10h 20m |
| 2026-05-15 | CXA8693 | NKG → CGK | May 15, 19:55 UTC | May 16, 12:45 UTC | 16h 51m |
| 2026-05-12 | CXA8674 | CGK → CKG | May 12, 16:25 UTC | May 13, 09:10 UTC | 16h 45m |
| 2026-05-12 | CXA8693 | NKG → CGK | May 12, 14:10 UTC | May 12, 14:30 UTC | 20m |
| 2026-05-12 | CXA8693 | NKG → CGK | May 12, 04:05 UTC | May 12, 12:45 UTC | 8h 40m |
| 2026-05-11 | CXA8673 | CKG → CGK | May 11, 21:05 UTC | May 11, 21:25 UTC | 20m |
| 2026-05-11 | CXA8673 | CKG → CGK | May 11, 19:45 UTC | May 11, 20:35 UTC | 50m |
| 2026-05-09 | CXA8674 | CGK → CKG | May 9, 16:35 UTC | May 9, 18:05 UTC | 1h 30m |
| 2026-05-09 | CXA8693 | NKG → CGK | May 9, 14:25 UTC | May 9, 14:45 UTC | 20m |
| 2026-05-08 | CXA8693 | NKG → CGK | May 8, 23:45 UTC | May 9, 13:00 UTC | 13h 15m |
| 2026-05-08 | CXA8673 | CKG → CGK | May 8, 19:50 UTC | May 8, 21:25 UTC | 1h 35m |
| 2026-05-06 | CXA8359 | XMN → NNG | May 6, 10:05 UTC | May 6, 10:30 UTC | 25m |
| 2026-05-05 | CXA8359 | XMN → NNG | May 5, 12:35 UTC | May 6, 10:30 UTC | 21h 55m |
| 2026-05-05 | CXA8307 | XMN → SYX | May 5, 09:10 UTC | May 5, 12:50 UTC | 3h 40m |
| 2026-05-02 | CXA8360 | NNG → XMN | May 2, 15:55 UTC | May 2, 16:05 UTC | 10m |
| 2026-05-01 | CXA8229 | TSN → URC | May 1, 03:40 UTC | May 1, 12:25 UTC | 8h 45m |
| 2026-04-29 | CXA8359 | XMN → NNG | Apr 29, 12:30 UTC | Apr 29, 12:50 UTC | 20m |
| 2026-04-27 | CXA8359 | XMN → NNG | Apr 27, 00:30 UTC | Apr 27, 11:45 UTC | 11h 15m |
| 2026-04-25 | CXA8674 | CGK → CKG | Apr 25, 17:35 UTC | Apr 25, 18:00 UTC | 25m |
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-20CR page for operator, model, and routing details .