sensors Mode-S transponder
78083D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6860 · AIRBUS A-320
- Hex
- 78083D
- Octal
- 36004075
- Decimal
- 7,866,429
- Country
- CN
- Tail
- B-6860
- Type
- A320
- Flights observed
- 36
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 78083D 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 |
|---|---|---|---|
| DKH1945 | - | 4 | 2026-07-04 |
| DKH1620 | Juneyao Airlines | 4 | 2026-06-06 |
| DKH1291 | - | 4 | 2026-07-06 |
| DKH1946 | - | 3 | 2026-07-03 |
| DKH1292 | - | 3 | 2026-07-06 |
| DKH2117 | - | 2 | 2026-07-05 |
| DKH1751 | Juneyao Airlines | 2 | 2026-06-10 |
| DKH1739 | Juneyao Airlines | 2 | 2026-05-06 |
| DKH1327 | - | 2 | 2026-07-05 |
| DKH2210 | - | 1 | 2026-06-18 |
| DKH211R | - | 1 | 2026-07-05 |
| DKH2118 | - | 1 | 2026-07-02 |
| DKH1752 | Juneyao Airlines | 1 | 2026-05-27 |
| DKH1740 | Juneyao Airlines | 1 | 2026-04-16 |
| DKH1619 | Juneyao Airlines | 1 | 2026-04-18 |
| DKH1066 | - | 1 | 2026-07-12 |
| DKH1062 | - | 1 | 2026-07-14 |
| DKH1035 | - | 1 | 2026-06-10 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | DKH1062 | - | Jul 14, 14:50 UTC | Jul 14, 15:05 UTC | 15m |
| 2026-07-12 | DKH1066 | - | Jul 12, 05:50 UTC | Jul 12, 06:15 UTC | 25m |
| 2026-07-06 | DKH1292 | - | Jul 6, 17:15 UTC | Jul 6, 18:40 UTC | 1h 25m |
| 2026-07-06 | DKH1291 | - | Jul 6, 14:55 UTC | Jul 6, 15:45 UTC | 50m |
| 2026-07-05 | DKH1291 | - | Jul 5, 20:00 UTC | Jul 6, 11:30 UTC | 15h 30m |
| 2026-07-05 | DKH1327 | - | Jul 5, 13:50 UTC | Jul 6, 11:00 UTC | 21h 10m |
| 2026-07-05 | DKH2117 | - | Jul 5, 04:40 UTC | Jul 5, 05:00 UTC | 20m |
| 2026-07-05 | DKH211R | - | Jul 5, 00:35 UTC | Jul 5, 00:50 UTC | 15m |
| 2026-07-04 | DKH1945 | - | Jul 4, 00:25 UTC | Jul 4, 01:25 UTC | 1h 0m |
| 2026-07-03 | DKH1946 | - | Jul 3, 21:55 UTC | Jul 3, 22:10 UTC | 15m |
| 2026-07-02 | DKH2117 | - | Jul 2, 23:10 UTC | Jul 3, 00:10 UTC | 1h 0m |
| 2026-07-02 | DKH2118 | - | Jul 2, 17:45 UTC | Jul 2, 18:00 UTC | 15m |
| 2026-06-26 | DKH1945 | - | Jun 26, 23:09 UTC | Jun 27, 11:59 UTC | 12h 50m |
| 2026-06-26 | DKH1946 | - | Jun 26, 17:40 UTC | Jun 26, 17:50 UTC | 10m |
| 2026-06-24 | DKH1945 | - | Jun 24, 23:04 UTC | Jun 25, 00:09 UTC | 1h 5m |
| 2026-06-22 | DKH1292 | - | Jun 22, 13:29 UTC | Jun 22, 14:55 UTC | 1h 25m |
| 2026-06-22 | DKH1291 | - | Jun 22, 03:40 UTC | Jun 22, 11:39 UTC | 8h 0m |
| 2026-06-20 | DKH1327 | PVG → SGN | Jun 20, 13:49 UTC | Jun 21, 03:25 UTC | 13h 35m |
| 2026-06-18 | DKH2210 | - | Jun 18, 14:30 UTC | Jun 18, 15:15 UTC | 45m |
| 2026-06-14 | DKH1292 | HKG → PVG | Jun 14, 13:25 UTC | Jun 14, 14:40 UTC | 1h 15m |
| 2026-06-14 | DKH1291 | PVG → HKG | Jun 14, 09:45 UTC | Jun 14, 11:15 UTC | 1h 30m |
| 2026-06-10 | DKH1035 | - | Jun 10, 23:20 UTC | Jun 11, 11:05 UTC | 11h 45m |
| 2026-06-10 | DKH1751 | NKG → SZX | Jun 10, 15:10 UTC | Jun 10, 16:05 UTC | 55m |
| 2026-06-06 | DKH1620 | KIX → NKG | Jun 6, 07:15 UTC | Jun 6, 08:05 UTC | 50m |
| 2026-06-06 | DKH1620 | KIX → NKG | Jun 6, 04:40 UTC | Jun 6, 05:35 UTC | 55m |
| 2026-05-27 | DKH1752 | SZX → NKG | May 27, 23:15 UTC | May 27, 23:25 UTC | 10m |
| 2026-05-27 | DKH1946 | - | May 27, 16:15 UTC | May 27, 16:25 UTC | 10m |
| 2026-05-27 | - | - | May 27, 05:04 UTC | May 27, 05:35 UTC | 30m |
| 2026-05-23 | DKH1945 | - | May 23, 23:05 UTC | May 23, 23:25 UTC | 20m |
| 2026-05-23 | DKH1751 | NKG → SZX | May 23, 15:15 UTC | May 23, 16:05 UTC | 50m |
| 2026-05-06 | DKH1739 | NKG → SYX | May 6, 10:15 UTC | May 6, 14:40 UTC | 4h 25m |
| 2026-04-18 | DKH1620 | KIX → NKG | Apr 18, 07:25 UTC | Apr 18, 07:55 UTC | 30m |
| 2026-04-18 | DKH1620 | KIX → NKG | Apr 18, 07:10 UTC | Apr 18, 07:20 UTC | 10m |
| 2026-04-18 | DKH1619 | NKG → KIX | Apr 18, 04:55 UTC | Apr 18, 05:20 UTC | 25m |
| 2026-04-16 | DKH1740 | SYX → NKG | Apr 16, 09:39 UTC | Apr 16, 09:54 UTC | 15m |
| 2026-04-16 | DKH1739 | NKG → SYX | Apr 16, 05:54 UTC | Apr 16, 06:20 UTC | 25m |
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-6860 page for operator, model, and routing details .