sensors Mode-S transponder
780F0A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8317 · AIRBUS A-321
- Hex
- 780F0A
- Octal
- 36007412
- Decimal
- 7,868,170
- Country
- CN
- Tail
- B-8317
- Type
- A321
- Flights observed
- 63
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 780F0A 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 |
|---|---|---|---|
| DKH1066 | - | 10 | 2026-07-14 |
| DKH1888 | Juneyao Airlines | 6 | 2026-06-06 |
| DKH1887 | Juneyao Airlines | 6 | 2026-06-06 |
| DKH1178 | - | 5 | 2026-06-28 |
| DKH1884 | - | 3 | 2026-06-27 |
| DKH2048 | Juneyao Airlines | 2 | 2026-06-09 |
| DKH2047 | Juneyao Airlines | 2 | 2026-06-08 |
| DKH1885 | - | 2 | 2026-07-01 |
| DKH1883 | - | 2 | 2026-06-27 |
| DKH1790 | Juneyao Airlines | 2 | 2026-05-05 |
| DKH1789 | Juneyao Airlines | 2 | 2026-05-05 |
| DKH1328 | Juneyao Airlines | 2 | 2026-04-23 |
| DKH1291 | - | 2 | 2026-07-02 |
| DKH1156 | Juneyao Airlines | 2 | 2026-05-30 |
| DKH1155 | Juneyao Airlines | 2 | 2026-05-30 |
| DKH2050 | Juneyao Airlines | 1 | 2026-05-12 |
| DKH1886 | Juneyao Airlines | 1 | 2026-06-10 |
| DKH1866 | Juneyao Airlines | 1 | 2026-05-27 |
| DKH1392 | Juneyao Airlines | 1 | 2026-04-13 |
| DKH1391 | - | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | DKH1066 | - | Jul 14, 03:35 UTC | Jul 14, 04:00 UTC | 25m |
| 2026-07-10 | DKH1066 | - | Jul 10, 03:40 UTC | Jul 10, 03:55 UTC | 15m |
| 2026-07-09 | DKH1066 | - | Jul 9, 03:30 UTC | Jul 9, 03:50 UTC | 20m |
| 2026-07-08 | DKH1066 | - | Jul 8, 03:25 UTC | Jul 8, 03:50 UTC | 25m |
| 2026-07-05 | DKH1312 | - | Jul 5, 04:55 UTC | Jul 5, 05:45 UTC | 50m |
| 2026-07-05 | DKH1311 | - | Jul 5, 02:35 UTC | Jul 5, 03:25 UTC | 50m |
| 2026-07-02 | DKH1292 | - | Jul 2, 13:05 UTC | Jul 2, 13:20 UTC | 15m |
| 2026-07-02 | DKH1291 | - | Jul 2, 11:00 UTC | Jul 2, 11:20 UTC | 20m |
| 2026-07-02 | DKH1291 | - | Jul 2, 09:55 UTC | Jul 2, 10:25 UTC | 30m |
| 2026-07-01 | DKH1885 | - | Jul 1, 09:15 UTC | Jul 1, 09:35 UTC | 20m |
| 2026-06-28 | DKH1178 | - | Jun 28, 03:19 UTC | Jun 28, 08:05 UTC | 4h 45m |
| 2026-06-27 | DKH1884 | - | Jun 27, 06:15 UTC | Jun 27, 06:25 UTC | 10m |
| 2026-06-27 | DKH1883 | - | Jun 27, 04:00 UTC | Jun 27, 04:09 UTC | 10m |
| 2026-06-25 | DKH1066 | - | Jun 25, 03:04 UTC | Jun 25, 03:29 UTC | 25m |
| 2026-06-24 | DKH1066 | - | Jun 24, 03:04 UTC | Jun 24, 03:24 UTC | 20m |
| 2026-06-13 | DKH1066 | DAT → SHA | Jun 13, 03:10 UTC | Jun 13, 03:40 UTC | 30m |
| 2026-06-10 | DKH1886 | SZX → SHA | Jun 10, 11:40 UTC | Jun 10, 11:50 UTC | 10m |
| 2026-06-10 | DKH1885 | SHA → SZX | Jun 10, 09:45 UTC | Jun 10, 10:05 UTC | 20m |
| 2026-06-09 | DKH2048 | HAK → HUZ | Jun 9, 00:00 UTC | Jun 9, 00:15 UTC | 15m |
| 2026-06-08 | DKH2047 | HGH → HUZ | Jun 8, 15:45 UTC | Jun 8, 16:00 UTC | 15m |
| 2026-06-07 | DKH2048 | HAK → HUZ | Jun 7, 23:45 UTC | Jun 8, 00:00 UTC | 15m |
| 2026-06-07 | DKH2047 | HGH → HUZ | Jun 7, 14:10 UTC | Jun 7, 14:30 UTC | 20m |
| 2026-06-06 | DKH1888 | SZX → SHA | Jun 6, 17:05 UTC | Jun 6, 17:19 UTC | 15m |
| 2026-06-06 | DKH1887 | SHA → SZX | Jun 6, 15:30 UTC | Jun 6, 15:39 UTC | 10m |
| 2026-06-06 | DKH1178 | SYX → SHA | Jun 6, 06:55 UTC | Jun 6, 07:10 UTC | 15m |
| 2026-06-05 | DKH1066 | DAT → SHA | Jun 5, 03:05 UTC | Jun 5, 03:30 UTC | 25m |
| 2026-05-30 | DKH1156 | ZUH → PVG | May 30, 14:10 UTC | May 30, 14:20 UTC | 10m |
| 2026-05-30 | DKH1155 | PVG → ZUH | May 30, 11:55 UTC | May 30, 12:20 UTC | 25m |
| 2026-05-29 | DKH1888 | SZX → SHA | May 29, 16:25 UTC | May 29, 17:45 UTC | 1h 20m |
| 2026-05-29 | DKH1887 | SHA → SZX | May 29, 11:50 UTC | May 29, 13:30 UTC | 1h 40m |
| 2026-05-28 | DKH1066 | DAT → SHA | May 28, 03:10 UTC | May 28, 03:30 UTC | 20m |
| 2026-05-27 | DKH1866 | CAN → SHA | May 27, 14:15 UTC | May 27, 14:25 UTC | 10m |
| 2026-05-20 | DKH1066 | DAT → SHA | May 20, 03:15 UTC | May 20, 03:40 UTC | 25m |
| 2026-05-12 | DKH1160 | ZUH → SHA | May 12, 09:30 UTC | May 12, 09:45 UTC | 15m |
| 2026-05-12 | DKH2050 | ZUH → HGH | May 12, 02:45 UTC | May 12, 02:55 UTC | 10m |
| 2026-05-11 | DKH1156 | ZUH → PVG | May 11, 11:30 UTC | May 11, 11:45 UTC | 15m |
| 2026-05-11 | DKH1155 | PVG → ZUH | May 11, 10:00 UTC | May 11, 10:10 UTC | 10m |
| 2026-05-05 | DKH1790 | XMN → NKG | May 5, 12:45 UTC | May 5, 12:55 UTC | 10m |
| 2026-05-05 | DKH1789 | NKG → XMN | May 5, 10:50 UTC | May 5, 11:15 UTC | 25m |
| 2026-05-05 | DKH1884 | SZX → SHA | May 5, 05:40 UTC | May 5, 05:50 UTC | 10m |
| 2026-05-05 | DKH1883 | SHA → SZX | May 5, 03:55 UTC | May 5, 04:05 UTC | 10m |
| 2026-05-04 | DKH1790 | XMN → NKG | May 4, 12:50 UTC | May 4, 13:00 UTC | 10m |
| 2026-05-04 | DKH1789 | NKG → XMN | May 4, 10:50 UTC | May 4, 11:10 UTC | 20m |
| 2026-05-04 | DKH1884 | SZX → SHA | May 4, 05:40 UTC | May 4, 05:50 UTC | 10m |
| 2026-05-03 | DKH1888 | SZX → SHA | May 3, 14:40 UTC | May 3, 14:50 UTC | 10m |
| 2026-05-03 | DKH1887 | SHA → SZX | May 3, 13:05 UTC | May 3, 13:25 UTC | 20m |
| 2026-04-25 | DKH1308 | HKG → PVG | Apr 25, 04:10 UTC | Apr 25, 05:10 UTC | 1h 0m |
| 2026-04-24 | DKH1307 | PVG → HKG | Apr 24, 12:10 UTC | Apr 25, 02:35 UTC | 14h 25m |
| 2026-04-23 | DKH1328 | SGN → PVG | Apr 23, 22:25 UTC | Apr 24, 12:10 UTC | 13h 45m |
| 2026-04-23 | DKH1328 | SGN → PVG | Apr 23, 20:30 UTC | Apr 23, 20:40 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-8317 page for operator, model, and routing details .