sensors Mode-S transponder
7812F3
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1371 · BOEING 737-800
- Hex
- 7812F3
- Octal
- 36011363
- Decimal
- 7,869,171
- Country
- CN
- Tail
- B-1371
- Type
- B738
- Flights observed
- 51
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 7812F3 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 |
|---|---|---|---|
| CXA8781 | - | 15 | 2026-07-08 |
| CXA8387 | - | 3 | 2026-07-08 |
| CXA8079 | - | 3 | 2026-07-01 |
| CXA8782 | Xiamen Airlines | 2 | 2026-04-26 |
| CXA8388 | - | 2 | 2026-07-09 |
| CXA8380 | - | 2 | 2026-07-14 |
| CXA8221 | - | 2 | 2026-07-19 |
| CXA8040 | - | 2 | 2026-05-02 |
| CXA8828 | Xiamen Airlines | 1 | 2026-05-13 |
| CXA8825 | Xiamen Airlines | 1 | 2026-05-28 |
| CXA8818 | - | 1 | 2026-07-01 |
| CXA8792 | - | 1 | 2026-07-09 |
| CXA8790 | - | 1 | 2026-04-28 |
| CXA8698 | Xiamen Airlines | 1 | 2026-06-15 |
| CXA8697 | - | 1 | 2026-06-14 |
| CXA8692 | - | 1 | 2026-07-21 |
| CXA8691 | - | 1 | 2026-07-21 |
| CXA864 | Xiamen Airlines | 1 | 2026-05-01 |
| CXA863 | Xiamen Airlines | 1 | 2026-05-01 |
| CXA8555 | Xiamen Airlines | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | CXA8692 | - | Jul 21, 06:30 UTC | Jul 21, 06:45 UTC | 15m |
| 2026-07-21 | CXA8691 | - | Jul 21, 04:25 UTC | Jul 21, 05:10 UTC | 45m |
| 2026-07-19 | CXA8221 | - | Jul 19, 08:35 UTC | Jul 19, 08:45 UTC | 10m |
| 2026-07-14 | CXA8523 | - | Jul 14, 13:55 UTC | Jul 15, 02:15 UTC | 12h 19m |
| 2026-07-14 | CXA8380 | - | Jul 14, 04:10 UTC | Jul 14, 04:20 UTC | 10m |
| 2026-07-09 | CXA8792 | - | Jul 9, 16:10 UTC | Jul 9, 16:25 UTC | 15m |
| 2026-07-09 | CXA8388 | - | Jul 9, 08:15 UTC | Jul 9, 08:25 UTC | 10m |
| 2026-07-08 | CXA8387 | - | Jul 8, 23:20 UTC | Jul 9, 05:45 UTC | 6h 25m |
| 2026-07-08 | CXA8387 | - | Jul 8, 09:00 UTC | Jul 9, 05:45 UTC | 20h 45m |
| 2026-07-08 | CXA8781 | - | Jul 8, 06:00 UTC | Jul 8, 23:35 UTC | 17h 35m |
| 2026-07-07 | CXA8781 | - | Jul 7, 23:55 UTC | Jul 8, 00:25 UTC | 30m |
| 2026-07-06 | CXA8221 | - | Jul 6, 06:00 UTC | Jul 6, 06:10 UTC | 10m |
| 2026-07-01 | CXA8818 | - | Jul 1, 12:05 UTC | Jul 2, 02:00 UTC | 13h 55m |
| 2026-07-01 | CXA8079 | - | Jul 1, 00:20 UTC | Jul 1, 17:15 UTC | 16h 55m |
| 2026-06-30 | CXA8079 | - | Jun 30, 15:00 UTC | Jul 1, 12:25 UTC | 21h 25m |
| 2026-06-30 | CXA8079 | - | Jun 30, 11:40 UTC | Jul 1, 00:45 UTC | 13h 5m |
| 2026-06-15 | CXA8698 | HAN → FOC | Jun 15, 09:45 UTC | Jun 15, 10:50 UTC | 1h 5m |
| 2026-06-14 | CXA8697 | - | Jun 14, 13:55 UTC | Jun 15, 07:55 UTC | 18h 0m |
| 2026-06-13 | CXA8144 | - | Jun 13, 04:10 UTC | Jun 13, 04:20 UTC | 10m |
| 2026-06-10 | CXA8222 | - | Jun 10, 04:00 UTC | Jun 10, 04:10 UTC | 10m |
| 2026-06-03 | CXA8044 | CGQ → HGH | Jun 3, 06:45 UTC | Jun 3, 07:30 UTC | 45m |
| 2026-06-01 | CXA8388 | SZX → HGH | Jun 1, 06:35 UTC | Jun 1, 06:50 UTC | 15m |
| 2026-06-01 | CXA8387 | HGH → SZX | Jun 1, 04:20 UTC | Jun 1, 04:40 UTC | 20m |
| 2026-05-28 | CXA8825 | FOC → KWL | May 28, 00:55 UTC | May 28, 01:10 UTC | 15m |
| 2026-05-23 | CXA8781 | SHE → FOC | May 23, 23:45 UTC | May 24, 07:50 UTC | 8h 5m |
| 2026-05-18 | CXA8380 | SZX → TSN | May 18, 04:15 UTC | May 18, 04:25 UTC | 10m |
| 2026-05-13 | CXA8828 | ZUH → XMN | May 13, 15:25 UTC | May 13, 15:45 UTC | 20m |
| 2026-05-13 | CXA8343 | - | May 13, 13:50 UTC | May 13, 14:10 UTC | 20m |
| 2026-05-09 | CXA8781 | SHE → FOC | May 9, 00:00 UTC | May 9, 07:55 UTC | 7h 55m |
| 2026-05-08 | CXA8781 | SHE → FOC | May 8, 09:04 UTC | May 9, 07:55 UTC | 22h 50m |
| 2026-05-08 | CXA8781 | SHE → FOC | May 8, 05:20 UTC | May 9, 04:35 UTC | 23h 15m |
| 2026-05-07 | CXA8781 | SHE → FOC | May 7, 23:34 UTC | May 8, 09:04 UTC | 9h 30m |
| 2026-05-04 | CXA8781 | SHE → FOC | May 4, 23:20 UTC | May 5, 08:05 UTC | 8h 45m |
| 2026-05-02 | CXA8040 | - | May 2, 23:50 UTC | May 3, 00:30 UTC | 40m |
| 2026-05-01 | CXA864 | SIN → HGH | May 1, 13:30 UTC | May 1, 15:50 UTC | 2h 20m |
| 2026-05-01 | CXA863 | HGH → SIN | May 1, 09:15 UTC | May 1, 11:50 UTC | 2h 35m |
| 2026-04-28 | CXA8790 | - | Apr 28, 07:10 UTC | Apr 28, 07:40 UTC | 30m |
| 2026-04-26 | CXA8782 | SYX → FOC | Apr 26, 10:25 UTC | Apr 27, 08:25 UTC | 22h 0m |
| 2026-04-26 | CXA8781 | SHE → FOC | Apr 26, 00:25 UTC | Apr 26, 08:10 UTC | 7h 45m |
| 2026-04-25 | CXA8781 | SHE → FOC | Apr 25, 08:50 UTC | Apr 26, 08:10 UTC | 23h 20m |
| 2026-04-24 | CXA8088 | SHE → HGH | Apr 24, 23:20 UTC | Apr 25, 08:50 UTC | 9h 30m |
| 2026-04-24 | CXA8781 | SHE → FOC | Apr 24, 04:50 UTC | Apr 25, 00:05 UTC | 19h 15m |
| 2026-04-24 | CXA8781 | SHE → FOC | Apr 24, 04:30 UTC | Apr 25, 00:05 UTC | 19h 35m |
| 2026-04-23 | CXA8781 | SHE → FOC | Apr 23, 00:15 UTC | Apr 23, 08:20 UTC | 8h 6m |
| 2026-04-22 | CXA8782 | SYX → FOC | Apr 22, 08:50 UTC | Apr 23, 08:20 UTC | 23h 30m |
| 2026-04-22 | CXA8781 | SHE → FOC | Apr 22, 04:10 UTC | Apr 23, 00:30 UTC | 20h 20m |
| 2026-04-21 | CXA8781 | SHE → FOC | Apr 21, 23:35 UTC | Apr 22, 09:00 UTC | 9h 25m |
| 2026-04-20 | CXA8023 | CSX → HRB | Apr 20, 09:25 UTC | Apr 20, 09:45 UTC | 20m |
| 2026-04-18 | CXA8555 | PKX → PVG | Apr 18, 00:40 UTC | Apr 18, 14:35 UTC | 13h 55m |
| 2026-04-16 | CXA8093 | - | Apr 16, 13:54 UTC | Apr 16, 14:10 UTC | 15m |
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-1371 page for operator, model, and routing details .