sensors Mode-S transponder
782207
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32L2 · AIRBUS A-320neo
- Hex
- 782207
- Octal
- 36021007
- Decimal
- 7,873,031
- Country
- CN
- Tail
- B-32L2
- Type
- A20N
- Flights observed
- 73
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 782207 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 |
|---|---|---|---|
| CSN8023 | - | 13 | 2026-07-13 |
| CSN8024 | - | 12 | 2026-07-13 |
| CSN8313 | - | 5 | 2026-07-12 |
| CSN323 | - | 5 | 2026-07-06 |
| CSN8315 | - | 4 | 2026-07-05 |
| CSN8316 | - | 2 | 2026-07-05 |
| CSN8314 | China Southern Airlines | 2 | 2026-06-22 |
| CSN8178 | - | 2 | 2026-07-12 |
| CSN8177 | - | 2 | 2026-07-12 |
| CSN6307 | China Southern Airlines | 2 | 2026-06-10 |
| CSN6064 | China Southern Airlines | 2 | 2026-05-29 |
| CSN6063 | China Southern Airlines | 2 | 2026-04-19 |
| CSN3497 | China Southern Airlines | 2 | 2026-06-15 |
| CSN3049 | - | 2 | 2026-06-20 |
| CSN8293 | China Southern Airlines | 1 | 2026-05-17 |
| CSN6499 | - | 1 | 2026-06-21 |
| CSN6331 | China Southern Airlines | 1 | 2026-06-02 |
| CSN6058 | China Southern Airlines | 1 | 2026-05-02 |
| CSN6057 | China Southern Airlines | 1 | 2026-05-02 |
| CSN3880 | - | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CSN8024 | - | Jul 13, 11:05 UTC | Jul 13, 11:25 UTC | 20m |
| 2026-07-13 | CSN8023 | - | Jul 13, 09:05 UTC | Jul 13, 09:30 UTC | 25m |
| 2026-07-12 | CSN8178 | - | Jul 12, 13:15 UTC | Jul 13, 07:50 UTC | 18h 35m |
| 2026-07-12 | CSN8177 | - | Jul 12, 10:55 UTC | Jul 12, 11:25 UTC | 30m |
| 2026-07-12 | CSN8313 | - | Jul 12, 01:20 UTC | Jul 12, 01:30 UTC | 10m |
| 2026-07-11 | CSN8024 | - | Jul 11, 11:10 UTC | Jul 11, 11:20 UTC | 10m |
| 2026-07-11 | CSN8023 | - | Jul 11, 09:10 UTC | Jul 11, 09:30 UTC | 20m |
| 2026-07-11 | CSN8023 | - | Jul 11, 07:20 UTC | Jul 11, 07:30 UTC | 10m |
| 2026-07-08 | CSN8024 | - | Jul 8, 14:35 UTC | Jul 9, 03:30 UTC | 12h 55m |
| 2026-07-08 | CSN8023 | - | Jul 8, 10:30 UTC | Jul 8, 12:55 UTC | 2h 25m |
| 2026-07-07 | CSN8024 | - | Jul 7, 11:15 UTC | Jul 7, 12:50 UTC | 1h 35m |
| 2026-07-07 | CSN8023 | - | Jul 7, 07:15 UTC | Jul 7, 09:50 UTC | 2h 35m |
| 2026-07-06 | CSN323 | - | Jul 6, 14:15 UTC | Jul 7, 02:35 UTC | 12h 20m |
| 2026-07-06 | CSN3082 | - | Jul 6, 08:55 UTC | Jul 6, 09:50 UTC | 55m |
| 2026-07-06 | CSN3081 | - | Jul 6, 06:35 UTC | Jul 6, 07:35 UTC | 1h 0m |
| 2026-07-05 | CSN8316 | - | Jul 5, 10:15 UTC | Jul 5, 10:45 UTC | 30m |
| 2026-07-05 | CSN8315 | - | Jul 5, 06:55 UTC | Jul 5, 08:05 UTC | 1h 10m |
| 2026-07-03 | CSN8313 | - | Jul 3, 01:10 UTC | Jul 3, 06:20 UTC | 5h 10m |
| 2026-07-02 | CSN3068 | - | Jul 2, 18:00 UTC | Jul 2, 20:55 UTC | 2h 55m |
| 2026-07-02 | CSN3067 | ZGN → KTM | Jul 2, 12:30 UTC | Jul 2, 16:35 UTC | 4h 5m |
| 2026-07-01 | CSN3409 | - | Jul 1, 00:40 UTC | Jul 1, 04:40 UTC | 4h 0m |
| 2026-06-24 | CSN3489 | - | Jun 24, 12:14 UTC | Jun 24, 15:59 UTC | 3h 45m |
| 2026-06-22 | CSN8314 | PNH → CAN | Jun 22, 06:05 UTC | Jun 22, 06:25 UTC | 20m |
| 2026-06-22 | CSN8313 | - | Jun 22, 01:19 UTC | Jun 22, 01:29 UTC | 10m |
| 2026-06-21 | CSN6499 | - | Jun 21, 02:20 UTC | Jun 21, 11:44 UTC | 9h 25m |
| 2026-06-20 | CSN3050 | HAN → CAN | Jun 20, 04:29 UTC | Jun 20, 04:54 UTC | 25m |
| 2026-06-20 | CSN3049 | - | Jun 20, 01:34 UTC | Jun 20, 02:49 UTC | 1h 15m |
| 2026-06-19 | - | - | Jun 19, 12:09 UTC | Jun 19, 12:19 UTC | 10m |
| 2026-06-17 | CSN8314 | PNH → CAN | Jun 17, 06:10 UTC | Jun 17, 06:30 UTC | 20m |
| 2026-06-17 | CSN8313 | - | Jun 17, 01:40 UTC | Jun 17, 01:50 UTC | 10m |
| 2026-06-15 | CSN3497 | CAN → KMG | Jun 15, 23:35 UTC | Jun 16, 00:29 UTC | 55m |
| 2026-06-11 | CSN8024 | BKK → CAN | Jun 11, 11:50 UTC | Jun 12, 07:35 UTC | 19h 46m |
| 2026-06-11 | CSN8024 | BKK → CAN | Jun 11, 11:25 UTC | Jun 12, 07:35 UTC | 20h 11m |
| 2026-06-11 | CSN8023 | CAN → BKK | Jun 11, 07:30 UTC | Jun 11, 09:10 UTC | 1h 40m |
| 2026-06-10 | CSN8023 | CAN → BKK | Jun 10, 07:50 UTC | Jun 11, 07:40 UTC | 23h 50m |
| 2026-06-10 | CSN6307 | SHE → CAN | Jun 10, 03:55 UTC | Jun 10, 07:55 UTC | 4h 0m |
| 2026-06-09 | CSN6307 | SHE → CAN | Jun 9, 11:50 UTC | Jun 10, 07:55 UTC | 20h 5m |
| 2026-06-09 | CSN8024 | BKK → CAN | Jun 9, 11:20 UTC | Jun 10, 07:55 UTC | 20h 35m |
| 2026-06-09 | CSN8023 | CAN → BKK | Jun 9, 07:30 UTC | Jun 9, 09:45 UTC | 2h 15m |
| 2026-06-06 | CSN8024 | BKK → CAN | Jun 6, 11:39 UTC | Jun 7, 01:30 UTC | 13h 50m |
| 2026-06-06 | CSN8023 | CAN → BKK | Jun 6, 08:45 UTC | Jun 6, 10:25 UTC | 1h 40m |
| 2026-06-05 | CSN8316 | HAN → CAN | Jun 5, 09:15 UTC | Jun 5, 09:40 UTC | 25m |
| 2026-06-05 | CSN8315 | CAN → HAN | Jun 5, 06:50 UTC | Jun 5, 07:15 UTC | 25m |
| 2026-06-02 | CSN6331 | SHE → CAN | Jun 2, 13:00 UTC | Jun 2, 13:30 UTC | 30m |
| 2026-05-31 | CSN8178 | HAN → CAN | May 31, 13:10 UTC | May 31, 13:35 UTC | 25m |
| 2026-05-31 | CSN8177 | CAN → HAN | May 31, 10:00 UTC | May 31, 11:05 UTC | 1h 5m |
| 2026-05-30 | CSN3880 | - | May 30, 09:40 UTC | May 30, 10:05 UTC | 25m |
| 2026-05-30 | CSN3879 | - | May 30, 06:40 UTC | May 30, 06:50 UTC | 10m |
| 2026-05-29 | CSN6064 | HKT → CAN | May 29, 05:25 UTC | May 29, 12:00 UTC | 6h 35m |
| 2026-05-28 | CSN8024 | BKK → CAN | May 28, 11:05 UTC | May 28, 12:45 UTC | 1h 40m |
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-32L2 page for operator, model, and routing details .