sensors Mode-S transponder
781929
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-30EQ · AIRBUS A-321neo
- Hex
- 781929
- Octal
- 36014451
- Decimal
- 7,870,761
- Country
- CN
- Tail
- B-30EQ
- Type
- A21N
- Flights observed
- 47
- Distinct callsigns
- 17
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 781929 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DKH1127 | Juneyao Airlines | 17 | 2026-05-11 |
| DKH1128 | Juneyao Airlines | 11 | 2026-04-22 |
| DKH1177 | Juneyao Airlines | 3 | 2026-05-18 |
| DKH1888 | Juneyao Airlines | 2 | 2026-05-10 |
| DKH1887 | Juneyao Airlines | 2 | 2026-05-10 |
| DKH2288 | Juneyao Airlines | 1 | 2026-05-25 |
| DKH1884 | Juneyao Airlines | 1 | 2026-05-12 |
| DKH1883 | Juneyao Airlines | 1 | 2026-05-12 |
| DKH1790 | Juneyao Airlines | 1 | 2026-05-12 |
| DKH1576 | Juneyao Airlines | 1 | 2026-05-27 |
| DKH1575 | Juneyao Airlines | 1 | 2026-05-26 |
| DKH1312 | Juneyao Airlines | 1 | 2026-05-27 |
| DKH1311 | Juneyao Airlines | 1 | 2026-05-26 |
| DKH1178 | - | 1 | 2026-04-13 |
| DKH1156 | Juneyao Airlines | 1 | 2026-05-25 |
| DKH1155 | Juneyao Airlines | 1 | 2026-05-25 |
| DKH1087 | Juneyao Airlines | 1 | 2026-05-20 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | DKH1576 | SIN → PVG | May 27, 16:15 UTC | May 27, 20:25 UTC | 4h 10m |
| 2026-05-27 | DKH1312 | KHH → PVG | May 27, 04:49 UTC | May 27, 13:30 UTC | 8h 41m |
| 2026-05-26 | DKH1311 | PVG → KHH | May 26, 15:54 UTC | May 27, 03:24 UTC | 11h 30m |
| 2026-05-26 | DKH1575 | PVG → SIN | May 26, 09:55 UTC | May 26, 13:45 UTC | 3h 50m |
| 2026-05-25 | DKH1156 | ZUH → PVG | May 25, 13:50 UTC | May 25, 14:05 UTC | 15m |
| 2026-05-25 | DKH1155 | PVG → ZUH | May 25, 11:15 UTC | May 25, 12:15 UTC | 1h 0m |
| 2026-05-25 | DKH2288 | CAN → SHA | May 25, 04:35 UTC | May 25, 04:45 UTC | 10m |
| 2026-05-20 | DKH1087 | PVG → HAK | May 20, 08:55 UTC | May 20, 10:10 UTC | 1h 15m |
| 2026-05-18 | DKH1177 | SHA → SYX | May 18, 03:20 UTC | May 18, 07:05 UTC | 3h 45m |
| 2026-05-13 | DKH1177 | SHA → SYX | May 13, 03:10 UTC | May 13, 07:00 UTC | 3h 50m |
| 2026-05-12 | DKH1790 | XMN → NKG | May 12, 12:45 UTC | May 12, 12:55 UTC | 10m |
| 2026-05-12 | DKH1884 | SZX → SHA | May 12, 05:30 UTC | May 12, 05:40 UTC | 10m |
| 2026-05-12 | DKH1883 | SHA → SZX | May 12, 03:50 UTC | May 12, 04:10 UTC | 20m |
| 2026-05-11 | DKH1127 | SHA → SYX | May 11, 09:50 UTC | May 11, 13:35 UTC | 3h 45m |
| 2026-05-10 | DKH1888 | SZX → SHA | May 10, 13:25 UTC | May 10, 13:35 UTC | 10m |
| 2026-05-10 | DKH1887 | SHA → SZX | May 10, 11:35 UTC | May 10, 11:55 UTC | 20m |
| 2026-04-25 | DKH1127 | SHA → SYX | Apr 25, 09:55 UTC | Apr 25, 13:50 UTC | 3h 55m |
| 2026-04-24 | DKH1127 | SHA → SYX | Apr 24, 13:35 UTC | Apr 25, 10:15 UTC | 20h 40m |
| 2026-04-24 | DKH1127 | SHA → SYX | Apr 24, 10:20 UTC | Apr 25, 10:15 UTC | 23h 55m |
| 2026-04-23 | DKH1127 | SHA → SYX | Apr 23, 13:40 UTC | Apr 24, 10:35 UTC | 20h 55m |
| 2026-04-23 | DKH1127 | SHA → SYX | Apr 23, 10:20 UTC | Apr 24, 10:15 UTC | 23h 54m |
| 2026-04-22 | DKH1128 | SYX → SHA | Apr 22, 14:35 UTC | Apr 23, 13:50 UTC | 23h 15m |
| 2026-04-22 | DKH1127 | SHA → SYX | Apr 22, 10:20 UTC | Apr 23, 10:15 UTC | 23h 55m |
| 2026-04-22 | DKH1127 | SHA → SYX | Apr 22, 10:05 UTC | Apr 22, 14:50 UTC | 4h 45m |
| 2026-04-21 | DKH1127 | SHA → SYX | Apr 21, 13:25 UTC | Apr 22, 10:30 UTC | 21h 5m |
| 2026-04-21 | DKH1127 | SHA → SYX | Apr 21, 10:20 UTC | Apr 22, 10:15 UTC | 23h 55m |
| 2026-04-21 | DKH1128 | SYX → SHA | Apr 21, 10:10 UTC | Apr 21, 13:35 UTC | 3h 25m |
| 2026-04-20 | DKH1128 | SYX → SHA | Apr 20, 13:40 UTC | Apr 21, 10:20 UTC | 20h 40m |
| 2026-04-20 | DKH1128 | SYX → SHA | Apr 20, 10:20 UTC | Apr 21, 10:15 UTC | 23h 56m |
| 2026-04-20 | DKH1128 | SYX → SHA | Apr 20, 10:10 UTC | Apr 20, 13:50 UTC | 3h 40m |
| 2026-04-19 | DKH1128 | SYX → SHA | Apr 19, 13:45 UTC | Apr 20, 10:20 UTC | 20h 35m |
| 2026-04-19 | DKH1128 | SYX → SHA | Apr 19, 10:20 UTC | Apr 20, 10:15 UTC | 23h 55m |
| 2026-04-19 | DKH1127 | SHA → SYX | Apr 19, 09:55 UTC | Apr 19, 14:00 UTC | 4h 5m |
| 2026-04-18 | DKH1127 | SHA → SYX | Apr 18, 13:20 UTC | Apr 19, 10:20 UTC | 21h 0m |
| 2026-04-18 | DKH1127 | SHA → SYX | Apr 18, 10:00 UTC | Apr 18, 13:30 UTC | 3h 30m |
| 2026-04-17 | DKH1128 | - | Apr 17, 13:55 UTC | Apr 18, 13:30 UTC | 23h 35m |
| 2026-04-17 | DKH1127 | SHA → SYX | Apr 17, 10:10 UTC | Apr 17, 10:30 UTC | 20m |
| 2026-04-16 | DKH1128 | - | Apr 16, 14:50 UTC | Apr 16, 15:05 UTC | 15m |
| 2026-04-16 | DKH1127 | SHA → SYX | Apr 16, 09:54 UTC | Apr 16, 10:14 UTC | 20m |
| 2026-04-15 | DKH1128 | - | Apr 15, 14:30 UTC | Apr 15, 14:45 UTC | 14m |
| 2026-04-15 | DKH1127 | SHA → SYX | Apr 15, 10:45 UTC | Apr 15, 10:55 UTC | 10m |
| 2026-04-14 | DKH1128 | - | Apr 14, 13:40 UTC | Apr 14, 13:55 UTC | 15m |
| 2026-04-14 | DKH1127 | - | Apr 14, 10:15 UTC | Apr 14, 10:35 UTC | 20m |
| 2026-04-13 | DKH1888 | - | Apr 13, 13:40 UTC | Apr 13, 13:55 UTC | 15m |
| 2026-04-13 | DKH1887 | - | Apr 13, 11:40 UTC | Apr 13, 12:00 UTC | 20m |
| 2026-04-13 | DKH1178 | - | Apr 13, 06:40 UTC | Apr 13, 06:50 UTC | 10m |
| 2026-04-13 | DKH1177 | SHA → SYX | Apr 13, 02:50 UTC | Apr 13, 03:35 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-30EQ page for operator, model, and routing details .