sensors Mode-S transponder
7812C0
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1355 · BOEING 737-800
- Hex
- 7812C0
- Octal
- 36011300
- Decimal
- 7,869,120
- Country
- CN
- Tail
- B-1355
- Type
- B738
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7812C0 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 |
|---|---|---|---|
| CXA860 | - | 3 | 2026-06-26 |
| CXA859 | - | 3 | 2026-06-26 |
| CXA8526 | - | 3 | 2026-06-27 |
| CXA8523 | - | 3 | 2026-06-26 |
| CXA818 | - | 3 | 2026-06-24 |
| CXA8790 | - | 2 | 2026-06-02 |
| CXA817 | - | 2 | 2026-06-24 |
| CXA8789 | - | 1 | 2026-06-15 |
| CXA8728 | - | 1 | 2026-05-23 |
| CXA8727 | Xiamen Airlines | 1 | 2026-05-21 |
| CXA8698 | Xiamen Airlines | 1 | 2026-05-22 |
| CXA8697 | Xiamen Airlines | 1 | 2026-05-22 |
| CXA8696 | - | 1 | 2026-06-23 |
| CXA8692 | - | 1 | 2026-07-04 |
| CXA8691 | - | 1 | 2026-07-04 |
| CXA8682 | Xiamen Airlines | 1 | 2026-05-29 |
| CXA8681 | Xiamen Airlines | 1 | 2026-05-29 |
| CXA8605 | Xiamen Airlines | 1 | 2026-04-30 |
| CXA8427 | Xiamen Airlines | 1 | 2026-05-30 |
| CXA8360 | Xiamen Airlines | 1 | 2026-05-29 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-04 | CXA8692 | - | Jul 4, 10:15 UTC | Jul 4, 10:30 UTC | 15m |
| 2026-07-04 | CXA8691 | - | Jul 4, 08:00 UTC | Jul 4, 08:05 UTC | 5m |
| 2026-06-29 | CXA8029 | WUH → SHE | Jun 29, 03:10 UTC | Jun 29, 03:25 UTC | 15m |
| 2026-06-27 | CXA8526 | - | Jun 27, 11:04 UTC | Jun 28, 02:14 UTC | 15h 10m |
| 2026-06-27 | CXA8526 | - | Jun 27, 05:15 UTC | Jun 28, 02:14 UTC | 21h 0m |
| 2026-06-26 | CXA8523 | - | Jun 26, 14:05 UTC | Jun 27, 11:14 UTC | 21h 10m |
| 2026-06-26 | CXA8523 | - | Jun 26, 13:59 UTC | Jun 27, 11:14 UTC | 21h 15m |
| 2026-06-26 | CXA860 | - | Jun 26, 09:05 UTC | Jun 26, 09:30 UTC | 25m |
| 2026-06-26 | CXA859 | - | Jun 26, 05:35 UTC | Jun 26, 07:30 UTC | 1h 55m |
| 2026-06-24 | CXA818 | - | Jun 24, 11:24 UTC | Jun 24, 11:34 UTC | 10m |
| 2026-06-24 | CXA818 | - | Jun 24, 10:14 UTC | Jun 24, 10:45 UTC | 30m |
| 2026-06-24 | CXA817 | - | Jun 24, 07:44 UTC | Jun 24, 08:30 UTC | 45m |
| 2026-06-23 | CXA8696 | - | Jun 23, 08:09 UTC | Jun 23, 12:55 UTC | 4h 45m |
| 2026-06-20 | CXA860 | - | Jun 20, 09:09 UTC | Jun 21, 02:40 UTC | 17h 30m |
| 2026-06-19 | CXA859 | - | Jun 19, 13:39 UTC | Jun 20, 07:09 UTC | 17h 30m |
| 2026-06-15 | CXA8789 | - | Jun 15, 14:20 UTC | Jun 15, 14:50 UTC | 30m |
| 2026-06-15 | CXA860 | - | Jun 15, 09:05 UTC | Jun 15, 09:20 UTC | 15m |
| 2026-06-14 | CXA859 | - | Jun 14, 14:00 UTC | Jun 15, 07:25 UTC | 17h 24m |
| 2026-06-07 | CXA8321 | HGH → SYX | Jun 7, 00:19 UTC | Jun 7, 04:20 UTC | 4h 0m |
| 2026-06-06 | CXA8230 | TSN → HGH | Jun 6, 11:49 UTC | Jun 6, 12:10 UTC | 20m |
| 2026-06-06 | CXA8229 | TSN → URC | Jun 6, 03:35 UTC | Jun 6, 04:00 UTC | 25m |
| 2026-06-02 | CXA8790 | - | Jun 2, 02:10 UTC | Jun 2, 02:25 UTC | 15m |
| 2026-05-30 | CXA8427 | XMN → KWE | May 30, 09:35 UTC | May 30, 15:15 UTC | 5h 40m |
| 2026-05-30 | CXA8790 | - | May 30, 07:05 UTC | May 30, 07:35 UTC | 30m |
| 2026-05-29 | CXA8360 | NNG → XMN | May 29, 14:40 UTC | May 29, 15:00 UTC | 20m |
| 2026-05-29 | CXA8359 | XMN → NNG | May 29, 10:05 UTC | May 29, 11:05 UTC | 1h 0m |
| 2026-05-29 | CXA8682 | MFM → XMN | May 29, 07:10 UTC | May 29, 07:20 UTC | 10m |
| 2026-05-29 | CXA8681 | XMN → MFM | May 29, 04:50 UTC | May 29, 05:15 UTC | 25m |
| 2026-05-27 | CXA818 | - | May 27, 10:05 UTC | May 27, 10:50 UTC | 45m |
| 2026-05-27 | CXA817 | - | May 27, 06:44 UTC | May 27, 08:25 UTC | 1h 41m |
| 2026-05-25 | CXA8346 | SZX → HGH | May 25, 15:40 UTC | May 25, 15:50 UTC | 10m |
| 2026-05-24 | CXA8526 | - | May 24, 01:50 UTC | May 24, 02:20 UTC | 30m |
| 2026-05-23 | CXA8728 | - | May 23, 10:30 UTC | May 23, 11:15 UTC | 45m |
| 2026-05-22 | CXA8698 | HAN → FOC | May 22, 13:55 UTC | May 22, 14:15 UTC | 20m |
| 2026-05-22 | CXA8697 | FOC → HAN | May 22, 06:40 UTC | May 22, 11:00 UTC | 4h 20m |
| 2026-05-21 | CXA8727 | TAO → FOC | May 21, 04:40 UTC | May 21, 04:50 UTC | 10m |
| 2026-05-20 | CXA8523 | - | May 20, 06:20 UTC | May 20, 14:20 UTC | 8h 0m |
| 2026-05-19 | CXA8315 | HGH → HAK | May 19, 00:45 UTC | May 19, 01:00 UTC | 15m |
| 2026-05-08 | CXA8051 | - | May 8, 10:54 UTC | May 9, 09:40 UTC | 22h 45m |
| 2026-04-30 | CXA8605 | FOC → NNG | Apr 30, 13:10 UTC | May 1, 07:15 UTC | 18h 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-1355 page for operator, model, and routing details .