sensors Mode-S transponder
79A06D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-2408 · AIRBUS A-320
- Hex
- 79A06D
- Octal
- 36320155
- Decimal
- 7,970,925
- Country
- CN
- Tail
- B-2408
- Type
- A320
- Flights observed
- 61
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 79A06D 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 |
|---|---|---|---|
| CSN8258 | China Southern Airlines | 10 | 2026-05-06 |
| CSN371 | - | 5 | 2026-07-01 |
| CSN372 | China Southern Airlines | 4 | 2026-07-02 |
| CSN3481 | - | 4 | 2026-07-09 |
| CSN6710 | - | 3 | 2026-04-17 |
| CSN3868 | China Southern Airlines | 3 | 2026-06-26 |
| CSN8257 | China Southern Airlines | 2 | 2026-05-07 |
| CSN6595 | China Southern Airlines | 2 | 2026-05-29 |
| CSN3676 | - | 2 | 2026-06-23 |
| CSN3449 | - | 2 | 2026-06-27 |
| CSN6778 | China Southern Airlines | 1 | 2026-04-15 |
| CSN6744 | China Southern Airlines | 1 | 2026-05-09 |
| CSN6709 | - | 1 | 2026-04-17 |
| CSN6568 | - | 1 | 2026-06-28 |
| CSN6528 | China Southern Airlines | 1 | 2026-06-29 |
| CSN6290 | - | 1 | 2026-04-18 |
| CSN5839 | China Southern Airlines | 1 | 2026-06-13 |
| CSN5591 | - | 1 | 2026-07-13 |
| CSN5471 | - | 1 | 2026-07-16 |
| CSN3958 | - | 1 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | CSN5471 | - | Jul 16, 09:15 UTC | Jul 16, 09:25 UTC | 10m |
| 2026-07-14 | - | - | Jul 14, 09:05 UTC | Jul 14, 09:20 UTC | 15m |
| 2026-07-13 | CSN5591 | - | Jul 13, 10:50 UTC | Jul 13, 11:00 UTC | 10m |
| 2026-07-11 | CSN3874 | - | Jul 11, 09:20 UTC | Jul 11, 09:30 UTC | 10m |
| 2026-07-11 | CSN3958 | - | Jul 11, 01:05 UTC | Jul 11, 01:20 UTC | 15m |
| 2026-07-09 | CSN3481 | - | Jul 9, 23:30 UTC | Jul 9, 23:45 UTC | 15m |
| 2026-07-07 | CSN3481 | - | Jul 7, 23:10 UTC | Jul 7, 23:25 UTC | 15m |
| 2026-07-02 | CSN372 | HAN → CAN | Jul 2, 01:25 UTC | Jul 2, 01:55 UTC | 30m |
| 2026-07-01 | CSN371 | - | Jul 1, 14:25 UTC | Jul 1, 15:35 UTC | 1h 10m |
| 2026-06-29 | CSN6528 | TYN → CAN | Jun 29, 12:29 UTC | Jun 29, 12:39 UTC | 10m |
| 2026-06-29 | CSN372 | HAN → CAN | Jun 29, 01:44 UTC | Jun 29, 02:05 UTC | 20m |
| 2026-06-28 | CSN371 | - | Jun 28, 16:19 UTC | Jun 28, 16:55 UTC | 35m |
| 2026-06-28 | CSN6568 | - | Jun 28, 10:55 UTC | Jun 28, 11:04 UTC | 10m |
| 2026-06-27 | CSN3449 | - | Jun 27, 07:24 UTC | Jun 27, 08:10 UTC | 45m |
| 2026-06-27 | CSN3923 | - | Jun 27, 01:35 UTC | Jun 27, 02:14 UTC | 40m |
| 2026-06-26 | CSN3868 | JUH → CAN | Jun 26, 16:35 UTC | Jun 26, 16:49 UTC | 15m |
| 2026-06-24 | CSN3913 | - | Jun 24, 00:55 UTC | Jun 24, 01:04 UTC | 10m |
| 2026-06-23 | CSN3676 | - | Jun 23, 15:19 UTC | Jun 23, 16:05 UTC | 45m |
| 2026-06-22 | CSN3481 | - | Jun 22, 23:05 UTC | Jun 23, 00:04 UTC | 1h 0m |
| 2026-06-21 | CSN3676 | - | Jun 21, 15:09 UTC | Jun 21, 15:44 UTC | 35m |
| 2026-06-15 | CSN3481 | CAN → DLU | Jun 15, 23:39 UTC | Jun 16, 00:00 UTC | 20m |
| 2026-06-15 | CSN3806 | - | Jun 15, 14:30 UTC | Jun 15, 14:40 UTC | 10m |
| 2026-06-14 | CSN3868 | JUH → CAN | Jun 14, 20:05 UTC | Jun 14, 20:25 UTC | 20m |
| 2026-06-13 | CSN5839 | CAN → WHA | Jun 13, 08:05 UTC | Jun 13, 08:15 UTC | 10m |
| 2026-06-12 | CSN372 | HAN → CAN | Jun 12, 01:35 UTC | Jun 12, 02:00 UTC | 25m |
| 2026-06-11 | CSN371 | PEK → CAN | Jun 11, 14:30 UTC | Jun 11, 15:30 UTC | 1h 0m |
| 2026-06-11 | CSN372 | HAN → CAN | Jun 11, 01:30 UTC | Jun 11, 01:55 UTC | 25m |
| 2026-06-10 | CSN371 | PEK → CAN | Jun 10, 14:15 UTC | Jun 10, 15:30 UTC | 1h 15m |
| 2026-06-04 | CSN3329 | CAN → ZHA | Jun 4, 15:30 UTC | Jun 4, 15:40 UTC | 10m |
| 2026-06-02 | CSN3810 | - | Jun 2, 13:10 UTC | Jun 2, 13:20 UTC | 10m |
| 2026-05-29 | CSN6595 | CAN → DLU | May 29, 00:55 UTC | May 29, 01:35 UTC | 40m |
| 2026-05-26 | CSN3353 | - | May 26, 15:14 UTC | May 26, 15:29 UTC | 15m |
| 2026-05-23 | - | - | May 23, 02:35 UTC | May 23, 02:45 UTC | 10m |
| 2026-05-21 | CSN3449 | CAN → KMG | May 21, 08:35 UTC | May 21, 08:45 UTC | 10m |
| 2026-05-21 | CSN3331 | CAN → NNG | May 21, 03:20 UTC | May 21, 03:30 UTC | 10m |
| 2026-05-15 | CSN3868 | JUH → CAN | May 15, 16:50 UTC | May 15, 17:00 UTC | 10m |
| 2026-05-09 | CSN6744 | CAN → SYX | May 9, 10:50 UTC | May 9, 11:05 UTC | 15m |
| 2026-05-07 | CSN8257 | HAK → PVG | May 7, 12:30 UTC | May 8, 01:49 UTC | 13h 19m |
| 2026-05-07 | CSN8257 | HAK → PVG | May 7, 01:15 UTC | May 7, 13:35 UTC | 12h 20m |
| 2026-05-06 | CSN8258 | PVG → HAK | May 6, 12:40 UTC | May 7, 01:35 UTC | 12h 54m |
| 2026-05-06 | CSN8258 | PVG → HAK | May 6, 01:30 UTC | May 7, 01:15 UTC | 23h 44m |
| 2026-05-06 | CSN8258 | PVG → HAK | May 6, 00:25 UTC | May 6, 12:50 UTC | 12h 24m |
| 2026-05-05 | CSN8258 | PVG → HAK | May 5, 12:30 UTC | May 6, 01:45 UTC | 13h 15m |
| 2026-05-05 | CSN8258 | PVG → HAK | May 5, 01:20 UTC | May 6, 01:05 UTC | 23h 45m |
| 2026-05-05 | CSN8258 | PVG → HAK | May 5, 01:00 UTC | May 5, 12:40 UTC | 11h 40m |
| 2026-05-04 | CSN8258 | PVG → HAK | May 4, 13:55 UTC | May 5, 12:40 UTC | 22h 46m |
| 2026-04-30 | CSN8258 | PVG → HAK | Apr 30, 12:45 UTC | May 1, 02:05 UTC | 13h 20m |
| 2026-04-30 | CSN8258 | PVG → HAK | Apr 30, 02:25 UTC | May 1, 01:15 UTC | 22h 50m |
| 2026-04-29 | CSN8258 | PVG → HAK | Apr 29, 13:40 UTC | Apr 30, 12:45 UTC | 23h 4m |
| 2026-04-25 | CSN371 | PEK → CAN | Apr 25, 14:25 UTC | Apr 25, 14:35 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-2408 page for operator, model, and routing details .