sensors Mode-S transponder
781A94
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-320Z · AIRBUS A-320neo
- Hex
- 781A94
- Octal
- 36015224
- Decimal
- 7,871,124
- Country
- CN
- Tail
- B-320Z
- Type
- A20N
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 25, 11:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 781A94 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 |
|---|---|---|---|
| DKH1353 | - | 14 | 2026-06-29 |
| DKH1365 | - | 12 | 2026-07-18 |
| DKH1366 | - | 9 | 2026-07-18 |
| DKH1575 | - | 8 | 2026-07-16 |
| DKH1355 | - | 6 | 2026-06-26 |
| DKH1562 | Juneyao Airlines | 4 | 2026-05-13 |
| DKH1356 | Juneyao Airlines | 4 | 2026-06-26 |
| DKH1354 | - | 4 | 2026-06-29 |
| DKH1602 | Juneyao Airlines | 3 | 2026-07-21 |
| DKH1601 | Juneyao Airlines | 3 | 2026-07-21 |
| DKH1576 | Juneyao Airlines | 3 | 2026-07-17 |
| DKH1561 | Juneyao Airlines | 3 | 2026-05-13 |
| DKH2117 | - | 2 | 2026-07-08 |
| DKH2010 | Juneyao Airlines | 2 | 2026-07-25 |
| DKH2009 | Juneyao Airlines | 2 | 2026-05-11 |
| DKH1563 | Juneyao Airlines | 2 | 2026-07-23 |
| DKH1308 | Juneyao Airlines | 2 | 2026-04-18 |
| DKH1307 | Juneyao Airlines | 2 | 2026-04-18 |
| DKH1291 | Juneyao Airlines | 2 | 2026-04-17 |
| DKH1271 | - | 2 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | DKH2010 | SYX → WUX | Jul 25, 07:35 UTC | Jul 25, 11:00 UTC | 3h 25m |
| 2026-07-23 | DKH1564 | KUL → WUX | Jul 23, 20:45 UTC | Jul 24, 01:05 UTC | 4h 20m |
| 2026-07-23 | DKH1563 | WUX → KUL | Jul 23, 18:55 UTC | Jul 23, 19:15 UTC | 20m |
| 2026-07-23 | DKH1563 | WUX → KUL | Jul 23, 06:25 UTC | Jul 23, 16:20 UTC | 9h 55m |
| 2026-07-21 | DKH1602 | SIN → PVG | Jul 21, 08:45 UTC | Jul 21, 13:05 UTC | 4h 20m |
| 2026-07-21 | DKH1601 | PVG → SIN | Jul 21, 02:25 UTC | Jul 21, 06:45 UTC | 4h 20m |
| 2026-07-18 | DKH1366 | - | Jul 18, 19:25 UTC | Jul 18, 20:10 UTC | 45m |
| 2026-07-18 | DKH1365 | - | Jul 18, 14:55 UTC | Jul 18, 15:10 UTC | 15m |
| 2026-07-17 | DKH1365 | - | Jul 17, 19:40 UTC | Jul 18, 12:20 UTC | 16h 41m |
| 2026-07-17 | DKH1576 | SIN → PVG | Jul 17, 16:24 UTC | Jul 18, 12:20 UTC | 19h 56m |
| 2026-07-16 | DKH1575 | - | Jul 16, 20:05 UTC | Jul 17, 14:15 UTC | 18h 10m |
| 2026-07-16 | DKH1575 | - | Jul 16, 17:05 UTC | Jul 17, 14:15 UTC | 21h 10m |
| 2026-07-16 | DKH1575 | - | Jul 16, 16:44 UTC | Jul 17, 14:15 UTC | 21h 30m |
| 2026-07-16 | DKH1575 | - | Jul 16, 14:00 UTC | Jul 16, 14:25 UTC | 25m |
| 2026-07-15 | DKH1575 | - | Jul 15, 23:35 UTC | Jul 16, 11:25 UTC | 11h 50m |
| 2026-07-15 | DKH2118 | - | Jul 15, 16:35 UTC | Jul 15, 16:45 UTC | 10m |
| 2026-07-14 | DKH1602 | - | Jul 14, 08:55 UTC | Jul 14, 13:05 UTC | 4h 10m |
| 2026-07-13 | DKH1601 | - | Jul 13, 13:00 UTC | Jul 14, 06:55 UTC | 17h 55m |
| 2026-07-13 | DKH1602 | - | Jul 13, 09:40 UTC | Jul 14, 06:55 UTC | 21h 15m |
| 2026-07-13 | DKH1601 | - | Jul 13, 03:40 UTC | Jul 13, 07:55 UTC | 4h 15m |
| 2026-07-10 | DKH1576 | - | Jul 10, 16:30 UTC | Jul 10, 20:25 UTC | 3h 55m |
| 2026-07-10 | DKH1575 | - | Jul 10, 13:30 UTC | Jul 10, 13:55 UTC | 25m |
| 2026-07-10 | DKH1271 | - | Jul 10, 00:50 UTC | Jul 10, 10:45 UTC | 9h 55m |
| 2026-07-09 | DKH1271 | - | Jul 9, 13:15 UTC | Jul 10, 10:45 UTC | 21h 30m |
| 2026-07-08 | DKH2117 | - | Jul 8, 23:15 UTC | Jul 8, 23:30 UTC | 15m |
| 2026-07-08 | DKH1946 | - | Jul 8, 18:40 UTC | Jul 8, 18:50 UTC | 10m |
| 2026-07-07 | DKH1576 | - | Jul 7, 16:10 UTC | Jul 8, 05:25 UTC | 13h 15m |
| 2026-07-07 | DKH1575 | - | Jul 7, 10:50 UTC | Jul 7, 14:15 UTC | 3h 25m |
| 2026-07-06 | DKH1575 | - | Jul 6, 15:50 UTC | Jul 7, 14:15 UTC | 22h 25m |
| 2026-07-05 | DKH1945 | - | Jul 5, 23:10 UTC | Jul 6, 12:50 UTC | 13h 40m |
| 2026-07-04 | DKH2086 | - | Jul 4, 03:25 UTC | Jul 4, 03:35 UTC | 10m |
| 2026-06-30 | DKH1366 | - | Jun 30, 19:05 UTC | Jun 30, 20:05 UTC | 1h 0m |
| 2026-06-30 | DKH1366 | - | Jun 30, 16:00 UTC | Jun 30, 16:10 UTC | 10m |
| 2026-06-30 | DKH1365 | - | Jun 30, 14:30 UTC | Jun 30, 14:45 UTC | 15m |
| 2026-06-29 | DKH1365 | - | Jun 29, 17:05 UTC | Jun 30, 11:10 UTC | 18h 6m |
| 2026-06-29 | DKH1354 | - | Jun 29, 16:35 UTC | Jun 30, 11:10 UTC | 18h 36m |
| 2026-06-29 | DKH1353 | - | Jun 29, 10:59 UTC | Jun 29, 15:09 UTC | 4h 10m |
| 2026-06-27 | DKH1366 | - | Jun 27, 19:15 UTC | Jun 27, 20:14 UTC | 1h 0m |
| 2026-06-27 | DKH1366 | - | Jun 27, 16:10 UTC | Jun 27, 16:20 UTC | 10m |
| 2026-06-27 | DKH1365 | - | Jun 27, 14:20 UTC | Jun 27, 14:35 UTC | 15m |
| 2026-06-27 | DKH1365 | - | Jun 27, 10:29 UTC | Jun 27, 11:39 UTC | 1h 10m |
| 2026-06-26 | DKH1365 | - | Jun 26, 13:49 UTC | Jun 27, 11:39 UTC | 21h 50m |
| 2026-06-26 | DKH1356 | DPS → PVG | Jun 26, 11:24 UTC | Jun 27, 10:54 UTC | 23h 30m |
| 2026-06-26 | DKH1355 | - | Jun 26, 02:34 UTC | Jun 26, 14:09 UTC | 11h 35m |
| 2026-06-25 | DKH1355 | - | Jun 25, 13:20 UTC | Jun 26, 12:10 UTC | 22h 50m |
| 2026-06-25 | DKH1355 | - | Jun 25, 11:04 UTC | Jun 26, 05:50 UTC | 18h 45m |
| 2026-06-25 | DKH1355 | - | Jun 25, 10:45 UTC | Jun 26, 05:50 UTC | 19h 5m |
| 2026-06-25 | DKH1355 | - | Jun 25, 05:09 UTC | Jun 26, 03:39 UTC | 22h 30m |
| 2026-06-24 | DKH1356 | DPS → PVG | Jun 24, 20:30 UTC | Jun 25, 13:35 UTC | 17h 5m |
| 2026-06-24 | DKH1356 | DPS → PVG | Jun 24, 17:20 UTC | Jun 25, 13:35 UTC | 20h 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-320Z page for operator, model, and routing details .