sensors Mode-S transponder
782159
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-226N · BOEING 787-9 Dreamliner
- Hex
- 782159
- Octal
- 36020531
- Decimal
- 7,872,857
- Country
- CN
- Tail
- B-226N
- Type
- B789
- Flights observed
- 188
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 20:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 782159 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 |
|---|---|---|---|
| DKH1657 | Juneyao Airlines | 15 | 2026-07-24 |
| DKH1607 | - | 13 | 2026-07-08 |
| DKH1659 | - | 11 | 2026-07-09 |
| DKH1885 | - | 10 | 2026-06-16 |
| DKH1881 | - | 10 | 2026-06-17 |
| DKH1608 | - | 10 | 2026-07-08 |
| DKH1882 | - | 9 | 2026-06-17 |
| DKH1658 | Juneyao Airlines | 9 | 2026-07-25 |
| DKH1790 | Juneyao Airlines | 7 | 2026-06-06 |
| DKH1379 | Juneyao Airlines | 7 | 2026-07-20 |
| DKH1883 | Juneyao Airlines | 6 | 2026-06-05 |
| DKH1789 | Juneyao Airlines | 6 | 2026-06-05 |
| DKH1670 | - | 6 | 2026-07-19 |
| DKH1669 | Juneyao Airlines | 6 | 2026-07-26 |
| DKH1886 | - | 5 | 2026-06-16 |
| DKH1884 | Juneyao Airlines | 5 | 2026-06-06 |
| DKH1662 | - | 5 | 2026-07-18 |
| DKH1660 | - | 5 | 2026-07-10 |
| DKH1655 | - | 5 | 2026-06-23 |
| DKH1380 | Juneyao Airlines | 5 | 2026-07-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | DKH1669 | PVG → SYD | Jul 26, 04:45 UTC | Jul 26, 20:20 UTC | 15h 36m |
| 2026-07-25 | DKH1658 | ATH → PVG | Jul 25, 12:00 UTC | Jul 26, 03:10 UTC | 15h 10m |
| 2026-07-24 | DKH1657 | PVG → ATH | Jul 24, 11:30 UTC | Jul 25, 05:05 UTC | 17h 35m |
| 2026-07-24 | DKH1657 | PVG → ATH | Jul 24, 05:15 UTC | Jul 25, 04:15 UTC | 23h 0m |
| 2026-07-24 | DKH1355 | PVG → DPS | Jul 24, 02:35 UTC | Jul 25, 02:15 UTC | 23h 40m |
| 2026-07-23 | DKH1355 | PVG → DPS | Jul 23, 14:20 UTC | Jul 24, 14:00 UTC | 23h 40m |
| 2026-07-23 | DKH1658 | - | Jul 23, 12:55 UTC | Jul 24, 05:50 UTC | 16h 55m |
| 2026-07-22 | DKH1657 | PVG → ATH | Jul 22, 11:20 UTC | Jul 23, 04:25 UTC | 17h 5m |
| 2026-07-22 | DKH1657 | PVG → ATH | Jul 22, 05:25 UTC | Jul 23, 04:15 UTC | 22h 50m |
| 2026-07-22 | DKH1355 | PVG → DPS | Jul 22, 02:30 UTC | Jul 23, 02:15 UTC | 23h 45m |
| 2026-07-21 | DKH1380 | NRT → PVG | Jul 21, 04:35 UTC | Jul 22, 03:35 UTC | 23h 0m |
| 2026-07-20 | DKH1379 | PVG → NRT | Jul 20, 13:40 UTC | Jul 21, 02:55 UTC | 13h 14m |
| 2026-07-19 | DKH1670 | SYD → KIX | Jul 19, 22:30 UTC | Jul 20, 12:20 UTC | 13h 50m |
| 2026-07-19 | DKH1669 | PVG → SYD | Jul 19, 04:40 UTC | Jul 19, 20:40 UTC | 16h 0m |
| 2026-07-18 | DKH1662 | MAN → NRT | Jul 18, 10:40 UTC | Jul 19, 03:05 UTC | 16h 25m |
| 2026-07-17 | DKH1661 | PVG → MAN | Jul 17, 14:00 UTC | Jul 18, 05:25 UTC | 15h 26m |
| 2026-07-17 | DKH1380 | NRT → KIX | Jul 17, 04:59 UTC | Jul 17, 12:40 UTC | 7h 40m |
| 2026-07-16 | DKH1379 | PVG → NRT | Jul 16, 14:00 UTC | Jul 17, 03:25 UTC | 13h 25m |
| 2026-07-15 | DKH1670 | SYD → KIX | Jul 15, 23:05 UTC | Jul 16, 12:40 UTC | 13h 35m |
| 2026-07-15 | DKH1669 | - | Jul 15, 11:40 UTC | Jul 15, 20:50 UTC | 9h 10m |
| 2026-07-14 | DKH1338 | - | Jul 14, 14:25 UTC | Jul 14, 15:20 UTC | 55m |
| 2026-07-13 | DKH1670 | SYD → KIX | Jul 13, 23:15 UTC | Jul 14, 13:05 UTC | 13h 50m |
| 2026-07-13 | DKH1669 | NRT → SYD | Jul 13, 04:40 UTC | Jul 13, 21:20 UTC | 16h 40m |
| 2026-07-12 | DKH1379 | - | Jul 12, 09:50 UTC | Jul 13, 03:01 UTC | 17h 10m |
| 2026-07-12 | DKH1379 | - | Jul 12, 07:01 UTC | Jul 13, 03:01 UTC | 20h 0m |
| 2026-07-11 | DKH1506 | - | Jul 11, 04:25 UTC | Jul 11, 05:25 UTC | 1h 0m |
| 2026-07-10 | DKH1660 | BRU → KIX | Jul 10, 11:15 UTC | Jul 11, 02:25 UTC | 15h 10m |
| 2026-07-09 | DKH1659 | - | Jul 9, 11:30 UTC | Jul 10, 05:40 UTC | 18h 10m |
| 2026-07-09 | DKH1659 | - | Jul 9, 06:20 UTC | Jul 10, 05:40 UTC | 23h 20m |
| 2026-07-09 | DKH1659 | - | Jul 9, 06:00 UTC | Jul 10, 04:15 UTC | 22h 15m |
| 2026-07-09 | DKH1659 | - | Jul 9, 03:25 UTC | Jul 10, 02:15 UTC | 22h 50m |
| 2026-07-08 | DKH1355 | - | Jul 8, 18:20 UTC | Jul 9, 14:00 UTC | 19h 40m |
| 2026-07-08 | DKH1608 | - | Jul 8, 14:20 UTC | Jul 9, 14:00 UTC | 23h 40m |
| 2026-07-08 | DKH1607 | - | Jul 8, 11:15 UTC | Jul 8, 11:30 UTC | 15m |
| 2026-07-07 | DKH1608 | - | Jul 7, 14:20 UTC | Jul 8, 09:55 UTC | 19h 35m |
| 2026-07-07 | DKH1608 | - | Jul 7, 13:50 UTC | Jul 8, 09:55 UTC | 20h 5m |
| 2026-07-07 | DKH1607 | - | Jul 7, 10:50 UTC | Jul 7, 10:55 UTC | 5m |
| 2026-07-06 | DKH1338 | - | Jul 6, 14:10 UTC | Jul 7, 07:05 UTC | 16h 55m |
| 2026-07-05 | DKH1670 | SYD → KIX | Jul 5, 23:30 UTC | Jul 6, 13:00 UTC | 13h 30m |
| 2026-07-05 | DKH1669 | NRT → SYD | Jul 5, 04:50 UTC | Jul 5, 20:45 UTC | 15h 55m |
| 2026-07-04 | DKH1658 | ATH → NRT | Jul 4, 11:55 UTC | Jul 5, 03:20 UTC | 15h 25m |
| 2026-07-03 | DKH1657 | - | Jul 3, 13:00 UTC | Jul 4, 05:15 UTC | 16h 15m |
| 2026-07-03 | DKH1506 | - | Jul 3, 04:45 UTC | Jul 3, 11:25 UTC | 6h 40m |
| 2026-07-02 | DKH1658 | ATH → KIX | Jul 2, 12:10 UTC | Jul 3, 02:55 UTC | 14h 45m |
| 2026-07-01 | DKH1657 | - | Jul 1, 08:50 UTC | Jul 2, 04:15 UTC | 19h 25m |
| 2026-06-30 | DKH1338 | - | Jun 30, 13:45 UTC | Jul 1, 07:10 UTC | 17h 25m |
| 2026-06-30 | DKH1506 | KIX → KIX | Jun 30, 03:55 UTC | Jun 30, 12:25 UTC | 8h 30m |
| 2026-06-29 | DKH1658 | ATH → KIX | Jun 29, 13:14 UTC | Jun 30, 02:10 UTC | 12h 55m |
| 2026-06-28 | DKH1657 | - | Jun 28, 22:34 UTC | Jun 29, 04:55 UTC | 6h 20m |
| 2026-06-28 | DKH1657 | - | Jun 28, 07:44 UTC | Jun 29, 04:55 UTC | 21h 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-226N page for operator, model, and routing details .