sensors Mode-S transponder
7816DE
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-20AY · BOEING 737 MAX 8
- Hex
- 7816DE
- Octal
- 36013336
- Decimal
- 7,870,174
- Country
- CN
- Tail
- B-20AY
- Type
- B38M
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 7816DE 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 |
|---|---|---|---|
| CSH866 | - | 10 | 2026-07-05 |
| CSH865 | - | 7 | 2026-07-04 |
| CSH863 | - | 7 | 2026-07-04 |
| CSH9539 | Shanghai Airlines | 6 | 2026-06-09 |
| CSH858 | Shanghai Airlines | 6 | 2026-05-22 |
| CSH831 | - | 6 | 2026-06-12 |
| CSH862 | - | 5 | 2026-07-10 |
| CSH861 | - | 5 | 2026-07-10 |
| CSH857 | - | 5 | 2026-07-05 |
| CSH848 | Shanghai Airlines | 4 | 2026-05-01 |
| CSH847 | Shanghai Airlines | 4 | 2026-05-01 |
| CSH832 | Shanghai Airlines | 4 | 2026-06-13 |
| CSH812 | - | 4 | 2026-07-07 |
| CSH868 | Shanghai Airlines | 3 | 2026-05-28 |
| CSH867 | Shanghai Airlines | 3 | 2026-05-28 |
| CSH843 | Shanghai Airlines | 3 | 2026-07-09 |
| CSH841 | - | 3 | 2026-07-01 |
| CSH833 | Shanghai Airlines | 3 | 2026-04-18 |
| CSH811 | - | 3 | 2026-07-06 |
| CSH9136 | - | 2 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CSH7222 | - | Jul 13, 06:25 UTC | Jul 13, 11:15 UTC | 4h 50m |
| 2026-07-12 | CSH7221 | - | Jul 12, 16:45 UTC | Jul 13, 04:55 UTC | 12h 10m |
| 2026-07-12 | CSH7223 | - | Jul 12, 01:20 UTC | Jul 12, 15:25 UTC | 14h 5m |
| 2026-07-10 | CSH862 | - | Jul 10, 18:00 UTC | Jul 11, 11:35 UTC | 17h 35m |
| 2026-07-10 | CSH861 | - | Jul 10, 15:50 UTC | Jul 10, 16:10 UTC | 20m |
| 2026-07-09 | CSH844 | SIN → PVG | Jul 9, 19:45 UTC | Jul 10, 12:45 UTC | 17h 0m |
| 2026-07-09 | CSH843 | PVG → SIN | Jul 9, 14:25 UTC | Jul 9, 18:30 UTC | 4h 5m |
| 2026-07-07 | CSH812 | - | Jul 7, 06:20 UTC | Jul 7, 07:30 UTC | 1h 10m |
| 2026-07-06 | CSH811 | - | Jul 6, 13:10 UTC | Jul 7, 04:10 UTC | 15h 0m |
| 2026-07-05 | CSH857 | - | Jul 5, 16:15 UTC | Jul 6, 15:30 UTC | 23h 15m |
| 2026-07-05 | CSH866 | - | Jul 5, 13:00 UTC | Jul 5, 17:10 UTC | 4h 10m |
| 2026-07-04 | CSH865 | - | Jul 4, 23:40 UTC | Jul 5, 11:30 UTC | 11h 50m |
| 2026-07-04 | CSH863 | - | Jul 4, 18:10 UTC | Jul 4, 22:20 UTC | 4h 10m |
| 2026-07-03 | CSH812 | - | Jul 3, 08:00 UTC | Jul 3, 08:55 UTC | 55m |
| 2026-07-02 | CSH811 | - | Jul 2, 19:50 UTC | Jul 3, 05:20 UTC | 9h 30m |
| 2026-07-02 | CSH843 | PVG → SIN | Jul 2, 05:00 UTC | Jul 2, 18:10 UTC | 13h 10m |
| 2026-07-01 | CSH841 | - | Jul 1, 10:45 UTC | Jul 1, 16:55 UTC | 6h 10m |
| 2026-06-30 | CSH9136 | - | Jun 30, 12:50 UTC | Jul 1, 11:15 UTC | 22h 25m |
| 2026-06-30 | CSH9136 | - | Jun 30, 04:25 UTC | Jun 30, 13:15 UTC | 8h 50m |
| 2026-06-24 | CSH9068 | CGQ → PVG | Jun 24, 13:34 UTC | Jun 24, 14:09 UTC | 35m |
| 2026-06-18 | CSH864 | - | Jun 18, 23:05 UTC | Jun 19, 03:05 UTC | 3h 59m |
| 2026-06-18 | CSH863 | - | Jun 18, 02:55 UTC | Jun 18, 21:30 UTC | 18h 35m |
| 2026-06-17 | CSH853 | HKG → BKK | Jun 17, 06:40 UTC | Jun 17, 14:40 UTC | 8h 0m |
| 2026-06-16 | CSH811 | - | Jun 16, 19:50 UTC | Jun 17, 04:30 UTC | 8h 40m |
| 2026-06-16 | CSH843 | PVG → SIN | Jun 16, 14:00 UTC | Jun 16, 17:49 UTC | 3h 50m |
| 2026-06-13 | CSH832 | HKT → PVG | Jun 13, 14:15 UTC | Jun 14, 08:50 UTC | 18h 35m |
| 2026-06-13 | CSH832 | HKT → PVG | Jun 13, 13:10 UTC | Jun 14, 08:50 UTC | 19h 40m |
| 2026-06-13 | CSH832 | HKT → PVG | Jun 13, 03:25 UTC | Jun 13, 20:15 UTC | 16h 49m |
| 2026-06-12 | CSH831 | - | Jun 12, 15:40 UTC | Jun 13, 15:05 UTC | 23h 24m |
| 2026-06-12 | CSH866 | KUL → PVG | Jun 12, 12:30 UTC | Jun 13, 03:40 UTC | 15h 10m |
| 2026-06-11 | CSH865 | PVG → KUL | Jun 11, 23:15 UTC | Jun 12, 11:05 UTC | 11h 51m |
| 2026-06-11 | CSH863 | PVG → KUL | Jun 11, 12:55 UTC | Jun 11, 21:35 UTC | 8h 40m |
| 2026-06-09 | CSH9539 | PVG → SYX | Jun 9, 03:45 UTC | Jun 9, 08:00 UTC | 4h 15m |
| 2026-06-07 | CSH9255 | PVG → HAK | Jun 7, 03:05 UTC | Jun 7, 06:35 UTC | 3h 30m |
| 2026-05-30 | CSH9253 | SHA → HAK | May 30, 10:35 UTC | May 30, 13:45 UTC | 3h 10m |
| 2026-05-28 | CSH868 | BKI → PVG | May 28, 17:45 UTC | May 28, 20:15 UTC | 2h 30m |
| 2026-05-28 | CSH867 | PVG → BKI | May 28, 13:20 UTC | May 28, 16:35 UTC | 3h 15m |
| 2026-05-23 | CSH814 | KUL → FOC | May 23, 19:25 UTC | May 24, 10:25 UTC | 15h 0m |
| 2026-05-23 | CSH813 | FOC → KUL | May 23, 13:00 UTC | May 23, 16:50 UTC | 3h 50m |
| 2026-05-22 | CSH858 | HKT → PVG | May 22, 13:35 UTC | May 23, 08:25 UTC | 18h 49m |
| 2026-05-22 | CSH857 | PVG → HKT | May 22, 11:35 UTC | May 23, 08:25 UTC | 20h 50m |
| 2026-05-21 | CSH857 | PVG → HKT | May 21, 17:35 UTC | May 22, 17:30 UTC | 23h 55m |
| 2026-05-21 | CSH857 | PVG → HKT | May 21, 16:45 UTC | May 22, 14:05 UTC | 21h 20m |
| 2026-05-21 | CSH857 | PVG → HKT | May 21, 13:35 UTC | May 22, 13:30 UTC | 23h 55m |
| 2026-05-16 | CSH832 | HKT → PVG | May 16, 13:35 UTC | May 17, 09:05 UTC | 19h 30m |
| 2026-05-16 | CSH831 | PVG → HKT | May 16, 11:55 UTC | May 17, 09:05 UTC | 21h 10m |
| 2026-05-16 | CSH831 | PVG → HKT | May 16, 06:35 UTC | May 17, 04:20 UTC | 21h 45m |
| 2026-05-16 | CSH831 | PVG → HKT | May 16, 03:10 UTC | May 16, 20:15 UTC | 17h 6m |
| 2026-05-15 | CSH831 | PVG → HKT | May 15, 15:45 UTC | May 16, 14:16 UTC | 22h 31m |
| 2026-05-15 | CSH866 | KUL → PVG | May 15, 12:30 UTC | May 16, 06:45 UTC | 18h 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-20AY page for operator, model, and routing details .