sensors Mode-S transponder
780F7A
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8425 · AIRBUS A-321
- Hex
- 780F7A
- Octal
- 36007572
- Decimal
- 7,868,282
- Country
- CN
- Tail
- B-8425
- Type
- A321
- Flights observed
- 31
- Distinct callsigns
- 15
- Country
- CN
- Last broadcast
- 17h ago
Current position
Country allocation
The ICAO 24-bit address 780F7A 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSN3836 | China Southern Airlines | 10 | 2026-05-17 |
| CSN6630 | China Southern Airlines | 3 | 2026-05-07 |
| CSN6629 | China Southern Airlines | 3 | 2026-05-26 |
| CSN6754 | China Southern Airlines | 2 | 2026-05-10 |
| CSN6744 | China Southern Airlines | 2 | 2026-04-27 |
| CSN3835 | China Southern Airlines | 2 | 2026-05-16 |
| CSN6765 | China Southern Airlines | 1 | 2026-04-24 |
| CSN6757 | China Southern Airlines | 1 | 2026-05-10 |
| CSN6740 | China Southern Airlines | 1 | 2026-05-28 |
| CSN6736 | China Southern Airlines | 1 | 2026-05-17 |
| CSN6734 | China Southern Airlines | 1 | 2026-04-16 |
| CSN6498 | China Southern Airlines | 1 | 2026-05-22 |
| CSN6190 | China Southern Airlines | 1 | 2026-05-29 |
| CSN3978 | China Southern Airlines | 1 | 2026-05-23 |
| CSN3516 | China Southern Airlines | 1 | 2026-04-23 |
Recent flights last 31
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | CSN6190 | TFU → SYX | May 29, 00:10 UTC | May 29, 12:35 UTC | 12h 25m |
| 2026-05-28 | CSN6740 | CAN → SYX | May 28, 06:50 UTC | May 28, 10:20 UTC | 3h 30m |
| 2026-05-26 | CSN6629 | SYX → HGH | May 26, 06:49 UTC | May 26, 12:30 UTC | 5h 40m |
| 2026-05-23 | CSN3978 | SZX → SYX | May 23, 01:35 UTC | May 23, 01:45 UTC | 10m |
| 2026-05-22 | CSN6498 | SYX → SZX | May 22, 18:00 UTC | May 22, 18:10 UTC | 10m |
| 2026-05-17 | CSN6736 | CAN → SYX | May 17, 15:45 UTC | May 18, 06:25 UTC | 14h 40m |
| 2026-05-17 | CSN3836 | PVG → SYX | May 17, 04:00 UTC | May 17, 10:35 UTC | 6h 35m |
| 2026-05-16 | CSN3835 | SYX → PVG | May 16, 05:35 UTC | May 17, 04:25 UTC | 22h 51m |
| 2026-05-10 | CSN6754 | PVG → SYX | May 10, 15:29 UTC | May 11, 07:00 UTC | 15h 30m |
| 2026-05-10 | CSN6757 | SYX → SZX | May 10, 13:40 UTC | May 10, 14:00 UTC | 20m |
| 2026-05-07 | CSN6630 | CGQ → HGH | May 7, 07:10 UTC | May 7, 12:45 UTC | 5h 35m |
| 2026-05-06 | CSN3836 | PVG → SYX | May 6, 10:35 UTC | May 7, 07:10 UTC | 20h 34m |
| 2026-05-06 | CSN3836 | PVG → SYX | May 6, 05:00 UTC | May 6, 10:50 UTC | 5h 50m |
| 2026-05-05 | CSN3835 | SYX → PVG | May 5, 10:55 UTC | May 6, 10:30 UTC | 23h 35m |
| 2026-05-03 | CSN3836 | PVG → SYX | May 3, 10:40 UTC | May 3, 10:50 UTC | 10m |
| 2026-04-30 | CSN6754 | PVG → SYX | Apr 30, 14:15 UTC | May 1, 06:55 UTC | 16h 40m |
| 2026-04-30 | CSN3836 | PVG → SYX | Apr 30, 05:25 UTC | May 1, 01:05 UTC | 19h 40m |
| 2026-04-29 | CSN3836 | PVG → SYX | Apr 29, 10:35 UTC | Apr 30, 05:25 UTC | 18h 49m |
| 2026-04-29 | CSN3836 | PVG → SYX | Apr 29, 05:50 UTC | Apr 29, 11:00 UTC | 5h 11m |
| 2026-04-28 | CSN3836 | PVG → SYX | Apr 28, 10:35 UTC | Apr 29, 06:29 UTC | 19h 55m |
| 2026-04-28 | CSN3836 | PVG → SYX | Apr 28, 05:15 UTC | Apr 28, 10:50 UTC | 5h 35m |
| 2026-04-27 | CSN6744 | CAN → SYX | Apr 27, 11:00 UTC | Apr 28, 10:30 UTC | 23h 30m |
| 2026-04-24 | CSN6765 | HAK → PVG | Apr 24, 10:05 UTC | Apr 24, 15:45 UTC | 5h 40m |
| 2026-04-23 | CSN3516 | PVG → HAK | Apr 23, 01:35 UTC | Apr 23, 07:01 UTC | 5h 26m |
| 2026-04-19 | CSN3836 | PVG → SYX | Apr 19, 05:20 UTC | Apr 19, 10:45 UTC | 5h 25m |
| 2026-04-18 | CSN6744 | CAN → SYX | Apr 18, 11:15 UTC | Apr 19, 10:30 UTC | 23h 15m |
| 2026-04-16 | CSN6734 | CAN → SYX | Apr 16, 06:20 UTC | Apr 16, 06:40 UTC | 20m |
| 2026-04-14 | CSN6630 | CGQ → HGH | Apr 14, 12:35 UTC | Apr 14, 12:45 UTC | 10m |
| 2026-04-14 | CSN6629 | SYX → HGH | Apr 14, 07:00 UTC | Apr 14, 07:10 UTC | 10m |
| 2026-04-13 | CSN6630 | - | Apr 13, 12:00 UTC | Apr 13, 12:15 UTC | 15m |
| 2026-04-13 | CSN6629 | SYX → HGH | Apr 13, 06:55 UTC | Apr 13, 07:10 UTC | 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-8425 page for operator, model, and routing details .