sensors Mode-S transponder
78062B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6660 · AIRBUS A-321
- Hex
- 78062B
- Octal
- 36003053
- Decimal
- 7,865,899
- Country
- CN
- Tail
- B-6660
- Type
- A321
- Flights observed
- 34
- Distinct callsigns
- 17
- Country
- CN
- Last broadcast
- 30m ago
Last known position
Country allocation
The ICAO 24-bit address 78062B 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSN5811 | China Southern Airlines | 8 | 2026-05-25 |
| CSN6505 | China Southern Airlines | 4 | 2026-05-06 |
| CSN6456 | China Southern Airlines | 3 | 2026-04-26 |
| CSN6674 | China Southern Airlines | 2 | 2026-05-01 |
| CSN6519 | China Southern Airlines | 2 | 2026-05-14 |
| CSN6347 | China Southern Airlines | 2 | 2026-05-26 |
| CSN6339 | China Southern Airlines | 2 | 2026-05-17 |
| CSN6301 | China Southern Airlines | 2 | 2026-04-20 |
| CSN8874 | China Southern Airlines | 1 | 2026-05-30 |
| CSN6529 | China Southern Airlines | 1 | 2026-05-07 |
| CSN6517 | China Southern Airlines | 1 | 2026-04-28 |
| CSN6403 | China Southern Airlines | 1 | 2026-04-21 |
| CSN6380 | China Southern Airlines | 1 | 2026-04-30 |
| CSN6367 | China Southern Airlines | 1 | 2026-05-10 |
| CSN6316 | China Southern Airlines | 1 | 2026-04-21 |
| CSN6315 | China Southern Airlines | 1 | 2026-04-21 |
| CSN5817 | China Southern Airlines | 1 | 2026-05-14 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | CSN8874 | PKX → SHE | May 30, 04:35 UTC | May 30, 04:45 UTC | 10m |
| 2026-05-26 | CSN6347 | SHE → CAN | May 26, 04:30 UTC | May 26, 11:39 UTC | 7h 10m |
| 2026-05-25 | CSN5811 | SHE → HGH | May 25, 04:05 UTC | May 25, 04:45 UTC | 40m |
| 2026-05-24 | CSN5811 | SHE → HGH | May 24, 04:50 UTC | May 25, 04:45 UTC | 23h 55m |
| 2026-05-24 | CSN5811 | SHE → HGH | May 24, 04:20 UTC | May 24, 05:00 UTC | 40m |
| 2026-05-23 | CSN5811 | SHE → HGH | May 23, 04:55 UTC | May 24, 04:30 UTC | 23h 36m |
| 2026-05-23 | CSN5811 | SHE → HGH | May 23, 04:20 UTC | May 23, 04:55 UTC | 35m |
| 2026-05-22 | CSN5811 | SHE → HGH | May 22, 04:50 UTC | May 23, 04:45 UTC | 23h 54m |
| 2026-05-21 | CSN6347 | SHE → CAN | May 21, 12:40 UTC | May 22, 04:50 UTC | 16h 10m |
| 2026-05-17 | CSN6339 | SHE → CAN | May 17, 11:25 UTC | May 17, 11:55 UTC | 30m |
| 2026-05-14 | CSN6519 | SHE → PVG | May 14, 09:25 UTC | May 15, 04:40 UTC | 19h 15m |
| 2026-05-14 | CSN5817 | CSX → CKG | May 14, 00:30 UTC | May 14, 10:00 UTC | 9h 30m |
| 2026-05-10 | CSN6367 | SHE → CAN | May 10, 05:55 UTC | May 10, 06:04 UTC | 10m |
| 2026-05-07 | CSN6529 | SHE → NGB | May 7, 00:55 UTC | May 7, 01:10 UTC | 15m |
| 2026-05-06 | CSN6505 | SHE → PVG | May 6, 01:30 UTC | May 6, 01:55 UTC | 25m |
| 2026-05-04 | CSN6505 | SHE → PVG | May 4, 04:15 UTC | May 5, 01:50 UTC | 21h 36m |
| 2026-05-03 | CSN5811 | SHE → HGH | May 3, 04:10 UTC | May 3, 04:45 UTC | 35m |
| 2026-05-01 | CSN6674 | TFU → SHE | May 1, 12:35 UTC | May 2, 01:55 UTC | 13h 20m |
| 2026-04-30 | CSN6674 | TFU → SHE | Apr 30, 15:50 UTC | May 1, 12:50 UTC | 21h 0m |
| 2026-04-30 | CSN6380 | CSX → SHE | Apr 30, 02:05 UTC | Apr 30, 16:00 UTC | 13h 56m |
| 2026-04-28 | CSN6517 | SHE → XMN | Apr 28, 14:30 UTC | Apr 29, 02:55 UTC | 12h 25m |
| 2026-04-28 | CSN6505 | SHE → PVG | Apr 28, 01:35 UTC | Apr 28, 14:30 UTC | 12h 55m |
| 2026-04-26 | CSN6456 | XIY → SHE | Apr 26, 01:35 UTC | Apr 26, 14:55 UTC | 13h 20m |
| 2026-04-24 | CSN6456 | XIY → SHE | Apr 24, 01:45 UTC | Apr 24, 14:30 UTC | 12h 45m |
| 2026-04-21 | CSN6403 | SHE → CKG | Apr 21, 13:10 UTC | Apr 22, 01:30 UTC | 12h 20m |
| 2026-04-21 | CSN6315 | SHE → CAN | Apr 21, 02:25 UTC | Apr 21, 06:30 UTC | 4h 5m |
| 2026-04-21 | CSN6316 | CAN → SHE | Apr 21, 00:10 UTC | Apr 21, 00:25 UTC | 15m |
| 2026-04-20 | CSN6339 | SHE → CAN | Apr 20, 14:30 UTC | Apr 20, 14:45 UTC | 15m |
| 2026-04-20 | CSN6301 | SHE → CAN | Apr 20, 01:00 UTC | Apr 20, 12:05 UTC | 11h 5m |
| 2026-04-19 | CSN6301 | SHE → CAN | Apr 19, 14:30 UTC | Apr 20, 12:05 UTC | 21h 35m |
| 2026-04-19 | CSN6456 | XIY → SHE | Apr 19, 01:20 UTC | Apr 19, 14:45 UTC | 13h 25m |
| 2026-04-18 | CSN6505 | SHE → PVG | Apr 18, 12:00 UTC | Apr 19, 02:00 UTC | 14h 0m |
| 2026-04-15 | CSN6519 | SHE → PVG | Apr 15, 11:40 UTC | Apr 15, 12:05 UTC | 25m |
| 2026-04-13 | CSN5811 | SHE → HGH | Apr 13, 04:15 UTC | Apr 13, 04:55 UTC | 40m |
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-6660 page for operator, model, and routing details .