sensors Mode-S transponder
781208
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1300 · BOEING 737-800
- Hex
- 781208
- Octal
- 36011010
- Decimal
- 7,868,936
- Country
- CN
- Tail
- B-1300
- Type
- B738
- Flights observed
- 70
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 46m ago
Last known position
Country allocation
The ICAO 24-bit address 781208 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 |
|---|---|---|---|
| CXA8698 | Xiamen Airlines | 4 | 2026-06-03 |
| CXA8526 | - | 4 | 2026-07-05 |
| CXA8818 | - | 3 | 2026-07-17 |
| CXA8781 | Xiamen Airlines | 3 | 2026-05-09 |
| CXA860 | - | 3 | 2026-06-29 |
| CXA859 | - | 3 | 2026-06-29 |
| CXA8309 | Xiamen Airlines | 3 | 2026-06-01 |
| CXA8827 | Xiamen Airlines | 2 | 2026-06-17 |
| CXA8812 | - | 2 | 2026-06-23 |
| CXA8789 | - | 2 | 2026-06-13 |
| CXA8697 | Xiamen Airlines | 2 | 2026-06-03 |
| CXA8555 | - | 2 | 2026-06-22 |
| CXA8366 | Xiamen Airlines | 2 | 2026-05-04 |
| CXA8365 | Xiamen Airlines | 2 | 2026-05-04 |
| CXA8315 | Xiamen Airlines | 2 | 2026-05-23 |
| CXA8076 | Xiamen Airlines | 2 | 2026-06-13 |
| CXA894 | - | 1 | 2026-06-27 |
| CXA893 | Xiamen Airlines | 1 | 2026-05-16 |
| CXA8828 | Xiamen Airlines | 1 | 2026-06-16 |
| CXA8816 | Xiamen Airlines | 1 | 2026-06-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | CXA8818 | - | Jul 17, 05:35 UTC | Jul 18, 02:00 UTC | 20h 25m |
| 2026-07-17 | CXA8818 | - | Jul 17, 00:50 UTC | Jul 17, 14:35 UTC | 13h 45m |
| 2026-07-13 | CXA8515 | - | Jul 13, 11:40 UTC | Jul 13, 12:10 UTC | 30m |
| 2026-07-11 | CXA818 | - | Jul 11, 10:25 UTC | Jul 11, 10:50 UTC | 25m |
| 2026-07-11 | CXA817 | - | Jul 11, 06:45 UTC | Jul 11, 08:35 UTC | 1h 50m |
| 2026-07-07 | CXA8065 | - | Jul 7, 05:20 UTC | Jul 7, 05:40 UTC | 20m |
| 2026-07-05 | CXA8526 | - | Jul 5, 14:10 UTC | Jul 6, 02:25 UTC | 12h 15m |
| 2026-07-01 | - | - | Jul 1, 22:50 UTC | Jul 1, 23:05 UTC | 15m |
| 2026-06-29 | CXA860 | - | Jun 29, 09:05 UTC | Jun 30, 02:15 UTC | 17h 11m |
| 2026-06-29 | CXA859 | - | Jun 29, 05:50 UTC | Jun 29, 07:15 UTC | 1h 25m |
| 2026-06-28 | CXA8390 | - | Jun 28, 16:35 UTC | Jun 28, 16:45 UTC | 10m |
| 2026-06-27 | CXA894 | - | Jun 27, 07:49 UTC | Jun 27, 07:59 UTC | 10m |
| 2026-06-24 | CXA8816 | SYX → XMN | Jun 24, 13:34 UTC | Jun 24, 14:09 UTC | 35m |
| 2026-06-23 | CXA8812 | - | Jun 23, 05:54 UTC | Jun 23, 06:24 UTC | 30m |
| 2026-06-22 | CXA8812 | - | Jun 22, 09:30 UTC | Jun 23, 06:24 UTC | 20h 55m |
| 2026-06-22 | CXA8555 | - | Jun 22, 00:44 UTC | Jun 22, 10:05 UTC | 9h 20m |
| 2026-06-21 | CXA8818 | - | Jun 21, 09:10 UTC | Jun 22, 00:50 UTC | 15h 40m |
| 2026-06-21 | CXA8555 | - | Jun 21, 00:55 UTC | Jun 21, 09:55 UTC | 9h 0m |
| 2026-06-17 | CXA8344 | SZX → HGH | Jun 17, 16:15 UTC | Jun 17, 16:30 UTC | 15m |
| 2026-06-17 | CXA8827 | XMN → ZUH | Jun 17, 14:05 UTC | Jun 17, 14:55 UTC | 50m |
| 2026-06-17 | CXA860 | - | Jun 17, 09:10 UTC | Jun 17, 10:25 UTC | 1h 15m |
| 2026-06-16 | CXA859 | - | Jun 16, 23:50 UTC | Jun 17, 07:35 UTC | 7h 45m |
| 2026-06-16 | CXA8828 | ZUH → XMN | Jun 16, 14:05 UTC | Jun 16, 14:20 UTC | 15m |
| 2026-06-16 | CXA8827 | XMN → ZUH | Jun 16, 12:35 UTC | Jun 16, 12:50 UTC | 15m |
| 2026-06-16 | CXA8341 | - | Jun 16, 05:40 UTC | Jun 16, 09:30 UTC | 3h 50m |
| 2026-06-13 | CXA8789 | - | Jun 13, 14:00 UTC | Jun 13, 14:40 UTC | 40m |
| 2026-06-13 | CXA8076 | CGQ → NGB | Jun 13, 06:35 UTC | Jun 13, 07:10 UTC | 35m |
| 2026-06-05 | CXA8526 | - | Jun 5, 01:50 UTC | Jun 5, 02:10 UTC | 20m |
| 2026-06-03 | CXA8698 | HAN → FOC | Jun 3, 14:00 UTC | Jun 3, 14:15 UTC | 15m |
| 2026-06-03 | CXA8698 | HAN → FOC | Jun 3, 09:50 UTC | Jun 3, 11:00 UTC | 1h 10m |
| 2026-06-03 | CXA8697 | FOC → HAN | Jun 3, 06:25 UTC | Jun 3, 08:00 UTC | 1h 35m |
| 2026-06-01 | CXA8309 | TAO → CSX | Jun 1, 14:15 UTC | Jun 2, 08:05 UTC | 17h 50m |
| 2026-06-01 | CXA8309 | TAO → CSX | Jun 1, 13:55 UTC | Jun 2, 08:05 UTC | 18h 10m |
| 2026-06-01 | CXA8309 | TAO → CSX | Jun 1, 10:05 UTC | Jun 2, 08:05 UTC | 22h 0m |
| 2026-06-01 | CXA860 | - | Jun 1, 08:55 UTC | Jun 2, 08:00 UTC | 23h 5m |
| 2026-06-01 | CXA859 | - | Jun 1, 05:45 UTC | Jun 1, 07:10 UTC | 1h 25m |
| 2026-05-23 | CXA8315 | HGH → HAK | May 23, 01:00 UTC | May 23, 04:00 UTC | 2h 59m |
| 2026-05-22 | CXA8315 | HGH → HAK | May 22, 04:25 UTC | May 23, 04:00 UTC | 23h 34m |
| 2026-05-21 | CXA8044 | CGQ → HGH | May 21, 06:35 UTC | May 22, 04:35 UTC | 22h 0m |
| 2026-05-19 | CXA878 | ICN → FOC | May 19, 11:45 UTC | May 19, 12:10 UTC | 25m |
| 2026-05-19 | CXA877 | FOC → ICN | May 19, 09:00 UTC | May 19, 09:30 UTC | 30m |
| 2026-05-17 | CXA8616 | - | May 17, 03:50 UTC | May 17, 04:10 UTC | 20m |
| 2026-05-16 | CXA893 | FOC → MFM | May 16, 02:10 UTC | May 16, 02:25 UTC | 15m |
| 2026-05-15 | CXA820 | MNL → XMN | May 15, 13:25 UTC | May 15, 13:55 UTC | 30m |
| 2026-05-15 | CXA819 | XMN → MNL | May 15, 10:45 UTC | May 15, 11:40 UTC | 55m |
| 2026-05-09 | CXA8781 | SHE → FOC | May 9, 23:35 UTC | May 10, 09:05 UTC | 9h 30m |
| 2026-05-09 | CXA8781 | SHE → FOC | May 9, 08:45 UTC | May 10, 04:50 UTC | 20h 5m |
| 2026-05-08 | CXA8408 | KWE → XMN | May 8, 05:00 UTC | May 8, 05:14 UTC | 15m |
| 2026-05-06 | - | - | May 6, 22:45 UTC | May 6, 22:55 UTC | 10m |
| 2026-05-04 | CXA8366 | SZX → TSN | May 4, 12:15 UTC | May 4, 12:25 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-1300 page for operator, model, and routing details .