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
- 87
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3d 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 |
|---|---|---|---|
| CSH877 | - | 8 | 2026-07-10 |
| CSH861 | - | 7 | 2026-07-08 |
| CSH862 | - | 6 | 2026-07-08 |
| CSH878 | - | 5 | 2026-07-11 |
| CSH858 | Shanghai Airlines | 5 | 2026-06-14 |
| CSH853 | - | 5 | 2026-06-27 |
| CSH841 | - | 5 | 2026-06-15 |
| CSH831 | Shanghai Airlines | 4 | 2026-04-29 |
| CSH811 | - | 4 | 2026-06-26 |
| CSH868 | - | 3 | 2026-07-05 |
| CSH856 | - | 3 | 2026-04-18 |
| CSH855 | Shanghai Airlines | 3 | 2026-04-18 |
| CSH842 | Shanghai Airlines | 3 | 2026-05-19 |
| CSH9256 | - | 2 | 2026-04-14 |
| CSH9068 | Shanghai Airlines | 2 | 2026-05-06 |
| CSH866 | Shanghai Airlines | 2 | 2026-05-30 |
| CSH865 | Shanghai Airlines | 2 | 2026-05-29 |
| CSH854 | Shanghai Airlines | 2 | 2026-06-06 |
| CSH840 | Shanghai Airlines | 2 | 2026-06-16 |
| CSH839 | Shanghai Airlines | 2 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | CSH878 | - | Jul 11, 00:30 UTC | Jul 11, 00:40 UTC | 10m |
| 2026-07-10 | CSH877 | - | Jul 10, 22:40 UTC | Jul 10, 22:50 UTC | 10m |
| 2026-07-10 | CSH877 | - | Jul 10, 19:35 UTC | Jul 10, 20:15 UTC | 40m |
| 2026-07-08 | CSH862 | - | Jul 8, 18:00 UTC | Jul 8, 22:25 UTC | 4h 25m |
| 2026-07-08 | CSH861 | - | Jul 8, 15:40 UTC | Jul 8, 16:00 UTC | 20m |
| 2026-07-08 | CSH861 | - | Jul 8, 04:00 UTC | Jul 8, 13:00 UTC | 9h 0m |
| 2026-07-08 | CSH878 | - | Jul 8, 00:50 UTC | Jul 8, 01:00 UTC | 10m |
| 2026-07-07 | CSH877 | - | Jul 7, 23:15 UTC | Jul 7, 23:25 UTC | 10m |
| 2026-07-07 | CSH878 | - | Jul 7, 03:55 UTC | Jul 7, 20:50 UTC | 16h 55m |
| 2026-07-07 | CSH878 | - | Jul 7, 00:35 UTC | Jul 7, 00:45 UTC | 10m |
| 2026-07-06 | CSH877 | - | Jul 6, 22:50 UTC | Jul 6, 23:05 UTC | 15m |
| 2026-07-06 | CSH877 | - | Jul 6, 19:45 UTC | Jul 6, 20:35 UTC | 50m |
| 2026-07-05 | CSH868 | - | Jul 5, 17:25 UTC | Jul 5, 19:50 UTC | 2h 25m |
| 2026-07-05 | CSH868 | - | Jul 5, 03:30 UTC | Jul 5, 16:05 UTC | 12h 35m |
| 2026-06-28 | CSH862 | - | Jun 28, 18:10 UTC | Jun 28, 22:24 UTC | 4h 15m |
| 2026-06-28 | CSH861 | - | Jun 28, 04:59 UTC | Jun 28, 16:19 UTC | 11h 20m |
| 2026-06-27 | CSH853 | HKG → BKK | Jun 27, 07:04 UTC | Jun 27, 14:35 UTC | 7h 30m |
| 2026-06-26 | CSH811 | - | Jun 26, 12:14 UTC | Jun 27, 04:29 UTC | 16h 15m |
| 2026-06-25 | CSH878 | - | Jun 25, 03:50 UTC | Jun 25, 04:54 UTC | 1h 5m |
| 2026-06-24 | CSH877 | - | Jun 24, 22:29 UTC | Jun 24, 22:45 UTC | 15m |
| 2026-06-24 | CSH877 | - | Jun 24, 20:05 UTC | Jun 24, 20:30 UTC | 25m |
| 2026-06-16 | CSH840 | BKK → PVG | Jun 16, 15:30 UTC | Jun 16, 17:49 UTC | 2h 20m |
| 2026-06-16 | CSH839 | PVG → BKK | Jun 16, 03:04 UTC | Jun 16, 14:00 UTC | 10h 55m |
| 2026-06-15 | CSH841 | - | Jun 15, 10:24 UTC | Jun 15, 18:10 UTC | 7h 45m |
| 2026-06-14 | CSH841 | - | Jun 14, 19:20 UTC | Jun 15, 18:10 UTC | 22h 49m |
| 2026-06-14 | CSH858 | HKT → PVG | Jun 14, 17:20 UTC | Jun 15, 16:49 UTC | 23h 29m |
| 2026-06-14 | CSH858 | HKT → PVG | Jun 14, 16:50 UTC | Jun 15, 10:24 UTC | 17h 34m |
| 2026-06-14 | CSH858 | HKT → PVG | Jun 14, 13:20 UTC | Jun 15, 10:24 UTC | 21h 5m |
| 2026-06-14 | CSH858 | HKT → PVG | Jun 14, 11:55 UTC | Jun 15, 10:24 UTC | 22h 29m |
| 2026-06-06 | CSH854 | BKK → PVG | Jun 6, 04:55 UTC | Jun 6, 07:05 UTC | 2h 10m |
| 2026-06-05 | CSH853 | PVG → BKK | Jun 5, 06:10 UTC | Jun 5, 14:55 UTC | 8h 45m |
| 2026-06-05 | CSH811 | PVG → HKG | Jun 5, 03:55 UTC | Jun 5, 04:10 UTC | 15m |
| 2026-06-05 | CSH811 | PVG → HKG | Jun 5, 02:55 UTC | Jun 5, 03:20 UTC | 25m |
| 2026-06-01 | CSH834 | BKK → PVG | Jun 1, 10:05 UTC | Jun 2, 03:40 UTC | 17h 35m |
| 2026-06-01 | CSH833 | PVG → BKK | Jun 1, 06:00 UTC | Jun 1, 08:15 UTC | 2h 15m |
| 2026-05-30 | CSH866 | KUL → PVG | May 30, 12:35 UTC | May 30, 17:00 UTC | 4h 25m |
| 2026-05-29 | CSH865 | PVG → KUL | May 29, 23:20 UTC | May 30, 11:15 UTC | 11h 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 |
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 .