sensors Mode-S transponder
780978
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6966 · AIRBUS A-320
- Hex
- 780978
- Octal
- 36004570
- Decimal
- 7,866,744
- Country
- CN
- Tail
- B-6966
- Type
- A320
- Flights observed
- 49
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 780978 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 |
|---|---|---|---|
| DKH1292 | - | 7 | 2026-06-20 |
| DKH1291 | - | 5 | 2026-06-20 |
| DKH1035 | - | 5 | 2026-07-08 |
| DKH1945 | - | 3 | 2026-07-01 |
| DKH1329 | Juneyao Airlines | 3 | 2026-06-25 |
| DKH1307 | Juneyao Airlines | 3 | 2026-05-24 |
| DKH1180 | Juneyao Airlines | 3 | 2026-06-11 |
| DKH1062 | - | 3 | 2026-06-27 |
| DKH1946 | - | 2 | 2026-07-01 |
| DKH1330 | - | 2 | 2026-06-25 |
| DKH1308 | Juneyao Airlines | 2 | 2026-05-24 |
| DKH2117 | Juneyao Airlines | 1 | 2026-04-27 |
| DKH2068 | Juneyao Airlines | 1 | 2026-06-03 |
| DKH2048 | Juneyao Airlines | 1 | 2026-04-15 |
| DKH2047 | Juneyao Airlines | 1 | 2026-04-14 |
| DKH1792 | - | 1 | 2026-05-03 |
| DKH1782 | - | 1 | 2026-07-14 |
| DKH1781 | - | 1 | 2026-07-14 |
| DKH1282 | - | 1 | 2026-06-17 |
| DKH1192 | - | 1 | 2026-06-26 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | DKH1782 | - | Jul 14, 04:15 UTC | Jul 14, 04:30 UTC | 15m |
| 2026-07-14 | DKH1781 | - | Jul 14, 01:50 UTC | Jul 14, 02:05 UTC | 15m |
| 2026-07-08 | DKH1035 | - | Jul 8, 13:45 UTC | Jul 8, 14:00 UTC | 15m |
| 2026-07-03 | DKH1035 | - | Jul 3, 13:15 UTC | Jul 3, 13:30 UTC | 15m |
| 2026-07-02 | DKH1035 | - | Jul 2, 14:05 UTC | Jul 3, 13:30 UTC | 23h 25m |
| 2026-07-01 | DKH1945 | - | Jul 1, 23:10 UTC | Jul 2, 14:30 UTC | 15h 20m |
| 2026-07-01 | DKH1946 | - | Jul 1, 16:05 UTC | Jul 1, 16:15 UTC | 10m |
| 2026-06-28 | DKH1020 | - | Jun 28, 14:19 UTC | Jun 28, 14:39 UTC | 20m |
| 2026-06-27 | DKH1062 | - | Jun 27, 13:30 UTC | Jun 27, 13:44 UTC | 15m |
| 2026-06-26 | DKH1062 | - | Jun 26, 14:05 UTC | Jun 27, 13:44 UTC | 23h 40m |
| 2026-06-26 | DKH1192 | - | Jun 26, 13:49 UTC | Jun 26, 14:35 UTC | 45m |
| 2026-06-25 | DKH1330 | - | Jun 25, 19:24 UTC | Jun 26, 14:35 UTC | 19h 10m |
| 2026-06-25 | DKH1329 | PVG → HAN | Jun 25, 16:45 UTC | Jun 25, 18:00 UTC | 1h 15m |
| 2026-06-23 | DKH1035 | - | Jun 23, 11:40 UTC | Jun 23, 11:59 UTC | 20m |
| 2026-06-21 | DKH1035 | - | Jun 21, 11:30 UTC | Jun 21, 11:44 UTC | 15m |
| 2026-06-20 | DKH1292 | - | Jun 20, 14:05 UTC | Jun 21, 11:44 UTC | 21h 40m |
| 2026-06-20 | DKH1292 | - | Jun 20, 13:24 UTC | Jun 21, 11:44 UTC | 22h 20m |
| 2026-06-20 | DKH1291 | - | Jun 20, 00:39 UTC | Jun 20, 11:20 UTC | 10h 40m |
| 2026-06-17 | DKH1282 | - | Jun 17, 04:50 UTC | Jun 17, 05:25 UTC | 35m |
| 2026-06-13 | DKH1945 | - | Jun 13, 23:05 UTC | Jun 14, 00:05 UTC | 1h 0m |
| 2026-06-13 | DKH1025 | - | Jun 13, 00:25 UTC | Jun 13, 04:30 UTC | 4h 4m |
| 2026-06-11 | DKH1180 | HRB → PVG | Jun 11, 07:10 UTC | Jun 11, 07:30 UTC | 20m |
| 2026-06-03 | DKH2068 | DAT → HGH | Jun 3, 16:05 UTC | Jun 4, 08:00 UTC | 15h 55m |
| 2026-05-30 | DKH1330 | HAN → PVG | May 30, 18:35 UTC | May 30, 19:05 UTC | 30m |
| 2026-05-30 | DKH1329 | PVG → HAN | May 30, 16:25 UTC | May 30, 16:45 UTC | 20m |
| 2026-05-29 | DKH1292 | HKG → PVG | May 29, 13:10 UTC | May 29, 14:40 UTC | 1h 30m |
| 2026-05-28 | DKH1291 | PVG → HKG | May 28, 18:30 UTC | May 29, 11:10 UTC | 16h 40m |
| 2026-05-28 | DKH1329 | PVG → HAN | May 28, 15:40 UTC | May 28, 16:50 UTC | 1h 10m |
| 2026-05-24 | DKH1945 | - | May 24, 23:10 UTC | May 24, 23:30 UTC | 20m |
| 2026-05-24 | DKH1946 | - | May 24, 16:15 UTC | May 24, 16:25 UTC | 10m |
| 2026-05-24 | DKH1308 | HKG → PVG | May 24, 04:00 UTC | May 24, 05:40 UTC | 1h 40m |
| 2026-05-24 | DKH1307 | PVG → HKG | May 24, 01:50 UTC | May 24, 02:05 UTC | 15m |
| 2026-05-24 | DKH1307 | PVG → HKG | May 24, 00:45 UTC | May 24, 01:20 UTC | 35m |
| 2026-05-21 | DKH1292 | HKG → PVG | May 21, 14:00 UTC | May 21, 14:25 UTC | 25m |
| 2026-05-21 | DKH1292 | HKG → PVG | May 21, 13:10 UTC | May 21, 13:25 UTC | 15m |
| 2026-05-21 | DKH1291 | PVG → HKG | May 21, 05:30 UTC | May 21, 11:00 UTC | 5h 30m |
| 2026-05-18 | DKH1180 | HRB → PVG | May 18, 07:10 UTC | May 18, 07:45 UTC | 35m |
| 2026-05-14 | DKH1292 | HKG → PVG | May 14, 14:01 UTC | May 14, 14:40 UTC | 40m |
| 2026-05-14 | DKH1292 | HKG → PVG | May 14, 13:15 UTC | May 14, 13:30 UTC | 15m |
| 2026-05-14 | DKH1291 | PVG → HKG | May 14, 11:10 UTC | May 14, 11:30 UTC | 20m |
| 2026-05-14 | DKH1291 | PVG → HKG | May 14, 09:45 UTC | May 14, 10:40 UTC | 55m |
| 2026-05-03 | DKH1792 | - | May 3, 13:15 UTC | May 3, 13:30 UTC | 15m |
| 2026-04-27 | DKH2117 | SZX → JHG | Apr 27, 23:05 UTC | Apr 27, 23:25 UTC | 20m |
| 2026-04-27 | DKH1308 | HKG → PVG | Apr 27, 04:00 UTC | Apr 27, 05:10 UTC | 1h 10m |
| 2026-04-27 | DKH1307 | PVG → HKG | Apr 27, 00:55 UTC | Apr 27, 02:30 UTC | 1h 35m |
| 2026-04-23 | DKH1062 | YLX → PVG | Apr 23, 14:25 UTC | Apr 23, 15:05 UTC | 40m |
| 2026-04-15 | DKH2048 | HAK → HUZ | Apr 15, 00:20 UTC | Apr 15, 00:35 UTC | 15m |
| 2026-04-14 | DKH2047 | HGH → HUZ | Apr 14, 15:15 UTC | Apr 14, 15:35 UTC | 20m |
| 2026-04-13 | DKH1180 | HRB → PVG | Apr 13, 07:05 UTC | Apr 13, 07:50 UTC | 45m |
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-6966 page for operator, model, and routing details .