sensors Mode-S transponder
781FC9
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32F9 · AIRBUS A-321neo
- Hex
- 781FC9
- Octal
- 36017711
- Decimal
- 7,872,457
- Country
- CN
- Tail
- B-32F9
- Type
- A21N
- Flights observed
- 61
- Distinct callsigns
- 9
- Country
- CN
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address 781FC9 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UEA2220 | - | Jul 13, 12:05 UTC | Jul 13, 12:20 UTC | 15m |
| 2026-07-13 | UEA2219 | - | Jul 13, 10:40 UTC | Jul 13, 10:50 UTC | 10m |
| 2026-07-11 | UEA2218 | - | Jul 11, 03:45 UTC | Jul 11, 04:01 UTC | 15m |
| 2026-07-11 | UEA2217 | - | Jul 11, 01:55 UTC | Jul 11, 02:05 UTC | 10m |
| 2026-07-08 | UEA2207 | - | Jul 8, 12:30 UTC | Jul 8, 15:30 UTC | 3h 0m |
| 2026-07-06 | UEA2208 | - | Jul 6, 12:35 UTC | Jul 6, 15:25 UTC | 2h 50m |
| 2026-07-05 | UEA6666 | PKX → CTU | Jul 5, 04:45 UTC | Jul 5, 05:00 UTC | 15m |
| 2026-07-04 | UEA2220 | - | Jul 4, 14:40 UTC | Jul 4, 14:50 UTC | 10m |
| 2026-07-04 | UEA2219 | - | Jul 4, 13:15 UTC | Jul 4, 13:25 UTC | 10m |
| 2026-07-03 | UEA2220 | - | Jul 3, 15:45 UTC | Jul 3, 16:00 UTC | 15m |
| 2026-07-02 | UEA2220 | - | Jul 2, 12:15 UTC | Jul 2, 12:30 UTC | 15m |
| 2026-07-02 | UEA2219 | - | Jul 2, 10:35 UTC | Jul 2, 10:45 UTC | 10m |
| 2026-06-30 | UEA2208 | - | Jun 30, 15:25 UTC | Jun 30, 15:40 UTC | 15m |
| 2026-06-30 | UEA2207 | - | Jun 30, 12:35 UTC | Jun 30, 13:15 UTC | 40m |
| 2026-06-25 | UEA2207 | CTU → SYX | Jun 25, 12:25 UTC | Jun 26, 06:39 UTC | 18h 15m |
| 2026-06-23 | UEA2264 | - | Jun 23, 15:09 UTC | Jun 24, 11:05 UTC | 19h 55m |
| 2026-06-23 | UEA2264 | - | Jun 23, 12:29 UTC | Jun 24, 11:05 UTC | 22h 35m |
| 2026-06-21 | UEA2220 | - | Jun 21, 12:14 UTC | Jun 21, 12:24 UTC | 10m |
| 2026-06-20 | UEA2208 | SYX → CTU | Jun 20, 14:54 UTC | Jun 20, 15:24 UTC | 30m |
| 2026-06-20 | UEA2207 | CTU → SYX | Jun 20, 12:34 UTC | Jun 20, 12:59 UTC | 25m |
| 2026-06-19 | UEA2220 | - | Jun 19, 15:39 UTC | Jun 19, 15:49 UTC | 10m |
| 2026-06-12 | UEA2218 | SZX → CTU | Jun 12, 03:40 UTC | Jun 12, 03:55 UTC | 15m |
| 2026-05-29 | UEA2218 | SZX → CTU | May 29, 03:45 UTC | May 29, 04:00 UTC | 15m |
| 2026-05-16 | UEA2220 | SZX → CTU | May 16, 13:25 UTC | May 16, 13:35 UTC | 10m |
| 2026-05-15 | UEA2264 | HGH → HAK | May 15, 07:40 UTC | May 15, 11:05 UTC | 3h 25m |
| 2026-05-14 | UEA2220 | SZX → CTU | May 14, 15:01 UTC | May 14, 15:15 UTC | 15m |
| 2026-05-13 | UEA2264 | HGH → HAK | May 13, 06:25 UTC | May 13, 06:50 UTC | 25m |
| 2026-05-12 | UEA2264 | HGH → HAK | May 12, 09:45 UTC | May 13, 06:50 UTC | 21h 5m |
| 2026-05-12 | UEA2264 | HGH → HAK | May 12, 06:15 UTC | May 12, 06:35 UTC | 20m |
| 2026-05-11 | UEA2220 | SZX → CTU | May 11, 12:10 UTC | May 11, 12:25 UTC | 15m |
| 2026-05-11 | UEA2219 | CTU → SZX | May 11, 10:30 UTC | May 11, 10:40 UTC | 10m |
| 2026-05-10 | UEA2218 | SZX → CTU | May 10, 03:40 UTC | May 10, 03:55 UTC | 15m |
| 2026-05-08 | UEA2220 | SZX → CTU | May 8, 12:25 UTC | May 8, 12:34 UTC | 10m |
| 2026-05-08 | UEA2219 | CTU → SZX | May 8, 10:49 UTC | May 8, 10:59 UTC | 10m |
| 2026-05-07 | UEA2218 | SZX → CTU | May 7, 03:50 UTC | May 7, 04:00 UTC | 10m |
| 2026-05-06 | UEA2218 | SZX → CTU | May 6, 03:45 UTC | May 6, 04:00 UTC | 15m |
| 2026-05-05 | UEA2264 | HGH → HAK | May 5, 06:30 UTC | May 5, 06:50 UTC | 20m |
| 2026-05-03 | UEA2220 | SZX → CTU | May 3, 14:00 UTC | May 3, 14:10 UTC | 10m |
| 2026-05-03 | UEA2219 | CTU → SZX | May 3, 11:50 UTC | May 3, 12:05 UTC | 15m |
| 2026-05-02 | UEA2220 | SZX → CTU | May 2, 12:25 UTC | May 2, 12:40 UTC | 15m |
| 2026-05-02 | UEA2219 | CTU → SZX | May 2, 10:30 UTC | May 2, 10:40 UTC | 10m |
| 2026-05-01 | UEA2220 | SZX → CTU | May 1, 12:15 UTC | May 1, 12:25 UTC | 10m |
| 2026-04-30 | UEA2220 | SZX → CTU | Apr 30, 12:20 UTC | Apr 30, 12:30 UTC | 10m |
| 2026-04-29 | UEA2264 | HGH → HAK | Apr 29, 07:45 UTC | Apr 29, 08:05 UTC | 20m |
| 2026-04-28 | UEA2220 | SZX → CTU | Apr 28, 13:20 UTC | Apr 28, 13:35 UTC | 15m |
| 2026-04-27 | UEA2264 | HGH → HAK | Apr 27, 06:35 UTC | Apr 27, 11:45 UTC | 5h 10m |
| 2026-04-26 | UEA2264 | HGH → HAK | Apr 26, 10:00 UTC | Apr 27, 07:00 UTC | 21h 0m |
| 2026-04-26 | UEA2264 | HGH → HAK | Apr 26, 06:35 UTC | Apr 26, 10:10 UTC | 3h 35m |
| 2026-04-25 | UEA2264 | HGH → HAK | Apr 25, 12:20 UTC | Apr 26, 10:10 UTC | 21h 50m |
| 2026-04-25 | UEA2264 | HGH → HAK | Apr 25, 12:10 UTC | Apr 26, 10:10 UTC | 22h 0m |
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-32F9 page for operator, model, and routing details .