sensors Mode-S transponder
780F09
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8315 · AIRBUS A-321
- Hex
- 780F09
- Octal
- 36007411
- Decimal
- 7,868,169
- Country
- CN
- Tail
- B-8315
- Type
- A321
- Flights observed
- 82
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 780F09 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 |
|---|---|---|---|
| DKH1889 | Juneyao Airlines | 6 | 2026-06-13 |
| DKH1890 | Juneyao Airlines | 5 | 2026-05-26 |
| DKH2047 | - | 4 | 2026-06-25 |
| DKH1352 | Juneyao Airlines | 4 | 2026-05-06 |
| DKH1882 | - | 3 | 2026-07-14 |
| DKH1881 | - | 3 | 2026-07-14 |
| DKH1291 | - | 3 | 2026-07-01 |
| DKH1160 | Juneyao Airlines | 3 | 2026-05-24 |
| DKH1159 | Juneyao Airlines | 3 | 2026-05-24 |
| DKH1155 | Juneyao Airlines | 3 | 2026-05-23 |
| DKH1129 | Juneyao Airlines | 3 | 2026-05-25 |
| DKH2049 | Juneyao Airlines | 2 | 2026-04-28 |
| DKH1886 | - | 2 | 2026-07-14 |
| DKH1885 | - | 2 | 2026-07-14 |
| DKH1351 | Juneyao Airlines | 2 | 2026-05-06 |
| DKH1312 | - | 2 | 2026-06-27 |
| DKH1311 | - | 2 | 2026-06-30 |
| DKH1308 | Juneyao Airlines | 2 | 2026-04-13 |
| DKH1292 | - | 2 | 2026-06-27 |
| DKH1156 | Juneyao Airlines | 2 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | DKH1886 | - | Jul 14, 10:35 UTC | Jul 14, 11:30 UTC | 55m |
| 2026-07-14 | DKH1885 | - | Jul 14, 08:25 UTC | Jul 14, 08:45 UTC | 20m |
| 2026-07-14 | DKH1882 | - | Jul 14, 03:20 UTC | Jul 14, 03:30 UTC | 10m |
| 2026-07-14 | DKH1881 | - | Jul 14, 01:05 UTC | Jul 14, 01:50 UTC | 45m |
| 2026-07-11 | DKH1886 | - | Jul 11, 11:15 UTC | Jul 11, 11:25 UTC | 10m |
| 2026-07-11 | DKH1885 | - | Jul 11, 09:40 UTC | Jul 11, 10:00 UTC | 20m |
| 2026-07-11 | DKH1882 | - | Jul 11, 03:30 UTC | Jul 11, 03:40 UTC | 10m |
| 2026-07-11 | DKH1881 | - | Jul 11, 01:25 UTC | Jul 11, 01:50 UTC | 25m |
| 2026-07-10 | DKH1127 | - | Jul 10, 10:30 UTC | Jul 10, 14:05 UTC | 3h 35m |
| 2026-07-09 | DKH1128 | - | Jul 9, 15:00 UTC | Jul 10, 14:05 UTC | 23h 5m |
| 2026-07-09 | DKH1127 | - | Jul 9, 10:15 UTC | Jul 9, 15:10 UTC | 4h 55m |
| 2026-07-06 | DKH1188 | - | Jul 6, 13:30 UTC | Jul 6, 13:45 UTC | 15m |
| 2026-07-02 | DKH1310 | - | Jul 2, 04:35 UTC | Jul 2, 05:05 UTC | 30m |
| 2026-07-01 | DKH1309 | HKG → TPE | Jul 1, 13:15 UTC | Jul 2, 02:35 UTC | 13h 20m |
| 2026-07-01 | DKH1291 | - | Jul 1, 05:05 UTC | Jul 1, 11:25 UTC | 6h 20m |
| 2026-06-30 | DKH1311 | - | Jun 30, 18:40 UTC | Jul 1, 03:50 UTC | 9h 10m |
| 2026-06-30 | DKH1329 | PVG → HAN | Jun 30, 16:45 UTC | Jun 30, 17:10 UTC | 25m |
| 2026-06-29 | DKH1883 | - | Jun 29, 03:44 UTC | Jun 29, 04:00 UTC | 15m |
| 2026-06-27 | DKH1292 | - | Jun 27, 13:15 UTC | Jun 27, 14:20 UTC | 1h 5m |
| 2026-06-27 | DKH1291 | - | Jun 27, 04:54 UTC | Jun 27, 11:30 UTC | 6h 35m |
| 2026-06-27 | DKH1312 | - | Jun 27, 02:29 UTC | Jun 27, 03:25 UTC | 55m |
| 2026-06-25 | DKH2048 | - | Jun 25, 23:39 UTC | Jun 25, 23:55 UTC | 15m |
| 2026-06-25 | DKH2047 | - | Jun 25, 15:59 UTC | Jun 25, 16:20 UTC | 20m |
| 2026-06-15 | DKH2047 | - | Jun 15, 14:20 UTC | Jun 15, 14:40 UTC | 20m |
| 2026-06-15 | DKH2047 | - | Jun 15, 12:05 UTC | Jun 15, 12:45 UTC | 40m |
| 2026-06-13 | DKH1889 | SHA → SZX | Jun 13, 16:50 UTC | Jun 13, 17:05 UTC | 15m |
| 2026-06-13 | DKH1130 | SYX → SHA | Jun 13, 06:30 UTC | Jun 13, 10:40 UTC | 4h 10m |
| 2026-06-12 | DKH1882 | - | Jun 12, 03:40 UTC | Jun 12, 03:55 UTC | 15m |
| 2026-06-12 | DKH1881 | SHA → SZX | Jun 12, 01:35 UTC | Jun 12, 01:55 UTC | 20m |
| 2026-05-27 | DKH1390 | NGO → PVG | May 27, 12:05 UTC | May 27, 13:00 UTC | 55m |
| 2026-05-27 | DKH1389 | PVG → NGO | May 27, 09:05 UTC | May 27, 09:55 UTC | 50m |
| 2026-05-26 | DKH1890 | SZX → SHA | May 26, 00:00 UTC | May 26, 00:09 UTC | 10m |
| 2026-05-25 | DKH1889 | SHA → SZX | May 25, 15:10 UTC | May 25, 15:35 UTC | 25m |
| 2026-05-25 | DKH1129 | SHA → SYX | May 25, 06:25 UTC | May 25, 10:00 UTC | 3h 35m |
| 2026-05-24 | DKH1160 | ZUH → SHA | May 24, 07:55 UTC | May 24, 08:10 UTC | 15m |
| 2026-05-24 | DKH1159 | SHA → ZUH | May 24, 03:45 UTC | May 24, 04:05 UTC | 20m |
| 2026-05-23 | DKH1156 | ZUH → PVG | May 23, 11:55 UTC | May 23, 12:05 UTC | 10m |
| 2026-05-23 | DKH1155 | PVG → ZUH | May 23, 09:55 UTC | May 23, 10:20 UTC | 25m |
| 2026-05-15 | DKH1890 | SZX → SHA | May 15, 23:55 UTC | May 16, 00:05 UTC | 10m |
| 2026-05-15 | DKH1889 | SHA → SZX | May 15, 17:15 UTC | May 15, 17:25 UTC | 10m |
| 2026-05-09 | DKH1890 | SZX → SHA | May 9, 23:50 UTC | May 10, 00:05 UTC | 15m |
| 2026-05-09 | DKH1889 | SHA → SZX | May 9, 15:10 UTC | May 9, 15:25 UTC | 15m |
| 2026-05-09 | DKH1129 | SHA → SYX | May 9, 06:25 UTC | May 9, 11:10 UTC | 4h 45m |
| 2026-05-06 | DKH1352 | BKK → PVG | May 6, 18:45 UTC | May 6, 20:55 UTC | 2h 10m |
| 2026-05-06 | DKH1351 | PVG → BKK | May 6, 03:50 UTC | May 6, 16:45 UTC | 12h 55m |
| 2026-05-06 | DKH2339 | - | May 6, 01:01 UTC | May 6, 01:20 UTC | 20m |
| 2026-05-04 | DKH2047 | HGH → HUZ | May 4, 14:35 UTC | May 4, 14:50 UTC | 15m |
| 2026-05-03 | DKH1292 | HKG → PVG | May 3, 13:30 UTC | May 3, 14:40 UTC | 1h 10m |
| 2026-05-03 | DKH1291 | PVG → HKG | May 3, 11:20 UTC | May 3, 11:35 UTC | 15m |
| 2026-05-03 | DKH1312 | KHH → PVG | May 3, 05:40 UTC | May 3, 10:20 UTC | 4h 40m |
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-8315 page for operator, model, and routing details .