sensors Mode-S transponder
7810EB
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8957 · AIRBUS A-321
- Hex
- 7810EB
- Octal
- 36010353
- Decimal
- 7,868,651
- Country
- CN
- Tail
- B-8957
- Type
- A321
- Flights observed
- 55
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 7810EB 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 |
|---|---|---|---|
| DKH1309 | - | 5 | 2026-07-12 |
| DKH1310 | - | 4 | 2026-07-12 |
| DKH1156 | Juneyao Airlines | 4 | 2026-05-31 |
| DKH1155 | Juneyao Airlines | 4 | 2026-05-31 |
| DKH1129 | Juneyao Airlines | 4 | 2026-05-24 |
| DKH1087 | - | 4 | 2026-06-23 |
| DKH1889 | Juneyao Airlines | 3 | 2026-05-04 |
| DKH1739 | Juneyao Airlines | 3 | 2026-04-28 |
| DKH1890 | Juneyao Airlines | 2 | 2026-05-04 |
| DKH1352 | - | 2 | 2026-04-13 |
| DKH2372 | Juneyao Airlines | 1 | 2026-05-18 |
| DKH2371 | Juneyao Airlines | 1 | 2026-05-18 |
| DKH2048 | Juneyao Airlines | 1 | 2026-04-24 |
| DKH2047 | Juneyao Airlines | 1 | 2026-04-23 |
| DKH1884 | Juneyao Airlines | 1 | 2026-06-07 |
| DKH1883 | Juneyao Airlines | 1 | 2026-06-07 |
| DKH1853 | - | 1 | 2026-04-18 |
| DKH1790 | Juneyao Airlines | 1 | 2026-06-07 |
| DKH1789 | Juneyao Airlines | 1 | 2026-06-07 |
| DKH1351 | Juneyao Airlines | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | DKH1310 | - | Jul 12, 08:20 UTC | Jul 12, 08:50 UTC | 30m |
| 2026-07-12 | DKH1309 | - | Jul 12, 06:15 UTC | Jul 12, 06:50 UTC | 35m |
| 2026-06-30 | DKH1310 | - | Jun 30, 04:30 UTC | Jun 30, 04:50 UTC | 20m |
| 2026-06-30 | DKH1309 | - | Jun 30, 02:25 UTC | Jun 30, 03:00 UTC | 35m |
| 2026-06-23 | DKH1087 | - | Jun 23, 08:45 UTC | Jun 23, 13:00 UTC | 4h 15m |
| 2026-06-18 | DKH1327 | PVG → SGN | Jun 18, 13:55 UTC | Jun 18, 20:00 UTC | 6h 5m |
| 2026-06-16 | DKH1310 | - | Jun 16, 04:30 UTC | Jun 16, 05:30 UTC | 1h 0m |
| 2026-06-15 | DKH1309 | - | Jun 15, 18:35 UTC | Jun 16, 02:40 UTC | 8h 5m |
| 2026-06-15 | DKH1329 | PVG → HAN | Jun 15, 16:24 UTC | Jun 15, 17:04 UTC | 40m |
| 2026-06-09 | DKH1087 | PVG → HAK | Jun 9, 04:40 UTC | Jun 9, 13:00 UTC | 8h 20m |
| 2026-06-09 | DKH1309 | PVG → TPE | Jun 9, 02:10 UTC | Jun 9, 02:50 UTC | 40m |
| 2026-06-07 | DKH1790 | XMN → NKG | Jun 7, 14:50 UTC | Jun 7, 15:00 UTC | 10m |
| 2026-06-07 | DKH1789 | NKG → XMN | Jun 7, 13:20 UTC | Jun 7, 13:30 UTC | 10m |
| 2026-06-07 | DKH1884 | SZX → SHA | Jun 7, 05:40 UTC | Jun 7, 05:50 UTC | 10m |
| 2026-06-07 | DKH1883 | SHA → SZX | Jun 7, 03:30 UTC | Jun 7, 03:50 UTC | 20m |
| 2026-06-06 | DKH1282 | CGQ → PVG | Jun 6, 04:50 UTC | Jun 6, 05:25 UTC | 35m |
| 2026-05-31 | DKH1156 | ZUH → PVG | May 31, 12:40 UTC | May 31, 12:55 UTC | 15m |
| 2026-05-31 | DKH1155 | PVG → ZUH | May 31, 10:15 UTC | May 31, 11:05 UTC | 50m |
| 2026-05-30 | DKH1155 | PVG → ZUH | May 30, 13:20 UTC | May 31, 11:05 UTC | 21h 45m |
| 2026-05-30 | DKH1127 | SHA → SYX | May 30, 10:00 UTC | May 30, 13:35 UTC | 3h 35m |
| 2026-05-25 | DKH1112 | - | May 25, 15:25 UTC | May 25, 15:50 UTC | 25m |
| 2026-05-24 | DKH1129 | SHA → SYX | May 24, 06:40 UTC | May 24, 15:45 UTC | 9h 5m |
| 2026-05-18 | DKH2371 | NKG → ZUH | May 18, 07:40 UTC | May 18, 07:50 UTC | 10m |
| 2026-05-18 | DKH2372 | ZUH → NKG | May 18, 03:01 UTC | May 18, 03:10 UTC | 10m |
| 2026-05-17 | DKH1159 | SHA → ZUH | May 17, 23:55 UTC | May 18, 00:50 UTC | 55m |
| 2026-05-15 | DKH1087 | PVG → HAK | May 15, 04:30 UTC | May 15, 10:05 UTC | 5h 35m |
| 2026-05-14 | DKH1309 | PVG → TPE | May 14, 14:45 UTC | May 15, 02:30 UTC | 11h 45m |
| 2026-05-11 | DKH1129 | SHA → SYX | May 11, 08:05 UTC | May 11, 11:30 UTC | 3h 25m |
| 2026-05-10 | DKH1292 | HKG → PVG | May 10, 12:54 UTC | May 11, 11:30 UTC | 22h 35m |
| 2026-05-10 | DKH1291 | PVG → HKG | May 10, 09:30 UTC | May 10, 11:05 UTC | 1h 35m |
| 2026-05-08 | DKH1156 | ZUH → PVG | May 8, 13:50 UTC | May 8, 14:00 UTC | 10m |
| 2026-05-08 | DKH1155 | PVG → ZUH | May 8, 12:04 UTC | May 8, 12:14 UTC | 10m |
| 2026-05-04 | DKH1890 | SZX → SHA | May 4, 23:45 UTC | May 4, 23:55 UTC | 10m |
| 2026-05-04 | DKH1889 | SHA → SZX | May 4, 15:30 UTC | May 4, 15:55 UTC | 25m |
| 2026-05-04 | DKH1129 | SHA → SYX | May 4, 06:45 UTC | May 4, 10:15 UTC | 3h 30m |
| 2026-05-02 | DKH1062 | YLX → PVG | May 2, 13:35 UTC | May 2, 13:45 UTC | 10m |
| 2026-04-30 | DKH1087 | PVG → HAK | Apr 30, 04:30 UTC | Apr 30, 12:55 UTC | 8h 25m |
| 2026-04-30 | DKH1310 | TPE → PVG | Apr 30, 02:05 UTC | Apr 30, 02:50 UTC | 45m |
| 2026-04-28 | DKH1739 | NKG → SYX | Apr 28, 10:30 UTC | Apr 28, 10:45 UTC | 15m |
| 2026-04-27 | DKH1739 | NKG → SYX | Apr 27, 10:45 UTC | Apr 27, 14:30 UTC | 3h 45m |
| 2026-04-26 | DKH1739 | NKG → SYX | Apr 26, 10:20 UTC | Apr 26, 14:25 UTC | 4h 5m |
| 2026-04-24 | DKH2048 | HAK → HUZ | Apr 24, 00:45 UTC | Apr 24, 01:00 UTC | 15m |
| 2026-04-23 | DKH2047 | HGH → HUZ | Apr 23, 14:20 UTC | Apr 23, 14:35 UTC | 15m |
| 2026-04-21 | DKH1890 | SZX → SHA | Apr 21, 23:55 UTC | Apr 22, 00:10 UTC | 15m |
| 2026-04-21 | DKH1889 | SHA → SZX | Apr 21, 14:25 UTC | Apr 21, 15:31 UTC | 1h 5m |
| 2026-04-20 | DKH1156 | ZUH → PVG | Apr 20, 13:50 UTC | Apr 20, 14:05 UTC | 15m |
| 2026-04-20 | DKH1155 | PVG → ZUH | Apr 20, 11:20 UTC | Apr 20, 11:55 UTC | 35m |
| 2026-04-18 | DKH1853 | - | Apr 18, 15:45 UTC | Apr 18, 15:55 UTC | 10m |
| 2026-04-18 | DKH1129 | SHA → SYX | Apr 18, 06:45 UTC | Apr 18, 11:00 UTC | 4h 15m |
| 2026-04-16 | DKH1889 | - | Apr 16, 16:05 UTC | Apr 16, 16:40 UTC | 35m |
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-8957 page for operator, model, and routing details .