sensors Mode-S transponder
781223
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8697 · AIRBUS A-320
- Hex
- 781223
- Octal
- 36011043
- Decimal
- 7,868,963
- Country
- CN
- Tail
- B-8697
- Type
- A320
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 781223 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 |
|---|---|---|---|
| HXA4940 | - | 5 | 2026-07-19 |
| HXA4939 | - | 4 | 2026-07-19 |
| HXA4018 | China Express Airlines | 4 | 2026-07-08 |
| HXA4095 | - | 3 | 2026-05-11 |
| HXA4027 | - | 3 | 2026-07-03 |
| HXA4839 | - | 2 | 2026-07-11 |
| HXA4028 | - | 2 | 2026-07-03 |
| HXA4840 | - | 1 | 2026-07-16 |
| HXA4590 | - | 1 | 2026-07-13 |
| HXA4550 | - | 1 | 2026-05-21 |
| HXA4549 | - | 1 | 2026-05-21 |
| HXA4362 | - | 1 | 2026-05-17 |
| HXA4318 | China Express Airlines | 1 | 2026-06-27 |
| HXA4274 | China Express Airlines | 1 | 2026-04-21 |
| HXA4228 | - | 1 | 2026-04-25 |
| HXA4218 | - | 1 | 2026-07-06 |
| HXA4217 | - | 1 | 2026-07-06 |
| HXA4164 | - | 1 | 2026-07-24 |
| HXA4163 | China Express Airlines | 1 | 2026-07-24 |
| HXA4140 | - | 1 | 2026-06-30 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | HXA4164 | - | Jul 24, 16:50 UTC | Jul 24, 17:15 UTC | 25m |
| 2026-07-24 | HXA4163 | TSN → DYG | Jul 24, 09:00 UTC | Jul 24, 09:25 UTC | 25m |
| 2026-07-24 | HXA2794 | - | Jul 24, 06:50 UTC | Jul 24, 07:15 UTC | 25m |
| 2026-07-22 | HXA4017 | - | Jul 22, 11:45 UTC | Jul 22, 15:10 UTC | 3h 25m |
| 2026-07-19 | - | - | Jul 19, 13:25 UTC | Jul 19, 13:35 UTC | 10m |
| 2026-07-19 | HXA4940 | - | Jul 19, 04:00 UTC | Jul 19, 04:15 UTC | 15m |
| 2026-07-19 | HXA4939 | - | Jul 19, 02:35 UTC | Jul 19, 02:45 UTC | 10m |
| 2026-07-16 | HXA4840 | - | Jul 16, 03:35 UTC | Jul 16, 03:50 UTC | 15m |
| 2026-07-13 | HXA4590 | - | Jul 13, 11:35 UTC | Jul 13, 14:00 UTC | 2h 25m |
| 2026-07-11 | HXA4839 | - | Jul 11, 04:20 UTC | Jul 11, 04:40 UTC | 20m |
| 2026-07-08 | HXA4018 | BPE → TFU | Jul 8, 13:45 UTC | Jul 9, 02:50 UTC | 13h 5m |
| 2026-07-08 | HXA4940 | - | Jul 8, 04:10 UTC | Jul 8, 04:20 UTC | 10m |
| 2026-07-08 | HXA4939 | - | Jul 8, 02:45 UTC | Jul 8, 02:55 UTC | 10m |
| 2026-07-06 | HXA4218 | - | Jul 6, 05:20 UTC | Jul 7, 02:55 UTC | 21h 35m |
| 2026-07-06 | HXA4217 | - | Jul 6, 01:20 UTC | Jul 6, 01:30 UTC | 10m |
| 2026-07-03 | HXA4028 | - | Jul 3, 03:45 UTC | Jul 3, 04:05 UTC | 20m |
| 2026-07-03 | HXA4027 | - | Jul 3, 01:15 UTC | Jul 3, 01:25 UTC | 10m |
| 2026-06-30 | HXA4140 | - | Jun 30, 06:15 UTC | Jun 30, 06:30 UTC | 15m |
| 2026-06-29 | HXA4028 | - | Jun 29, 14:29 UTC | Jun 29, 14:50 UTC | 20m |
| 2026-06-29 | HXA4027 | - | Jun 29, 11:39 UTC | Jun 29, 11:50 UTC | 10m |
| 2026-06-29 | HXA4027 | - | Jun 29, 09:00 UTC | Jun 29, 09:10 UTC | 10m |
| 2026-06-27 | HXA4318 | TSN → LFQ | Jun 27, 10:40 UTC | Jun 27, 11:04 UTC | 25m |
| 2026-06-27 | HXA4839 | - | Jun 27, 04:19 UTC | Jun 27, 04:34 UTC | 15m |
| 2026-06-24 | HXA4018 | BPE → TFU | Jun 24, 13:44 UTC | Jun 24, 14:09 UTC | 25m |
| 2026-06-24 | HXA4940 | - | Jun 24, 04:00 UTC | Jun 24, 04:15 UTC | 15m |
| 2026-06-24 | HXA4939 | - | Jun 24, 02:34 UTC | Jun 24, 02:45 UTC | 10m |
| 2026-06-22 | HXA4018 | BPE → TFU | Jun 22, 13:29 UTC | Jun 23, 02:49 UTC | 13h 20m |
| 2026-06-22 | HXA4940 | - | Jun 22, 04:15 UTC | Jun 22, 04:24 UTC | 10m |
| 2026-06-21 | HXA4018 | BPE → TFU | Jun 21, 13:29 UTC | Jun 22, 02:54 UTC | 13h 25m |
| 2026-06-21 | HXA4940 | SJW → TFU | Jun 21, 03:59 UTC | Jun 21, 04:14 UTC | 15m |
| 2026-06-21 | HXA4939 | TFU → SJW | Jun 21, 02:15 UTC | Jun 21, 02:24 UTC | 10m |
| 2026-05-21 | HXA4550 | - | May 21, 03:50 UTC | May 21, 04:00 UTC | 10m |
| 2026-05-21 | HXA4549 | - | May 21, 02:00 UTC | May 21, 02:15 UTC | 15m |
| 2026-05-17 | HXA4362 | - | May 17, 14:40 UTC | May 17, 15:05 UTC | 25m |
| 2026-05-14 | HXA4087 | - | May 14, 15:50 UTC | May 14, 16:05 UTC | 15m |
| 2026-05-11 | HXA4095 | - | May 11, 09:15 UTC | May 11, 12:40 UTC | 3h 25m |
| 2026-05-10 | HXA4095 | - | May 10, 14:54 UTC | May 11, 12:40 UTC | 21h 45m |
| 2026-05-06 | HXA4095 | - | May 6, 09:10 UTC | May 6, 12:45 UTC | 3h 35m |
| 2026-04-25 | HXA4228 | - | Apr 25, 11:15 UTC | Apr 26, 04:50 UTC | 17h 35m |
| 2026-04-21 | HXA4274 | ZUH → DYG | Apr 21, 11:30 UTC | Apr 21, 11:45 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-8697 page for operator, model, and routing details .