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
- 127
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 02:30 UTC
Last known 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSN3836 | - | 22 | 2026-07-22 |
| CSN6624 | - | 9 | 2026-07-05 |
| CSN6630 | - | 8 | 2026-07-24 |
| CSN8919 | - | 6 | 2026-07-01 |
| CSN6757 | - | 6 | 2026-07-15 |
| CSN6629 | China Southern Airlines | 6 | 2026-07-25 |
| CSN6758 | - | 5 | 2026-07-15 |
| CSN6754 | China Southern Airlines | 5 | 2026-07-23 |
| CSN6744 | - | 5 | 2026-07-17 |
| CSN3978 | - | 5 | 2026-07-13 |
| CSN6782 | - | 4 | 2026-07-07 |
| CSN6668 | - | 4 | 2026-07-12 |
| CSN3835 | China Southern Airlines | 4 | 2026-07-18 |
| CSN6623 | - | 3 | 2026-07-20 |
| CSN8920 | - | 2 | 2026-07-05 |
| CSN8276 | - | 2 | 2026-06-28 |
| CSN8208 | China Southern Airlines | 2 | 2026-06-18 |
| CSN6781 | - | 2 | 2026-07-06 |
| CSN6739 | China Southern Airlines | 2 | 2026-06-08 |
| CSN6736 | China Southern Airlines | 2 | 2026-07-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | CSN6629 | SYX → HGH | Jul 25, 06:50 UTC | Jul 26, 02:30 UTC | 19h 40m |
| 2026-07-25 | CSN6629 | SYX → HGH | Jul 25, 02:05 UTC | Jul 25, 13:40 UTC | 11h 35m |
| 2026-07-24 | CSN6630 | - | Jul 24, 12:40 UTC | Jul 25, 07:00 UTC | 18h 20m |
| 2026-07-24 | CSN6630 | - | Jul 24, 12:15 UTC | Jul 25, 07:00 UTC | 18h 45m |
| 2026-07-24 | CSN6630 | - | Jul 24, 07:45 UTC | Jul 25, 02:15 UTC | 18h 30m |
| 2026-07-24 | CSN6630 | - | Jul 24, 01:25 UTC | Jul 24, 13:00 UTC | 11h 35m |
| 2026-07-23 | CSN6754 | PVG → SYX | Jul 23, 06:40 UTC | Jul 24, 01:35 UTC | 18h 55m |
| 2026-07-22 | CSN6736 | CAN → SYX | Jul 22, 15:55 UTC | Jul 23, 07:15 UTC | 15h 20m |
| 2026-07-22 | CSN6735 | SYX → CAN | Jul 22, 13:50 UTC | Jul 22, 14:05 UTC | 15m |
| 2026-07-22 | CSN3836 | - | Jul 22, 05:00 UTC | Jul 22, 11:20 UTC | 6h 20m |
| 2026-07-21 | CSN3836 | - | Jul 21, 15:45 UTC | Jul 22, 11:20 UTC | 19h 35m |
| 2026-07-21 | CSN6743 | - | Jul 21, 08:55 UTC | Jul 21, 09:05 UTC | 10m |
| 2026-07-20 | CSN6623 | - | Jul 20, 11:05 UTC | Jul 21, 05:50 UTC | 18h 44m |
| 2026-07-20 | CSN6754 | PVG → SYX | Jul 20, 06:40 UTC | Jul 21, 05:50 UTC | 23h 9m |
| 2026-07-19 | CSN6753 | SYX → PVG | Jul 19, 01:00 UTC | Jul 19, 06:50 UTC | 5h 50m |
| 2026-07-18 | CSN6735 | SYX → CAN | Jul 18, 14:20 UTC | Jul 18, 14:30 UTC | 10m |
| 2026-07-18 | CSN3835 | SYX → PVG | Jul 18, 05:45 UTC | Jul 18, 11:20 UTC | 5h 35m |
| 2026-07-17 | CSN6744 | - | Jul 17, 11:20 UTC | Jul 18, 06:00 UTC | 18h 41m |
| 2026-07-16 | CSN6754 | - | Jul 16, 01:30 UTC | Jul 16, 07:40 UTC | 6h 10m |
| 2026-07-15 | CSN6758 | - | Jul 15, 19:15 UTC | Jul 15, 19:25 UTC | 10m |
| 2026-07-15 | CSN6757 | - | Jul 15, 15:10 UTC | Jul 15, 16:00 UTC | 50m |
| 2026-07-15 | CSN3836 | - | Jul 15, 02:15 UTC | Jul 15, 11:05 UTC | 8h 50m |
| 2026-07-14 | CSN3836 | - | Jul 14, 14:00 UTC | Jul 15, 11:05 UTC | 21h 4m |
| 2026-07-14 | CSN3836 | - | Jul 14, 10:55 UTC | Jul 15, 10:30 UTC | 23h 34m |
| 2026-07-14 | CSN6744 | - | Jul 14, 06:05 UTC | Jul 15, 02:15 UTC | 20h 9m |
| 2026-07-13 | CSN6744 | - | Jul 13, 16:35 UTC | Jul 14, 14:05 UTC | 21h 30m |
| 2026-07-13 | CSN3836 | - | Jul 13, 10:35 UTC | Jul 14, 06:05 UTC | 19h 30m |
| 2026-07-13 | CSN3836 | - | Jul 13, 05:25 UTC | Jul 13, 16:35 UTC | 11h 10m |
| 2026-07-13 | CSN3978 | - | Jul 13, 01:40 UTC | Jul 13, 01:55 UTC | 15m |
| 2026-07-12 | CSN3977 | - | Jul 12, 23:45 UTC | Jul 13, 00:01 UTC | 15m |
| 2026-07-12 | CSN6668 | - | Jul 12, 00:30 UTC | Jul 12, 12:35 UTC | 12h 5m |
| 2026-07-11 | CSN3836 | - | Jul 11, 02:05 UTC | Jul 11, 10:25 UTC | 8h 20m |
| 2026-07-10 | CSN3836 | - | Jul 10, 11:15 UTC | Jul 11, 10:25 UTC | 23h 10m |
| 2026-07-09 | CSN3978 | - | Jul 9, 03:05 UTC | Jul 9, 03:15 UTC | 10m |
| 2026-07-08 | CSN3835 | - | Jul 8, 05:25 UTC | Jul 8, 10:40 UTC | 5h 15m |
| 2026-07-07 | CSN6782 | - | Jul 7, 13:20 UTC | Jul 8, 10:40 UTC | 21h 20m |
| 2026-07-07 | CSN6782 | - | Jul 7, 09:15 UTC | Jul 8, 05:35 UTC | 20h 20m |
| 2026-07-07 | CSN3978 | - | Jul 7, 04:40 UTC | Jul 7, 04:50 UTC | 10m |
| 2026-07-06 | CSN6781 | - | Jul 6, 09:40 UTC | Jul 6, 15:40 UTC | 6h 0m |
| 2026-07-05 | CSN6624 | - | Jul 5, 09:25 UTC | Jul 6, 06:05 UTC | 20h 40m |
| 2026-07-05 | CSN8920 | - | Jul 5, 05:55 UTC | Jul 5, 09:30 UTC | 3h 35m |
| 2026-07-04 | CSN6732 | - | Jul 4, 04:45 UTC | Jul 4, 05:00 UTC | 15m |
| 2026-07-03 | CSN6624 | - | Jul 3, 06:35 UTC | Jul 3, 06:50 UTC | 15m |
| 2026-07-02 | CSN6623 | - | Jul 2, 09:20 UTC | Jul 3, 06:50 UTC | 21h 30m |
| 2026-07-01 | CSN8919 | - | Jul 1, 23:40 UTC | Jul 2, 10:15 UTC | 10h 35m |
| 2026-07-01 | CSN8919 | - | Jul 1, 07:25 UTC | Jul 2, 06:00 UTC | 22h 35m |
| 2026-07-01 | CSN8919 | - | Jul 1, 00:55 UTC | Jul 2, 00:10 UTC | 23h 15m |
| 2026-06-30 | CSN6758 | - | Jun 30, 15:30 UTC | Jun 30, 15:45 UTC | 15m |
| 2026-06-30 | CSN6757 | - | Jun 30, 13:55 UTC | Jun 30, 14:10 UTC | 15m |
| 2026-06-29 | CSN6758 | - | Jun 29, 15:39 UTC | Jun 29, 15:54 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 .