sensors Mode-S transponder
782105
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32HD · AIRBUS A-320neo
- Hex
- 782105
- Octal
- 36020405
- Decimal
- 7,872,773
- Country
- CN
- Tail
- B-32HD
- Type
- A20N
- Flights observed
- 106
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 782105 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DKH1365 | - | 49 | 2026-07-12 |
| DKH1366 | - | 17 | 2026-07-04 |
| DKH2009 | Juneyao Airlines | 5 | 2026-05-19 |
| DKH1354 | Juneyao Airlines | 5 | 2026-04-14 |
| DKH1353 | Juneyao Airlines | 5 | 2026-04-14 |
| DKH1562 | Juneyao Airlines | 3 | 2026-05-20 |
| DKH1329 | Juneyao Airlines | 3 | 2026-06-27 |
| DKH1308 | - | 3 | 2026-06-15 |
| DKH1129 | - | 3 | 2026-07-09 |
| DKH1561 | Juneyao Airlines | 2 | 2026-05-20 |
| DKH1330 | - | 2 | 2026-06-27 |
| DKH1307 | - | 2 | 2026-06-15 |
| DKH1062 | Juneyao Airlines | 2 | 2026-06-03 |
| DKH1327 | Juneyao Airlines | 1 | 2026-05-13 |
| DKH1271 | Juneyao Airlines | 1 | 2026-06-11 |
| DKH1262 | - | 1 | 2026-07-04 |
| DKH1192 | Juneyao Airlines | 1 | 2026-05-20 |
| DKH1160 | Juneyao Airlines | 1 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | DKH1365 | - | Jul 12, 10:20 UTC | Jul 12, 20:30 UTC | 10h 10m |
| 2026-07-09 | DKH1129 | - | Jul 9, 07:20 UTC | Jul 9, 11:10 UTC | 3h 50m |
| 2026-07-04 | DKH1262 | - | Jul 4, 21:00 UTC | Jul 5, 13:35 UTC | 16h 35m |
| 2026-07-04 | DKH1366 | - | Jul 4, 17:50 UTC | Jul 4, 18:00 UTC | 10m |
| 2026-07-04 | DKH1365 | - | Jul 4, 16:35 UTC | Jul 4, 16:45 UTC | 10m |
| 2026-07-04 | DKH1365 | - | Jul 4, 13:35 UTC | Jul 4, 14:20 UTC | 45m |
| 2026-06-27 | DKH1330 | - | Jun 27, 18:24 UTC | Jun 28, 03:50 UTC | 9h 25m |
| 2026-06-27 | DKH1329 | PVG → HAN | Jun 27, 16:20 UTC | Jun 27, 16:44 UTC | 25m |
| 2026-06-20 | DKH1129 | - | Jun 20, 19:19 UTC | Jun 21, 11:20 UTC | 16h 0m |
| 2026-06-20 | DKH1366 | - | Jun 20, 16:14 UTC | Jun 20, 16:24 UTC | 10m |
| 2026-06-20 | DKH1365 | - | Jun 20, 14:19 UTC | Jun 20, 14:35 UTC | 15m |
| 2026-06-20 | DKH1365 | - | Jun 20, 10:29 UTC | Jun 20, 11:40 UTC | 1h 10m |
| 2026-06-18 | DKH1129 | - | Jun 18, 06:55 UTC | Jun 18, 10:50 UTC | 3h 55m |
| 2026-06-15 | DKH1308 | - | Jun 15, 04:10 UTC | Jun 15, 05:20 UTC | 1h 10m |
| 2026-06-15 | DKH1307 | - | Jun 15, 02:15 UTC | Jun 15, 02:35 UTC | 20m |
| 2026-06-14 | DKH1307 | - | Jun 14, 19:05 UTC | Jun 15, 01:45 UTC | 6h 40m |
| 2026-06-13 | DKH1365 | - | Jun 13, 19:10 UTC | Jun 14, 11:35 UTC | 16h 26m |
| 2026-06-13 | DKH1366 | PEN → PVG | Jun 13, 16:05 UTC | Jun 13, 16:15 UTC | 10m |
| 2026-06-12 | DKH1365 | - | Jun 12, 19:05 UTC | Jun 13, 11:40 UTC | 16h 34m |
| 2026-06-12 | DKH1365 | - | Jun 12, 11:30 UTC | Jun 13, 11:10 UTC | 23h 39m |
| 2026-06-12 | DKH1365 | - | Jun 12, 10:25 UTC | Jun 12, 20:05 UTC | 9h 40m |
| 2026-06-11 | DKH1365 | - | Jun 11, 19:55 UTC | Jun 12, 19:15 UTC | 23h 20m |
| 2026-06-11 | DKH1365 | - | Jun 11, 19:00 UTC | Jun 12, 11:40 UTC | 16h 41m |
| 2026-06-11 | DKH1366 | PEN → PVG | Jun 11, 15:55 UTC | Jun 11, 16:05 UTC | 10m |
| 2026-06-11 | DKH1271 | SHA → HAK | Jun 11, 00:50 UTC | Jun 11, 11:30 UTC | 10h 40m |
| 2026-06-08 | DKH1366 | PEN → PVG | Jun 8, 19:10 UTC | Jun 8, 19:25 UTC | 15m |
| 2026-06-08 | DKH1365 | PVG → PEN | Jun 8, 14:30 UTC | Jun 8, 14:45 UTC | 15m |
| 2026-06-07 | DKH1365 | PVG → PEN | Jun 7, 19:10 UTC | Jun 8, 11:50 UTC | 16h 40m |
| 2026-06-07 | DKH1365 | PVG → PEN | Jun 7, 11:35 UTC | Jun 8, 11:10 UTC | 23h 35m |
| 2026-06-07 | DKH1365 | PVG → PEN | Jun 7, 10:30 UTC | Jun 7, 20:10 UTC | 9h 40m |
| 2026-06-06 | DKH1330 | HAN → PVG | Jun 6, 18:35 UTC | Jun 6, 18:55 UTC | 20m |
| 2026-06-06 | DKH1329 | PVG → HAN | Jun 6, 03:15 UTC | Jun 6, 16:55 UTC | 13h 40m |
| 2026-06-05 | DKH1329 | PVG → HAN | Jun 5, 19:20 UTC | Jun 6, 16:55 UTC | 21h 35m |
| 2026-06-05 | DKH1366 | PEN → PVG | Jun 5, 16:05 UTC | Jun 5, 16:15 UTC | 10m |
| 2026-06-05 | DKH1365 | PVG → PEN | Jun 5, 14:25 UTC | Jun 5, 14:40 UTC | 15m |
| 2026-06-05 | DKH1365 | PVG → PEN | Jun 5, 10:35 UTC | Jun 5, 11:35 UTC | 1h 0m |
| 2026-06-04 | DKH1365 | PVG → PEN | Jun 4, 13:25 UTC | Jun 5, 11:35 UTC | 22h 10m |
| 2026-06-03 | DKH1062 | YLX → PVG | Jun 3, 19:20 UTC | Jun 4, 14:35 UTC | 19h 15m |
| 2026-06-03 | DKH1366 | PEN → PVG | Jun 3, 19:10 UTC | Jun 4, 14:35 UTC | 19h 25m |
| 2026-06-03 | DKH1365 | PVG → PEN | Jun 3, 14:40 UTC | Jun 3, 14:55 UTC | 15m |
| 2026-06-02 | DKH1365 | PVG → PEN | Jun 2, 19:05 UTC | Jun 3, 11:50 UTC | 16h 45m |
| 2026-06-02 | DKH1365 | PVG → PEN | Jun 2, 11:45 UTC | Jun 3, 11:15 UTC | 23h 30m |
| 2026-06-02 | DKH1365 | PVG → PEN | Jun 2, 10:40 UTC | Jun 2, 20:10 UTC | 9h 30m |
| 2026-06-01 | DKH1365 | PVG → PEN | Jun 1, 19:20 UTC | Jun 2, 19:15 UTC | 23h 55m |
| 2026-06-01 | DKH1365 | PVG → PEN | Jun 1, 19:10 UTC | Jun 2, 11:50 UTC | 16h 40m |
| 2026-06-01 | DKH1365 | PVG → PEN | Jun 1, 11:40 UTC | Jun 2, 11:15 UTC | 23h 35m |
| 2026-06-01 | DKH1366 | PEN → PVG | Jun 1, 10:30 UTC | Jun 1, 20:20 UTC | 9h 50m |
| 2026-05-31 | DKH1160 | ZUH → SHA | May 31, 10:00 UTC | May 31, 10:15 UTC | 15m |
| 2026-05-30 | DKH1366 | PEN → PVG | May 30, 19:25 UTC | May 31, 00:45 UTC | 5h 20m |
| 2026-05-30 | DKH1366 | PEN → PVG | May 30, 16:15 UTC | May 30, 16:25 UTC | 10m |
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-32HD page for operator, model, and routing details .