sensors Mode-S transponder
78124F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1002 · AIRBUS A-321
- Hex
- 78124F
- Octal
- 36011117
- Decimal
- 7,869,007
- Country
- CN
- Tail
- B-1002
- Type
- A321
- Flights observed
- 67
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 78124F 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 |
|---|---|---|---|
| DKH1351 | Juneyao Airlines | 5 | 2026-05-19 |
| DKH2047 | - | 4 | 2026-07-07 |
| DKH1887 | Juneyao Airlines | 4 | 2026-05-16 |
| DKH1329 | Juneyao Airlines | 4 | 2026-07-06 |
| DKH2048 | - | 3 | 2026-07-07 |
| DKH1890 | Juneyao Airlines | 3 | 2026-05-29 |
| DKH1888 | Juneyao Airlines | 3 | 2026-05-16 |
| DKH1330 | - | 3 | 2026-07-06 |
| DKH1327 | - | 3 | 2026-06-28 |
| DKH1127 | Juneyao Airlines | 3 | 2026-06-10 |
| DKH1889 | Juneyao Airlines | 2 | 2026-05-29 |
| DKH1352 | Juneyao Airlines | 2 | 2026-05-19 |
| DKH1310 | - | 2 | 2026-06-29 |
| DKH1309 | - | 2 | 2026-06-29 |
| DKH1155 | Juneyao Airlines | 2 | 2026-06-12 |
| DKH1128 | Juneyao Airlines | 2 | 2026-06-08 |
| DKH1886 | Juneyao Airlines | 1 | 2026-06-06 |
| DKH1884 | Juneyao Airlines | 1 | 2026-06-11 |
| DKH1883 | Juneyao Airlines | 1 | 2026-06-11 |
| DKH1856 | Juneyao Airlines | 1 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-07 | DKH2048 | - | Jul 7, 23:45 UTC | Jul 7, 23:55 UTC | 10m |
| 2026-07-07 | DKH2047 | - | Jul 7, 18:10 UTC | Jul 7, 18:25 UTC | 15m |
| 2026-07-06 | DKH1330 | - | Jul 6, 18:35 UTC | Jul 6, 18:45 UTC | 10m |
| 2026-07-06 | DKH1329 | PVG → HAN | Jul 6, 16:30 UTC | Jul 6, 16:40 UTC | 10m |
| 2026-06-29 | DKH1310 | - | Jun 29, 04:25 UTC | Jun 29, 04:50 UTC | 25m |
| 2026-06-29 | DKH1309 | - | Jun 29, 02:00 UTC | Jun 29, 02:20 UTC | 20m |
| 2026-06-28 | DKH1327 | - | Jun 28, 13:59 UTC | Jun 28, 20:45 UTC | 6h 45m |
| 2026-06-19 | DKH1310 | - | Jun 19, 04:39 UTC | Jun 20, 03:44 UTC | 23h 5m |
| 2026-06-18 | DKH1309 | - | Jun 18, 12:55 UTC | Jun 19, 02:24 UTC | 13h 29m |
| 2026-06-16 | DKH1330 | HAN → PVG | Jun 16, 18:29 UTC | Jun 16, 18:50 UTC | 20m |
| 2026-06-16 | DKH1329 | PVG → HAN | Jun 16, 16:20 UTC | Jun 16, 17:00 UTC | 40m |
| 2026-06-15 | DKH1329 | PVG → HAN | Jun 15, 19:50 UTC | Jun 16, 17:00 UTC | 21h 10m |
| 2026-06-15 | DKH1327 | PVG → SGN | Jun 15, 14:10 UTC | Jun 15, 20:04 UTC | 5h 55m |
| 2026-06-14 | DKH1282 | CGQ → PVG | Jun 14, 04:55 UTC | Jun 14, 05:30 UTC | 35m |
| 2026-06-12 | DKH1155 | PVG → ZUH | Jun 12, 09:25 UTC | Jun 12, 10:20 UTC | 55m |
| 2026-06-11 | DKH1790 | XMN → NKG | Jun 11, 14:10 UTC | Jun 11, 14:20 UTC | 10m |
| 2026-06-11 | DKH1789 | NKG → XMN | Jun 11, 12:05 UTC | Jun 11, 12:25 UTC | 20m |
| 2026-06-11 | DKH1884 | SZX → SHA | Jun 11, 05:50 UTC | Jun 11, 06:00 UTC | 10m |
| 2026-06-11 | DKH1883 | SHA → SZX | Jun 11, 03:40 UTC | Jun 11, 03:55 UTC | 15m |
| 2026-06-10 | DKH1127 | SHA → SYX | Jun 10, 09:55 UTC | Jun 11, 03:05 UTC | 17h 10m |
| 2026-06-09 | DKH1127 | SHA → SYX | Jun 9, 13:30 UTC | Jun 10, 10:10 UTC | 20h 40m |
| 2026-06-09 | DKH1127 | SHA → SYX | Jun 9, 10:05 UTC | Jun 9, 13:40 UTC | 3h 35m |
| 2026-06-08 | DKH1128 | SYX → SHA | Jun 8, 13:55 UTC | Jun 9, 13:40 UTC | 23h 45m |
| 2026-06-08 | DKH1128 | SYX → SHA | Jun 8, 10:10 UTC | Jun 8, 14:10 UTC | 4h 0m |
| 2026-06-06 | DKH1886 | SZX → SHA | Jun 6, 14:34 UTC | Jun 6, 14:45 UTC | 10m |
| 2026-06-06 | DKH1856 | CAN → SHA | Jun 6, 04:25 UTC | Jun 6, 12:14 UTC | 7h 50m |
| 2026-06-04 | DKH2048 | HAK → HUZ | Jun 4, 23:55 UTC | Jun 5, 00:10 UTC | 15m |
| 2026-06-04 | DKH2047 | HGH → HUZ | Jun 4, 14:10 UTC | Jun 4, 14:30 UTC | 20m |
| 2026-06-02 | DKH1327 | PVG → SGN | Jun 2, 14:10 UTC | Jun 2, 20:40 UTC | 6h 30m |
| 2026-05-31 | DKH1330 | HAN → PVG | May 31, 18:45 UTC | May 31, 19:05 UTC | 20m |
| 2026-05-31 | DKH1329 | PVG → HAN | May 31, 16:30 UTC | May 31, 16:50 UTC | 20m |
| 2026-05-29 | DKH1890 | SZX → SHA | May 29, 23:55 UTC | May 30, 00:05 UTC | 10m |
| 2026-05-29 | DKH1889 | SHA → SZX | May 29, 06:30 UTC | May 29, 18:15 UTC | 11h 45m |
| 2026-05-28 | DKH1156 | ZUH → PVG | May 28, 11:50 UTC | May 28, 12:05 UTC | 15m |
| 2026-05-28 | DKH1155 | PVG → ZUH | May 28, 09:45 UTC | May 28, 10:10 UTC | 25m |
| 2026-05-27 | DKH1308 | HKG → PVG | May 27, 04:04 UTC | May 27, 04:59 UTC | 55m |
| 2026-05-27 | DKH1307 | PVG → HKG | May 27, 01:14 UTC | May 27, 02:19 UTC | 1h 5m |
| 2026-05-26 | DKH2048 | HAK → HUZ | May 26, 00:00 UTC | May 26, 00:09 UTC | 10m |
| 2026-05-25 | DKH2047 | HGH → HUZ | May 25, 14:10 UTC | May 25, 14:25 UTC | 15m |
| 2026-05-25 | - | - | May 25, 12:20 UTC | May 25, 12:45 UTC | 25m |
| 2026-05-22 | DKH1292 | HKG → PVG | May 22, 13:25 UTC | May 22, 14:30 UTC | 1h 5m |
| 2026-05-22 | DKH1291 | PVG → HKG | May 22, 05:25 UTC | May 22, 10:55 UTC | 5h 30m |
| 2026-05-19 | DKH1352 | BKK → PVG | May 19, 19:10 UTC | May 19, 19:35 UTC | 25m |
| 2026-05-19 | DKH1351 | PVG → BKK | May 19, 17:15 UTC | May 19, 17:40 UTC | 25m |
| 2026-05-18 | DKH1352 | BKK → PVG | May 18, 18:35 UTC | May 18, 20:50 UTC | 2h 15m |
| 2026-05-18 | DKH1351 | PVG → BKK | May 18, 14:35 UTC | May 18, 16:50 UTC | 2h 15m |
| 2026-05-17 | DKH1351 | PVG → BKK | May 17, 20:45 UTC | May 18, 16:50 UTC | 20h 5m |
| 2026-05-17 | DKH1351 | PVG → BKK | May 17, 18:45 UTC | May 18, 16:50 UTC | 22h 5m |
| 2026-05-17 | DKH1351 | PVG → BKK | May 17, 14:45 UTC | May 17, 17:05 UTC | 2h 20m |
| 2026-05-16 | DKH1888 | SZX → SHA | May 16, 13:35 UTC | May 16, 13:46 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-1002 page for operator, model, and routing details .