sensors Mode-S transponder
782188
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32JL · AIRBUS A-320neo
- Hex
- 782188
- Octal
- 36020610
- Decimal
- 7,872,904
- Country
- CN
- Tail
- B-32JL
- Type
- A20N
- Flights observed
- 37
- Distinct callsigns
- 17
- Country
- CN
- Last broadcast
- 36m ago
Last known position
Country allocation
The ICAO 24-bit address 782188 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 |
|---|---|---|---|
| CSN8258 | China Southern Airlines | 5 | 2026-04-21 |
| CSN6774 | China Southern Airlines | 4 | 2026-04-21 |
| CSN6331 | China Southern Airlines | 4 | 2026-05-05 |
| CSN8024 | China Southern Airlines | 3 | 2026-05-14 |
| CSN8023 | China Southern Airlines | 3 | 2026-05-14 |
| CSN6058 | China Southern Airlines | 3 | 2026-05-01 |
| CSN8313 | China Southern Airlines | 2 | 2026-05-22 |
| CSN8257 | - | 2 | 2026-04-17 |
| CSN3536 | China Southern Airlines | 2 | 2026-05-29 |
| CSN3081 | China Southern Airlines | 2 | 2026-05-30 |
| CSN8100 | China Southern Airlines | 1 | 2026-05-20 |
| CSN8099 | China Southern Airlines | 1 | 2026-05-20 |
| CSN6793 | China Southern Airlines | 1 | 2026-04-16 |
| CSN6063 | China Southern Airlines | 1 | 2026-05-18 |
| CSN5588 | China Southern Airlines | 1 | 2026-04-25 |
| CSN5470 | China Southern Airlines | 1 | 2026-04-26 |
| CSN3082 | China Southern Airlines | 1 | 2026-05-27 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | CSN3081 | CAN → BKK | May 30, 05:20 UTC | May 30, 05:35 UTC | 15m |
| 2026-05-29 | CSN3536 | TAO → CAN | May 29, 15:50 UTC | May 29, 16:10 UTC | 20m |
| 2026-05-29 | CSN3536 | TAO → CAN | May 29, 11:25 UTC | May 29, 12:00 UTC | 35m |
| 2026-05-27 | CSN3082 | BKK → CAN | May 27, 09:00 UTC | May 27, 10:40 UTC | 1h 40m |
| 2026-05-27 | CSN3081 | CAN → BKK | May 27, 06:15 UTC | May 27, 06:49 UTC | 35m |
| 2026-05-22 | CSN8313 | CAN → PNH | May 22, 01:30 UTC | May 22, 01:40 UTC | 10m |
| 2026-05-20 | CSN8100 | BKK → CAN | May 20, 07:05 UTC | May 20, 07:30 UTC | 25m |
| 2026-05-20 | CSN8099 | CAN → BKK | May 20, 03:10 UTC | May 20, 05:15 UTC | 2h 6m |
| 2026-05-18 | CSN6063 | CAN → HKT | May 18, 07:00 UTC | May 18, 11:00 UTC | 4h 0m |
| 2026-05-14 | CSN8024 | BKK → CAN | May 14, 11:55 UTC | May 14, 12:35 UTC | 40m |
| 2026-05-14 | CSN8023 | CAN → BKK | May 14, 10:00 UTC | May 14, 10:35 UTC | 35m |
| 2026-05-13 | CSN8024 | BKK → CAN | May 13, 11:15 UTC | May 14, 10:00 UTC | 22h 45m |
| 2026-05-13 | CSN8023 | CAN → BKK | May 13, 07:30 UTC | May 13, 09:45 UTC | 2h 15m |
| 2026-05-05 | CSN6331 | SHE → CAN | May 5, 03:55 UTC | May 5, 12:45 UTC | 8h 50m |
| 2026-05-04 | CSN8024 | BKK → CAN | May 4, 11:55 UTC | May 5, 04:00 UTC | 16h 6m |
| 2026-05-04 | CSN8023 | CAN → BKK | May 4, 07:20 UTC | May 4, 10:05 UTC | 2h 45m |
| 2026-05-02 | CSN6331 | SHE → CAN | May 2, 12:40 UTC | May 3, 03:40 UTC | 14h 59m |
| 2026-05-02 | CSN6331 | SHE → CAN | May 2, 03:40 UTC | May 2, 13:10 UTC | 9h 30m |
| 2026-05-01 | CSN6058 | HKT → CAN | May 1, 17:05 UTC | May 2, 13:10 UTC | 20h 5m |
| 2026-05-01 | CSN6058 | HKT → CAN | May 1, 14:05 UTC | May 2, 13:10 UTC | 23h 6m |
| 2026-05-01 | CSN6058 | HKT → CAN | May 1, 13:55 UTC | May 2, 03:40 UTC | 13h 46m |
| 2026-05-01 | CSN8313 | CAN → PNH | May 1, 01:20 UTC | May 1, 01:30 UTC | 10m |
| 2026-04-26 | CSN5470 | CGQ → HGH | Apr 26, 05:55 UTC | Apr 26, 06:25 UTC | 30m |
| 2026-04-25 | CSN5588 | ZUH → HGH | Apr 25, 12:15 UTC | Apr 25, 12:25 UTC | 10m |
| 2026-04-23 | CSN6331 | SHE → CAN | Apr 23, 15:10 UTC | Apr 23, 15:25 UTC | 15m |
| 2026-04-21 | CSN8258 | PVG → HAK | Apr 21, 12:55 UTC | Apr 22, 02:00 UTC | 13h 5m |
| 2026-04-21 | CSN6774 | CAN → HAK | Apr 21, 01:50 UTC | Apr 21, 02:05 UTC | 15m |
| 2026-04-19 | CSN8258 | PVG → HAK | Apr 19, 14:45 UTC | Apr 20, 02:05 UTC | 11h 20m |
| 2026-04-18 | CSN8258 | PVG → HAK | Apr 18, 01:45 UTC | Apr 18, 02:00 UTC | 15m |
| 2026-04-17 | CSN8257 | - | Apr 17, 14:25 UTC | Apr 17, 14:35 UTC | 10m |
| 2026-04-17 | CSN6774 | CAN → HAK | Apr 17, 02:15 UTC | Apr 17, 02:25 UTC | 10m |
| 2026-04-16 | CSN6793 | HAK → CAN | Apr 16, 13:54 UTC | Apr 16, 14:05 UTC | 10m |
| 2026-04-16 | CSN8258 | PVG → HAK | Apr 16, 01:10 UTC | Apr 16, 02:09 UTC | 1h 0m |
| 2026-04-16 | CSN8258 | PVG → HAK | Apr 16, 00:45 UTC | Apr 16, 01:05 UTC | 20m |
| 2026-04-15 | CSN6774 | CAN → HAK | Apr 15, 02:00 UTC | Apr 15, 02:15 UTC | 14m |
| 2026-04-13 | CSN8257 | - | Apr 13, 13:00 UTC | Apr 13, 13:10 UTC | 10m |
| 2026-04-13 | CSN6774 | CAN → HAK | Apr 13, 02:10 UTC | Apr 13, 02:20 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-32JL page for operator, model, and routing details .