sensors Mode-S transponder
7820A5
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-225E · BOEING 737 MAX 8
- Hex
- 7820A5
- Octal
- 36020245
- Decimal
- 7,872,677
- Country
- CN
- Tail
- B-225E
- Type
- B38M
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 7820A5 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 |
|---|---|---|---|
| CSN8894 | - | 5 | 2026-06-13 |
| CSN8893 | - | 5 | 2026-06-13 |
| CSN6906 | - | 3 | 2026-07-12 |
| CSN6890 | China Southern Airlines | 3 | 2026-06-04 |
| CSN8891 | - | 2 | 2026-06-20 |
| CSN6905 | - | 2 | 2026-07-12 |
| CSN6889 | China Southern Airlines | 2 | 2026-05-11 |
| CSN5603 | - | 2 | 2026-07-08 |
| CSN8924 | China Southern Airlines | 1 | 2026-05-01 |
| CSN8923 | China Southern Airlines | 1 | 2026-05-01 |
| CSN8892 | - | 1 | 2026-07-06 |
| CSN8189 | - | 1 | 2026-06-24 |
| CSN6914 | China Southern Airlines | 1 | 2026-06-06 |
| CSN6913 | China Southern Airlines | 1 | 2026-06-05 |
| CSN6912 | China Southern Airlines | 1 | 2026-06-05 |
| CSN6911 | China Southern Airlines | 1 | 2026-06-05 |
| CSN6902 | China Southern Airlines | 1 | 2026-05-04 |
| CSN6901 | China Southern Airlines | 1 | 2026-05-04 |
| CSN6894 | - | 1 | 2026-07-02 |
| CSN6893 | - | 1 | 2026-07-01 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | CSN6906 | - | Jul 12, 12:55 UTC | Jul 12, 13:15 UTC | 20m |
| 2026-07-12 | CSN6905 | - | Jul 12, 10:30 UTC | Jul 12, 10:45 UTC | 15m |
| 2026-07-09 | CSN6906 | - | Jul 9, 12:55 UTC | Jul 9, 13:20 UTC | 25m |
| 2026-07-09 | CSN6905 | - | Jul 9, 10:45 UTC | Jul 9, 11:00 UTC | 15m |
| 2026-07-08 | CSN5603 | - | Jul 8, 03:55 UTC | Jul 8, 04:10 UTC | 15m |
| 2026-07-06 | CSN8892 | - | Jul 6, 07:55 UTC | Jul 6, 08:05 UTC | 10m |
| 2026-07-02 | CSN6894 | - | Jul 2, 00:55 UTC | Jul 2, 01:10 UTC | 15m |
| 2026-07-01 | CSN6893 | - | Jul 1, 13:30 UTC | Jul 1, 14:05 UTC | 35m |
| 2026-06-24 | CSN8189 | - | Jun 24, 16:54 UTC | Jun 24, 21:34 UTC | 4h 40m |
| 2026-06-20 | CSN8891 | - | Jun 20, 04:39 UTC | Jun 20, 04:49 UTC | 10m |
| 2026-06-13 | CSN8894 | - | Jun 13, 07:45 UTC | Jun 13, 07:55 UTC | 10m |
| 2026-06-13 | CSN8893 | - | Jun 13, 05:10 UTC | Jun 13, 05:30 UTC | 20m |
| 2026-06-09 | CSN8894 | - | Jun 9, 07:45 UTC | Jun 9, 08:05 UTC | 20m |
| 2026-06-09 | CSN8893 | - | Jun 9, 05:00 UTC | Jun 9, 05:15 UTC | 15m |
| 2026-06-08 | CSN8894 | - | Jun 8, 07:50 UTC | Jun 9, 05:15 UTC | 21h 25m |
| 2026-06-08 | CSN8893 | - | Jun 8, 05:00 UTC | Jun 8, 05:15 UTC | 15m |
| 2026-06-06 | CSN6914 | PKX → URC | Jun 6, 00:15 UTC | Jun 6, 00:40 UTC | 25m |
| 2026-06-05 | CSN6913 | URC → PKX | Jun 5, 14:25 UTC | Jun 5, 14:40 UTC | 15m |
| 2026-06-05 | CSN6912 | PKX → URC | Jun 5, 06:25 UTC | Jun 5, 06:50 UTC | 25m |
| 2026-06-05 | CSN6911 | URC → PKX | Jun 5, 04:00 UTC | Jun 5, 04:15 UTC | 15m |
| 2026-06-04 | CSN6890 | SZX → URC | Jun 4, 10:05 UTC | Jun 4, 10:20 UTC | 15m |
| 2026-05-27 | CSN8894 | - | May 27, 09:10 UTC | May 27, 09:25 UTC | 15m |
| 2026-05-27 | CSN8893 | - | May 27, 05:59 UTC | May 27, 06:09 UTC | 10m |
| 2026-05-19 | CSN8891 | KHG → PKX | May 19, 06:15 UTC | May 19, 06:30 UTC | 15m |
| 2026-05-11 | CSN6890 | SZX → URC | May 11, 09:45 UTC | May 11, 10:00 UTC | 15m |
| 2026-05-11 | CSN6889 | URC → SZX | May 11, 07:30 UTC | May 11, 07:45 UTC | 15m |
| 2026-05-08 | CSN6890 | SZX → URC | May 8, 10:04 UTC | May 8, 10:14 UTC | 10m |
| 2026-05-08 | CSN6889 | URC → SZX | May 8, 07:44 UTC | May 8, 07:55 UTC | 10m |
| 2026-05-04 | CSN6902 | PKX → URC | May 4, 07:30 UTC | May 4, 07:55 UTC | 25m |
| 2026-05-04 | CSN6901 | URC → PKX | May 4, 04:50 UTC | May 4, 05:05 UTC | 15m |
| 2026-05-01 | CSN8924 | XNN → PKX | May 1, 08:30 UTC | May 1, 08:40 UTC | 10m |
| 2026-05-01 | CSN8923 | URC → SZX | May 1, 06:20 UTC | May 1, 06:30 UTC | 10m |
| 2026-04-30 | CSN8894 | - | Apr 30, 07:50 UTC | Apr 30, 08:15 UTC | 25m |
| 2026-04-30 | CSN8893 | - | Apr 30, 05:00 UTC | Apr 30, 05:15 UTC | 15m |
| 2026-04-27 | CSN5603 | - | Apr 27, 03:25 UTC | Apr 27, 03:40 UTC | 15m |
| 2026-04-21 | CSN6906 | PKX → URC | Apr 21, 12:55 UTC | Apr 21, 13:20 UTC | 25m |
| 2026-04-14 | CSN6014 | URC → CAN | Apr 14, 21:20 UTC | Apr 14, 21:40 UTC | 20m |
| 2026-04-14 | CSN6013 | URC → NQZ | Apr 14, 16:55 UTC | Apr 14, 17:30 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-225E page for operator, model, and routing details .