sensors Mode-S transponder
7820B5
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-225G · BOEING 737 MAX 8
- Hex
- 7820B5
- Octal
- 36020265
- Decimal
- 7,872,693
- Country
- CN
- Tail
- B-225G
- Type
- B38M
- Flights observed
- 51
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 56m ago
Last known position
Country allocation
The ICAO 24-bit address 7820B5 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 |
|---|---|---|---|
| CSH862 | Shanghai Airlines | 4 | 2026-04-27 |
| CSH861 | Shanghai Airlines | 4 | 2026-04-27 |
| CSH831 | Shanghai Airlines | 4 | 2026-04-29 |
| CSH856 | - | 3 | 2026-04-18 |
| CSH855 | Shanghai Airlines | 3 | 2026-04-18 |
| CSH853 | Shanghai Airlines | 3 | 2026-05-22 |
| CSH842 | Shanghai Airlines | 3 | 2026-05-19 |
| CSH841 | Shanghai Airlines | 3 | 2026-04-26 |
| CSH9256 | - | 2 | 2026-04-14 |
| CSH9068 | Shanghai Airlines | 2 | 2026-05-06 |
| CSH832 | Shanghai Airlines | 2 | 2026-05-23 |
| CSH9540 | Shanghai Airlines | 1 | 2026-04-16 |
| CSH9539 | Shanghai Airlines | 1 | 2026-04-16 |
| CSH9255 | Shanghai Airlines | 1 | 2026-05-02 |
| CSH9088 | Shanghai Airlines | 1 | 2026-04-13 |
| CSH877 | Shanghai Airlines | 1 | 2026-05-05 |
| CSH868 | Shanghai Airlines | 1 | 2026-05-27 |
| CSH867 | Shanghai Airlines | 1 | 2026-05-27 |
| CSH866 | Shanghai Airlines | 1 | 2026-04-28 |
| CSH865 | Shanghai Airlines | 1 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | CSH864 | KUL → PVG | May 29, 23:20 UTC | May 30, 03:15 UTC | 3h 55m |
| 2026-05-29 | CSH863 | PVG → KUL | May 29, 17:20 UTC | May 29, 21:50 UTC | 4h 30m |
| 2026-05-27 | CSH868 | BKI → PVG | May 27, 18:10 UTC | May 27, 20:40 UTC | 2h 30m |
| 2026-05-27 | CSH867 | PVG → BKI | May 27, 16:05 UTC | May 27, 16:30 UTC | 25m |
| 2026-05-23 | CSH832 | HKT → PVG | May 23, 03:20 UTC | May 23, 20:10 UTC | 16h 51m |
| 2026-05-22 | CSH853 | PVG → BKK | May 22, 12:50 UTC | May 22, 15:10 UTC | 2h 20m |
| 2026-05-19 | CSH842 | BKK → PVG | May 19, 03:55 UTC | May 19, 06:10 UTC | 2h 15m |
| 2026-05-18 | CSH853 | PVG → BKK | May 18, 06:20 UTC | May 18, 14:40 UTC | 8h 20m |
| 2026-05-18 | CSH811 | PVG → HKG | May 18, 02:55 UTC | May 18, 04:11 UTC | 1h 15m |
| 2026-05-13 | CSH840 | BKK → PVG | May 13, 15:10 UTC | May 13, 18:05 UTC | 2h 55m |
| 2026-05-13 | CSH839 | PVG → BKK | May 13, 11:20 UTC | May 13, 13:50 UTC | 2h 30m |
| 2026-05-08 | CSH858 | HKT → PVG | May 8, 11:19 UTC | May 8, 19:15 UTC | 7h 55m |
| 2026-05-06 | CSH9068 | CGQ → PVG | May 6, 13:25 UTC | May 7, 04:55 UTC | 15h 30m |
| 2026-05-05 | CSH877 | PVG → PEN | May 5, 19:45 UTC | May 6, 13:55 UTC | 18h 10m |
| 2026-05-03 | CSH842 | BKK → PVG | May 3, 03:05 UTC | May 3, 03:40 UTC | 34m |
| 2026-05-02 | CSH853 | PVG → BKK | May 2, 06:35 UTC | May 2, 14:40 UTC | 8h 5m |
| 2026-05-02 | CSH9255 | PVG → HAK | May 2, 03:25 UTC | May 2, 03:40 UTC | 15m |
| 2026-04-29 | CSH832 | HKT → PVG | Apr 29, 14:10 UTC | Apr 30, 08:05 UTC | 17h 54m |
| 2026-04-29 | CSH831 | PVG → HKT | Apr 29, 12:15 UTC | Apr 30, 08:05 UTC | 19h 49m |
| 2026-04-28 | CSH831 | PVG → HKT | Apr 28, 16:00 UTC | Apr 29, 15:00 UTC | 23h 0m |
| 2026-04-28 | CSH866 | KUL → PVG | Apr 28, 12:45 UTC | Apr 28, 16:00 UTC | 3h 15m |
| 2026-04-28 | CSH865 | PVG → KUL | Apr 28, 10:40 UTC | Apr 28, 11:10 UTC | 30m |
| 2026-04-27 | CSH862 | KUL → PVG | Apr 27, 19:00 UTC | Apr 28, 07:00 UTC | 12h 0m |
| 2026-04-27 | CSH861 | PVG → KUL | Apr 27, 05:15 UTC | Apr 27, 16:20 UTC | 11h 5m |
| 2026-04-26 | CSH841 | CGQ → PVG | Apr 26, 11:10 UTC | Apr 26, 18:40 UTC | 7h 30m |
| 2026-04-25 | CSH841 | CGQ → PVG | Apr 25, 17:35 UTC | Apr 26, 16:30 UTC | 22h 55m |
| 2026-04-25 | CSH9068 | CGQ → PVG | Apr 25, 17:10 UTC | Apr 26, 11:30 UTC | 18h 20m |
| 2026-04-25 | CSH842 | BKK → PVG | Apr 25, 03:00 UTC | Apr 25, 17:35 UTC | 14h 35m |
| 2026-04-23 | CSH848 | BKK → PVG | Apr 23, 22:10 UTC | Apr 24, 15:10 UTC | 17h 0m |
| 2026-04-23 | CSH847 | PVG → BKK | Apr 23, 02:30 UTC | Apr 23, 20:45 UTC | 18h 15m |
| 2026-04-19 | CSH831 | PVG → HKT | Apr 19, 03:05 UTC | Apr 19, 20:20 UTC | 17h 15m |
| 2026-04-18 | CSH831 | PVG → HKT | Apr 18, 15:30 UTC | Apr 19, 14:30 UTC | 23h 0m |
| 2026-04-18 | CSH856 | - | Apr 18, 13:20 UTC | Apr 19, 12:10 UTC | 22h 50m |
| 2026-04-18 | CSH855 | PVG → BKK | Apr 18, 11:40 UTC | Apr 18, 11:55 UTC | 15m |
| 2026-04-17 | CSH862 | KUL → PVG | Apr 17, 21:50 UTC | Apr 17, 22:45 UTC | 55m |
| 2026-04-17 | CSH862 | KUL → PVG | Apr 17, 20:00 UTC | Apr 17, 20:10 UTC | 10m |
| 2026-04-17 | CSH862 | KUL → PVG | Apr 17, 18:45 UTC | Apr 18, 09:35 UTC | 14h 51m |
| 2026-04-17 | CSH861 | - | Apr 17, 15:50 UTC | Apr 17, 16:25 UTC | 35m |
| 2026-04-17 | CSH861 | - | Apr 17, 14:50 UTC | Apr 17, 15:05 UTC | 14m |
| 2026-04-17 | CSH861 | - | Apr 17, 12:00 UTC | Apr 17, 12:40 UTC | 40m |
| 2026-04-17 | CSH854 | BKK → PVG | Apr 17, 05:20 UTC | Apr 17, 05:30 UTC | 10m |
| 2026-04-16 | CSH841 | CGQ → PVG | Apr 16, 16:25 UTC | Apr 16, 16:35 UTC | 10m |
| 2026-04-16 | CSH9540 | SYX → PVG | Apr 16, 08:04 UTC | Apr 16, 08:15 UTC | 10m |
| 2026-04-16 | CSH9539 | PVG → SYX | Apr 16, 03:09 UTC | Apr 16, 04:29 UTC | 1h 20m |
| 2026-04-14 | CSH9256 | - | Apr 14, 07:10 UTC | Apr 14, 07:30 UTC | 20m |
| 2026-04-14 | CSH9256 | - | Apr 14, 06:25 UTC | Apr 14, 07:10 UTC | 45m |
| 2026-04-13 | CSH856 | - | Apr 13, 14:40 UTC | Apr 13, 14:50 UTC | 10m |
| 2026-04-13 | CSH856 | - | Apr 13, 12:35 UTC | Apr 13, 12:50 UTC | 15m |
| 2026-04-13 | CSH855 | - | Apr 13, 10:40 UTC | Apr 13, 11:00 UTC | 20m |
| 2026-04-13 | CSH855 | - | Apr 13, 08:35 UTC | Apr 13, 08:55 UTC | 20m |
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-225G page for operator, model, and routing details .