sensors Mode-S transponder
780F9D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8540 · AIRBUS A-321
- Hex
- 780F9D
- Octal
- 36007635
- Decimal
- 7,868,317
- Country
- CN
- Tail
- B-8540
- Type
- A321
- Flights observed
- 84
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 780F9D 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 |
|---|---|---|---|
| DKH1914 | - | 14 | 2026-07-16 |
| DKH1913 | - | 10 | 2026-07-02 |
| DKH2047 | Juneyao Airlines | 3 | 2026-05-24 |
| DKH1887 | Juneyao Airlines | 3 | 2026-06-05 |
| DKH1351 | Juneyao Airlines | 3 | 2026-05-12 |
| DKH1327 | Juneyao Airlines | 3 | 2026-05-06 |
| DKH1309 | Juneyao Airlines | 3 | 2026-05-08 |
| DKH1286 | - | 3 | 2026-07-15 |
| DKH1087 | Juneyao Airlines | 3 | 2026-06-03 |
| DKH2048 | Juneyao Airlines | 2 | 2026-05-19 |
| DKH1352 | Juneyao Airlines | 2 | 2026-05-05 |
| DKH1312 | - | 2 | 2026-07-18 |
| DKH1311 | - | 2 | 2026-07-18 |
| DKH1307 | Juneyao Airlines | 2 | 2026-04-21 |
| DKH1291 | Juneyao Airlines | 2 | 2026-04-21 |
| DKH1233 | - | 2 | 2026-06-25 |
| DKH1160 | Juneyao Airlines | 2 | 2026-05-15 |
| DKH1159 | Juneyao Airlines | 2 | 2026-05-15 |
| DKH2372 | Juneyao Airlines | 1 | 2026-05-15 |
| DKH2371 | Juneyao Airlines | 1 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | DKH1312 | - | Jul 18, 05:00 UTC | Jul 18, 05:45 UTC | 45m |
| 2026-07-18 | DKH1311 | - | Jul 18, 03:05 UTC | Jul 18, 03:55 UTC | 50m |
| 2026-07-16 | DKH1914 | - | Jul 16, 14:25 UTC | Jul 17, 01:20 UTC | 10h 55m |
| 2026-07-16 | DKH1914 | - | Jul 16, 04:25 UTC | Jul 17, 01:20 UTC | 20h 55m |
| 2026-07-15 | DKH1286 | - | Jul 15, 14:45 UTC | Jul 16, 04:40 UTC | 13h 55m |
| 2026-07-15 | DKH1914 | - | Jul 15, 00:45 UTC | Jul 15, 15:10 UTC | 14h 25m |
| 2026-07-14 | DKH1914 | - | Jul 14, 16:05 UTC | Jul 15, 15:10 UTC | 23h 4m |
| 2026-07-13 | DKH1066 | - | Jul 13, 03:10 UTC | Jul 13, 03:30 UTC | 20m |
| 2026-07-07 | DKH1914 | - | Jul 7, 00:40 UTC | Jul 7, 16:30 UTC | 15h 50m |
| 2026-07-06 | DKH1914 | - | Jul 6, 04:10 UTC | Jul 7, 00:50 UTC | 20h 40m |
| 2026-07-04 | DKH1914 | - | Jul 4, 15:20 UTC | Jul 5, 00:50 UTC | 9h 30m |
| 2026-07-03 | DKH1286 | - | Jul 3, 00:35 UTC | Jul 3, 18:45 UTC | 18h 10m |
| 2026-07-02 | DKH1913 | - | Jul 2, 15:25 UTC | Jul 3, 00:45 UTC | 9h 20m |
| 2026-07-02 | DKH1913 | - | Jul 2, 04:10 UTC | Jul 3, 00:45 UTC | 20h 35m |
| 2026-06-30 | DKH1914 | - | Jun 30, 16:15 UTC | Jul 1, 01:20 UTC | 9h 5m |
| 2026-06-27 | DKH1914 | - | Jun 27, 15:14 UTC | Jun 28, 01:10 UTC | 9h 55m |
| 2026-06-26 | DKH1286 | - | Jun 26, 14:55 UTC | Jun 27, 05:29 UTC | 14h 35m |
| 2026-06-25 | DKH1913 | - | Jun 25, 14:24 UTC | Jun 26, 00:35 UTC | 10h 10m |
| 2026-06-25 | DKH1233 | - | Jun 25, 08:45 UTC | Jun 25, 09:14 UTC | 30m |
| 2026-06-25 | DKH1233 | - | Jun 25, 07:45 UTC | Jun 25, 08:14 UTC | 30m |
| 2026-06-23 | DKH1188 | - | Jun 23, 13:05 UTC | Jun 23, 13:19 UTC | 15m |
| 2026-06-18 | DKH1914 | - | Jun 18, 00:25 UTC | Jun 18, 16:10 UTC | 15h 45m |
| 2026-06-17 | DKH1913 | HUZ → HGH | Jun 17, 09:25 UTC | Jun 18, 01:05 UTC | 15h 40m |
| 2026-06-14 | DKH1128 | SYX → SHA | Jun 14, 10:05 UTC | Jun 14, 13:45 UTC | 3h 40m |
| 2026-06-12 | DKH1886 | SZX → SHA | Jun 12, 10:15 UTC | Jun 12, 10:25 UTC | 10m |
| 2026-06-09 | DKH1882 | SZX → SHA | Jun 9, 03:25 UTC | Jun 9, 03:35 UTC | 10m |
| 2026-06-09 | DKH1881 | SHA → SZX | Jun 9, 01:30 UTC | Jun 9, 01:50 UTC | 20m |
| 2026-06-08 | DKH1506 | KIX → PVG | Jun 8, 04:10 UTC | Jun 8, 05:00 UTC | 50m |
| 2026-06-07 | DKH1505 | PVG → KIX | Jun 7, 11:55 UTC | Jun 8, 02:30 UTC | 14h 35m |
| 2026-06-06 | DKH1112 | - | Jun 6, 13:39 UTC | Jun 7, 11:55 UTC | 22h 15m |
| 2026-06-06 | DKH1890 | SZX → SHA | Jun 6, 00:00 UTC | Jun 6, 00:10 UTC | 10m |
| 2026-06-05 | DKH1887 | SHA → SZX | Jun 5, 13:05 UTC | Jun 5, 13:20 UTC | 15m |
| 2026-06-03 | DKH1087 | PVG → HAK | Jun 3, 04:00 UTC | Jun 3, 14:35 UTC | 10h 35m |
| 2026-06-03 | DKH1308 | HKG → PVG | Jun 3, 02:00 UTC | Jun 3, 02:15 UTC | 15m |
| 2026-06-02 | DKH1156 | ZUH → PVG | Jun 2, 13:45 UTC | Jun 2, 13:55 UTC | 10m |
| 2026-06-02 | DKH1155 | PVG → ZUH | Jun 2, 11:05 UTC | Jun 2, 11:30 UTC | 25m |
| 2026-06-01 | DKH1087 | PVG → HAK | Jun 1, 03:55 UTC | Jun 1, 12:45 UTC | 8h 50m |
| 2026-05-30 | DKH1184 | SHE → PVG | May 30, 04:10 UTC | May 30, 18:55 UTC | 14h 45m |
| 2026-05-28 | DKH1914 | HRB → HGH | May 28, 14:20 UTC | May 29, 00:35 UTC | 10h 15m |
| 2026-05-28 | DKH1914 | HRB → HGH | May 28, 04:05 UTC | May 29, 00:35 UTC | 20h 30m |
| 2026-05-26 | DKH1913 | HUZ → HGH | May 26, 13:54 UTC | May 27, 00:34 UTC | 10h 40m |
| 2026-05-24 | DKH2047 | HGH → HUZ | May 24, 15:45 UTC | May 24, 16:05 UTC | 20m |
| 2026-05-19 | DKH2048 | HAK → HUZ | May 19, 00:20 UTC | May 19, 00:35 UTC | 15m |
| 2026-05-18 | DKH2047 | HGH → HUZ | May 18, 14:45 UTC | May 18, 15:05 UTC | 20m |
| 2026-05-17 | DKH2048 | HAK → HUZ | May 17, 00:05 UTC | May 17, 00:25 UTC | 20m |
| 2026-05-16 | DKH2047 | HGH → HUZ | May 16, 14:16 UTC | May 16, 14:31 UTC | 15m |
| 2026-05-15 | DKH1160 | ZUH → SHA | May 15, 12:30 UTC | May 15, 12:45 UTC | 15m |
| 2026-05-15 | DKH2371 | NKG → ZUH | May 15, 10:45 UTC | May 15, 11:15 UTC | 30m |
| 2026-05-15 | DKH2372 | ZUH → NKG | May 15, 05:25 UTC | May 15, 05:35 UTC | 10m |
| 2026-05-15 | DKH1159 | SHA → ZUH | May 15, 01:15 UTC | May 15, 01: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-8540 page for operator, model, and routing details .