sensors Mode-S transponder
780D0F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1606 · AIRBUS A-321
- Hex
- 780D0F
- Octal
- 36006417
- Decimal
- 7,867,663
- Country
- CN
- Tail
- B-1606
- Type
- A321
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 780D0F 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 |
|---|---|---|---|
| CSN8100 | - | 2 | 2026-07-13 |
| CSN8099 | - | 2 | 2026-07-13 |
| CSN8086 | China Southern Airlines | 2 | 2026-07-05 |
| CSN8085 | China Southern Airlines | 2 | 2026-07-05 |
| CSN3602 | China Southern Airlines | 2 | 2026-04-20 |
| CSN8820 | - | 1 | 2026-07-04 |
| CSN8819 | - | 1 | 2026-07-04 |
| CSN8712 | China Southern Airlines | 1 | 2026-06-10 |
| CSN8212 | China Southern Airlines | 1 | 2026-06-04 |
| CSN6722 | - | 1 | 2026-06-29 |
| CSN6315 | - | 1 | 2026-07-12 |
| CSN6154 | China Southern Airlines | 1 | 2026-07-03 |
| CSN6153 | - | 1 | 2026-07-03 |
| CSN6059 | China Southern Airlines | 1 | 2026-04-13 |
| CSN5820 | China Southern Airlines | 1 | 2026-06-11 |
| CSN5819 | China Southern Airlines | 1 | 2026-06-11 |
| CSN3964 | China Southern Airlines | 1 | 2026-06-10 |
| CSN3963 | China Southern Airlines | 1 | 2026-06-10 |
| CSN3943 | China Southern Airlines | 1 | 2026-06-12 |
| CSN3812 | - | 1 | 2026-04-29 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CSN8100 | - | Jul 13, 06:55 UTC | Jul 13, 07:10 UTC | 15m |
| 2026-07-13 | CSN8099 | - | Jul 13, 04:50 UTC | Jul 13, 05:01 UTC | 10m |
| 2026-07-12 | CSN6315 | - | Jul 12, 02:25 UTC | Jul 12, 06:01 UTC | 3h 35m |
| 2026-07-06 | CSN3797 | - | Jul 6, 04:15 UTC | Jul 6, 04:25 UTC | 10m |
| 2026-07-05 | CSN8086 | HAN → SZX | Jul 5, 14:45 UTC | Jul 5, 14:55 UTC | 10m |
| 2026-07-05 | CSN8086 | HAN → SZX | Jul 5, 13:25 UTC | Jul 5, 13:55 UTC | 30m |
| 2026-07-05 | CSN8085 | SZX → HAN | Jul 5, 10:35 UTC | Jul 5, 11:10 UTC | 35m |
| 2026-07-05 | CSN8085 | SZX → HAN | Jul 5, 09:50 UTC | Jul 5, 10:00 UTC | 10m |
| 2026-07-05 | CSN3459 | - | Jul 5, 02:05 UTC | Jul 5, 02:15 UTC | 10m |
| 2026-07-04 | CSN8820 | - | Jul 4, 16:00 UTC | Jul 4, 16:10 UTC | 10m |
| 2026-07-04 | CSN8819 | - | Jul 4, 10:55 UTC | Jul 4, 11:05 UTC | 10m |
| 2026-07-04 | CSN3176 | - | Jul 4, 08:45 UTC | Jul 4, 09:00 UTC | 15m |
| 2026-07-03 | CSN3171 | - | Jul 3, 23:45 UTC | Jul 3, 23:55 UTC | 10m |
| 2026-07-03 | CSN6154 | NGB → SZX | Jul 3, 14:55 UTC | Jul 3, 20:15 UTC | 5h 20m |
| 2026-07-03 | CSN6153 | - | Jul 3, 14:05 UTC | Jul 3, 14:25 UTC | 20m |
| 2026-07-03 | CSN3798 | - | Jul 3, 11:55 UTC | Jul 3, 12:05 UTC | 10m |
| 2026-07-01 | CSN3676 | - | Jul 1, 16:35 UTC | Jul 1, 16:50 UTC | 15m |
| 2026-07-01 | CSN3062 | - | Jul 1, 07:50 UTC | Jul 1, 08:40 UTC | 50m |
| 2026-07-01 | CSN3061 | - | Jul 1, 05:30 UTC | Jul 1, 06:15 UTC | 45m |
| 2026-06-29 | CSN6722 | - | Jun 29, 13:30 UTC | Jun 29, 13:44 UTC | 15m |
| 2026-06-29 | CSN3770 | - | Jun 29, 00:54 UTC | Jun 29, 01:10 UTC | 15m |
| 2026-06-13 | CSN3124 | - | Jun 13, 04:10 UTC | Jun 13, 04:25 UTC | 15m |
| 2026-06-12 | CSN3943 | CSX → SYX | Jun 12, 12:55 UTC | Jun 12, 15:40 UTC | 2h 45m |
| 2026-06-11 | CSN3155 | SZX → PEK | Jun 11, 12:00 UTC | Jun 11, 12:10 UTC | 10m |
| 2026-06-11 | CSN5820 | TSN → SZX | Jun 11, 10:05 UTC | Jun 11, 10:15 UTC | 10m |
| 2026-06-11 | CSN5819 | SZX → TSN | Jun 11, 02:00 UTC | Jun 11, 02:15 UTC | 15m |
| 2026-06-10 | CSN3964 | TAO → SZX | Jun 10, 16:05 UTC | Jun 10, 16:30 UTC | 25m |
| 2026-06-10 | CSN3963 | SZX → TAO | Jun 10, 09:35 UTC | Jun 10, 09:50 UTC | 15m |
| 2026-06-10 | CSN8712 | HGH → SZX | Jun 10, 07:15 UTC | Jun 10, 07:35 UTC | 20m |
| 2026-06-05 | CSN8100 | BKK → CAN | Jun 5, 07:05 UTC | Jun 5, 08:45 UTC | 1h 40m |
| 2026-06-05 | CSN8099 | CAN → BKK | Jun 5, 04:55 UTC | Jun 5, 05:35 UTC | 40m |
| 2026-06-04 | CSN8212 | PVG → CAN | Jun 4, 17:50 UTC | Jun 4, 18:00 UTC | 10m |
| 2026-04-29 | CSN3508 | NKG → CAN | Apr 29, 16:35 UTC | Apr 29, 16:45 UTC | 10m |
| 2026-04-29 | CSN3812 | - | Apr 29, 07:15 UTC | Apr 29, 07:24 UTC | 10m |
| 2026-04-21 | CSN3497 | CAN → KMG | Apr 21, 23:30 UTC | Apr 21, 23:45 UTC | 15m |
| 2026-04-20 | CSN3602 | SHE → CAN | Apr 20, 09:10 UTC | Apr 20, 09:40 UTC | 30m |
| 2026-04-19 | CSN3602 | SHE → CAN | Apr 19, 12:00 UTC | Apr 20, 09:40 UTC | 21h 40m |
| 2026-04-13 | CSN6059 | CAN → PNH | Apr 13, 05:35 UTC | Apr 13, 05:45 UTC | 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-1606 page for operator, model, and routing details .