sensors Mode-S transponder
781C98
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-326N · AIRBUS A-320neo
- Hex
- 781C98
- Octal
- 36016230
- Decimal
- 7,871,640
- Country
- CN
- Tail
- B-326N
- Type
- A20N
- Flights observed
- 36
- Distinct callsigns
- 16
- Country
- CN
- Last broadcast
- 23h ago
Current position
Country allocation
The ICAO 24-bit address 781C98 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HXA4719 | - | 6 | 2026-07-02 |
| HXA4063 | China Express Airlines | 6 | 2026-07-24 |
| HXA4550 | - | 4 | 2026-07-18 |
| HXA4549 | - | 4 | 2026-07-18 |
| HXA4840 | China Express Airlines | 3 | 2026-06-25 |
| HXA4720 | - | 2 | 2026-06-20 |
| HXA4274 | China Express Airlines | 2 | 2026-04-30 |
| HXA4977 | - | 1 | 2026-05-04 |
| HXA4940 | China Express Airlines | 1 | 2026-06-10 |
| HXA4939 | China Express Airlines | 1 | 2026-06-10 |
| HXA4839 | - | 1 | 2026-07-03 |
| HXA472Z | - | 1 | 2026-07-03 |
| HXA4589 | China Express Airlines | 1 | 2026-06-21 |
| HXA4217 | - | 1 | 2026-06-07 |
| HXA4095 | - | 1 | 2026-06-19 |
| HXA2806 | - | 1 | 2026-07-18 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | HXA4063 | BAV → HGH | Jul 24, 00:00 UTC | Jul 24, 00:25 UTC | 25m |
| 2026-07-18 | HXA2806 | - | Jul 18, 14:25 UTC | Jul 18, 14:40 UTC | 15m |
| 2026-07-18 | HXA4550 | - | Jul 18, 03:50 UTC | Jul 18, 04:05 UTC | 15m |
| 2026-07-18 | HXA4549 | - | Jul 18, 02:19 UTC | Jul 18, 02:29 UTC | 10m |
| 2026-07-16 | HXA4063 | - | Jul 16, 00:05 UTC | Jul 16, 00:25 UTC | 20m |
| 2026-07-14 | HXA4550 | - | Jul 14, 04:00 UTC | Jul 14, 04:15 UTC | 15m |
| 2026-07-14 | HXA4549 | - | Jul 14, 02:20 UTC | Jul 14, 02:30 UTC | 10m |
| 2026-07-03 | HXA4839 | - | Jul 3, 12:05 UTC | Jul 4, 04:35 UTC | 16h 30m |
| 2026-07-03 | HXA472Z | - | Jul 3, 03:25 UTC | Jul 3, 12:05 UTC | 8h 40m |
| 2026-07-02 | HXA4719 | - | Jul 2, 14:05 UTC | Jul 3, 12:05 UTC | 22h 0m |
| 2026-07-02 | HXA4719 | - | Jul 2, 13:55 UTC | Jul 3, 03:30 UTC | 13h 35m |
| 2026-06-30 | HXA4719 | - | Jun 30, 02:35 UTC | Jun 30, 06:30 UTC | 3h 55m |
| 2026-06-25 | HXA4840 | SJW → TFU | Jun 25, 03:50 UTC | Jun 25, 03:59 UTC | 10m |
| 2026-06-21 | HXA4589 | XIY → BPE | Jun 21, 01:39 UTC | Jun 21, 11:40 UTC | 10h 0m |
| 2026-06-20 | HXA4720 | - | Jun 20, 05:39 UTC | Jun 21, 01:45 UTC | 20h 5m |
| 2026-06-20 | HXA4719 | - | Jun 20, 02:35 UTC | Jun 21, 01:45 UTC | 23h 10m |
| 2026-06-19 | HXA4719 | - | Jun 19, 12:44 UTC | Jun 20, 05:59 UTC | 17h 15m |
| 2026-06-19 | HXA4095 | - | Jun 19, 09:19 UTC | Jun 19, 09:40 UTC | 20m |
| 2026-06-11 | HXA4720 | - | Jun 11, 05:20 UTC | Jun 11, 05:55 UTC | 35m |
| 2026-06-10 | HXA4719 | - | Jun 10, 14:00 UTC | Jun 11, 03:15 UTC | 13h 15m |
| 2026-06-10 | HXA4940 | SJW → TFU | Jun 10, 04:00 UTC | Jun 10, 04:10 UTC | 10m |
| 2026-06-10 | HXA4939 | TFU → SJW | Jun 10, 02:20 UTC | Jun 10, 02:30 UTC | 10m |
| 2026-06-07 | HXA4217 | - | Jun 7, 01:30 UTC | Jun 7, 05:35 UTC | 4h 5m |
| 2026-06-06 | HXA4840 | SJW → TFU | Jun 6, 03:55 UTC | Jun 6, 04:15 UTC | 20m |
| 2026-05-30 | HXA4063 | BAV → HGH | May 30, 23:45 UTC | May 31, 00:10 UTC | 25m |
| 2026-05-29 | HXA4063 | BAV → HGH | May 29, 00:40 UTC | May 29, 01:00 UTC | 20m |
| 2026-05-26 | HXA4550 | - | May 26, 03:45 UTC | May 26, 03:55 UTC | 10m |
| 2026-05-26 | HXA4549 | - | May 26, 02:15 UTC | May 26, 02:24 UTC | 10m |
| 2026-05-22 | HXA4063 | BAV → HGH | May 22, 00:00 UTC | May 22, 00:20 UTC | 20m |
| 2026-05-20 | HXA4063 | BAV → HGH | May 20, 04:40 UTC | May 20, 05:05 UTC | 25m |
| 2026-05-07 | HXA4550 | - | May 7, 03:45 UTC | May 7, 04:00 UTC | 15m |
| 2026-05-07 | HXA4549 | - | May 7, 02:15 UTC | May 7, 02:25 UTC | 10m |
| 2026-05-04 | HXA4977 | - | May 4, 02:10 UTC | May 4, 02:19 UTC | 10m |
| 2026-04-30 | HXA4274 | ZUH → DYG | Apr 30, 12:10 UTC | Apr 30, 12:25 UTC | 15m |
| 2026-04-25 | HXA4840 | SJW → TFU | Apr 25, 04:05 UTC | Apr 25, 04:15 UTC | 10m |
| 2026-04-23 | HXA4274 | ZUH → DYG | Apr 23, 13:15 UTC | Apr 23, 13:30 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-326N page for operator, model, and routing details .