sensors Mode-S transponder
780D90
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1645 · AIRBUS A-321
- Hex
- 780D90
- Octal
- 36006620
- Decimal
- 7,867,792
- Country
- CN
- Tail
- B-1645
- Type
- A321
- Flights observed
- 54
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 780D90 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 |
|---|---|---|---|
| DKH1127 | Juneyao Airlines | 6 | 2026-05-23 |
| DKH1066 | - | 5 | 2026-06-28 |
| DKH1177 | - | 4 | 2026-07-02 |
| DKH1890 | - | 3 | 2026-07-02 |
| DKH1883 | Juneyao Airlines | 3 | 2026-06-01 |
| DKH2047 | Juneyao Airlines | 2 | 2026-06-11 |
| DKH1790 | Juneyao Airlines | 2 | 2026-05-28 |
| DKH1292 | Juneyao Airlines | 2 | 2026-05-17 |
| DKH1291 | Juneyao Airlines | 2 | 2026-05-17 |
| DKH1156 | Juneyao Airlines | 2 | 2026-05-05 |
| DKH1155 | Juneyao Airlines | 2 | 2026-05-05 |
| DKH1128 | Juneyao Airlines | 2 | 2026-04-28 |
| DKH1087 | - | 2 | 2026-07-10 |
| DKH2068 | - | 1 | 2026-06-24 |
| DKH2048 | Juneyao Airlines | 1 | 2026-06-11 |
| DKH188Q | - | 1 | 2026-05-21 |
| DKH1888 | - | 1 | 2026-07-01 |
| DKH1887 | - | 1 | 2026-07-02 |
| DKH1886 | Juneyao Airlines | 1 | 2026-05-21 |
| DKH1884 | Juneyao Airlines | 1 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | DKH1375 | - | Jul 12, 07:01 UTC | Jul 12, 07:10 UTC | 10m |
| 2026-07-10 | DKH1087 | - | Jul 10, 08:35 UTC | Jul 10, 14:50 UTC | 6h 15m |
| 2026-07-09 | DKH1329 | - | Jul 9, 17:35 UTC | Jul 9, 18:00 UTC | 25m |
| 2026-07-02 | DKH1890 | - | Jul 2, 23:55 UTC | Jul 3, 00:05 UTC | 10m |
| 2026-07-02 | DKH1887 | - | Jul 2, 13:25 UTC | Jul 2, 13:50 UTC | 25m |
| 2026-07-02 | DKH1177 | - | Jul 2, 03:15 UTC | Jul 2, 07:15 UTC | 4h 0m |
| 2026-07-01 | DKH1888 | - | Jul 1, 15:05 UTC | Jul 1, 15:15 UTC | 10m |
| 2026-07-01 | DKH1177 | - | Jul 1, 03:45 UTC | Jul 1, 07:30 UTC | 3h 45m |
| 2026-06-28 | DKH1066 | - | Jun 28, 04:50 UTC | Jun 28, 05:09 UTC | 20m |
| 2026-06-24 | DKH2068 | - | Jun 24, 14:09 UTC | Jun 24, 14:34 UTC | 25m |
| 2026-06-23 | DKH1066 | - | Jun 23, 03:00 UTC | Jun 23, 03:20 UTC | 20m |
| 2026-06-22 | DKH1066 | - | Jun 22, 03:24 UTC | Jun 22, 03:45 UTC | 20m |
| 2026-06-21 | DKH1312 | - | Jun 21, 04:44 UTC | Jun 21, 05:40 UTC | 55m |
| 2026-06-20 | DKH1311 | - | Jun 20, 13:04 UTC | Jun 21, 03:19 UTC | 14h 15m |
| 2026-06-15 | DKH1506 | - | Jun 15, 04:04 UTC | Jun 15, 05:10 UTC | 1h 5m |
| 2026-06-15 | DKH1505 | - | Jun 15, 01:25 UTC | Jun 15, 02:24 UTC | 1h 0m |
| 2026-06-11 | DKH2048 | HAK → HUZ | Jun 11, 23:55 UTC | Jun 12, 00:10 UTC | 15m |
| 2026-06-11 | DKH2047 | HGH → HUZ | Jun 11, 14:50 UTC | Jun 11, 15:00 UTC | 10m |
| 2026-06-11 | DKH2047 | HGH → HUZ | Jun 11, 12:40 UTC | Jun 11, 13:15 UTC | 35m |
| 2026-06-07 | DKH1177 | SHA → SYX | Jun 7, 03:00 UTC | Jun 7, 07:10 UTC | 4h 10m |
| 2026-06-04 | DKH1066 | DAT → SHA | Jun 4, 03:15 UTC | Jun 4, 03:40 UTC | 25m |
| 2026-06-03 | DKH1130 | SYX → SHA | Jun 3, 09:25 UTC | Jun 3, 10:20 UTC | 55m |
| 2026-06-03 | DKH1129 | SHA → SYX | Jun 3, 06:35 UTC | Jun 3, 07:15 UTC | 40m |
| 2026-06-02 | DKH1890 | SZX → SHA | Jun 2, 00:00 UTC | Jun 2, 00:15 UTC | 15m |
| 2026-06-01 | DKH1883 | SHA → SZX | Jun 1, 03:25 UTC | Jun 1, 03:50 UTC | 25m |
| 2026-05-28 | DKH1790 | XMN → NKG | May 28, 12:55 UTC | May 28, 13:10 UTC | 15m |
| 2026-05-28 | DKH1884 | SZX → SHA | May 28, 05:35 UTC | May 28, 05:45 UTC | 10m |
| 2026-05-28 | DKH1883 | SHA → SZX | May 28, 03:15 UTC | May 28, 04:00 UTC | 45m |
| 2026-05-23 | DKH1127 | SHA → SYX | May 23, 10:05 UTC | May 23, 13:30 UTC | 3h 25m |
| 2026-05-21 | DKH1886 | SZX → SHA | May 21, 13:10 UTC | May 21, 13:20 UTC | 10m |
| 2026-05-21 | DKH1890 | SZX → SHA | May 21, 06:15 UTC | May 21, 06:25 UTC | 10m |
| 2026-05-21 | DKH188Q | - | May 21, 02:10 UTC | May 21, 02:20 UTC | 10m |
| 2026-05-19 | DKH1087 | PVG → HAK | May 19, 08:45 UTC | May 19, 12:50 UTC | 4h 5m |
| 2026-05-17 | DKH1292 | HKG → PVG | May 17, 13:20 UTC | May 17, 14:30 UTC | 1h 10m |
| 2026-05-17 | DKH1291 | PVG → HKG | May 17, 09:45 UTC | May 17, 11:10 UTC | 1h 25m |
| 2026-05-15 | - | - | May 15, 14:35 UTC | May 15, 14:45 UTC | 10m |
| 2026-05-07 | DKH1292 | HKG → PVG | May 7, 13:15 UTC | May 7, 14:25 UTC | 1h 10m |
| 2026-05-07 | DKH1291 | PVG → HKG | May 7, 05:45 UTC | May 7, 11:10 UTC | 5h 25m |
| 2026-05-05 | DKH1156 | ZUH → PVG | May 5, 11:40 UTC | May 5, 11:50 UTC | 10m |
| 2026-05-05 | DKH1155 | PVG → ZUH | May 5, 09:50 UTC | May 5, 10:15 UTC | 25m |
| 2026-05-01 | DKH1790 | XMN → NKG | May 1, 13:10 UTC | May 1, 13:20 UTC | 10m |
| 2026-05-01 | DKH1789 | NKG → XMN | May 1, 10:40 UTC | May 1, 11:00 UTC | 20m |
| 2026-05-01 | DKH1883 | SHA → SZX | May 1, 03:40 UTC | May 1, 04:00 UTC | 20m |
| 2026-04-29 | DKH1127 | SHA → SYX | Apr 29, 10:15 UTC | Apr 30, 03:10 UTC | 16h 54m |
| 2026-04-28 | DKH1128 | SYX → SHA | Apr 28, 14:05 UTC | Apr 29, 14:00 UTC | 23h 56m |
| 2026-04-28 | DKH1127 | SHA → SYX | Apr 28, 10:10 UTC | Apr 28, 15:00 UTC | 4h 50m |
| 2026-04-27 | DKH1127 | SHA → SYX | Apr 27, 13:40 UTC | Apr 28, 10:35 UTC | 20h 55m |
| 2026-04-27 | DKH1127 | SHA → SYX | Apr 27, 10:20 UTC | Apr 27, 13:50 UTC | 3h 30m |
| 2026-04-23 | DKH1177 | SHA → SYX | Apr 23, 02:55 UTC | Apr 23, 15:55 UTC | 13h 0m |
| 2026-04-22 | DKH1066 | DAT → SHA | Apr 22, 03:15 UTC | Apr 22, 03:30 UTC | 15m |
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-1645 page for operator, model, and routing details .