sensors Mode-S transponder
781916
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-30EA · AIRBUS A-350-900
- Hex
- 781916
- Octal
- 36014426
- Decimal
- 7,870,742
- Country
- CN
- Tail
- B-30EA
- Type
- A359
- Flights observed
- 87
- Distinct callsigns
- 12
- Country
- CN
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 781916 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 12 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSN655 | China Southern Airlines | 38 | 2026-05-18 |
| CSN656 | China Southern Airlines | 19 | 2026-05-16 |
| CSN8027 | China Southern Airlines | 15 | 2026-05-25 |
| CSN8028 | China Southern Airlines | 7 | 2026-05-26 |
| CSN8004 | China Southern Airlines | 1 | 2026-04-12 |
| CSN656A | - | 1 | 2026-05-20 |
| CSN347 | China Southern Airlines | 1 | 2026-05-29 |
| CSN3415 | China Southern Airlines | 1 | 2026-04-25 |
| CSN308 | China Southern Airlines | 1 | 2026-04-20 |
| CSN307 | China Southern Airlines | 1 | 2026-04-19 |
| CSN302 | China Southern Airlines | 1 | 2026-05-21 |
| CSN301 | China Southern Airlines | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | CSN347 | CAN → CDG | May 29, 22:15 UTC | May 30, 05:00 UTC | 6h 45m |
| 2026-05-26 | CSN8028 | SVO → CAN | May 26, 13:40 UTC | May 26, 17:30 UTC | 3h 50m |
| 2026-05-25 | CSN8027 | CAN → SVO | May 25, 16:30 UTC | May 26, 10:14 UTC | 17h 44m |
| 2026-05-25 | CSN8027 | CAN → SVO | May 25, 13:35 UTC | May 26, 10:14 UTC | 20h 40m |
| 2026-05-25 | CSN8027 | CAN → SVO | May 25, 13:15 UTC | May 26, 10:14 UTC | 21h 0m |
| 2026-05-24 | CSN8027 | CAN → SVO | May 24, 15:35 UTC | May 25, 10:15 UTC | 18h 40m |
| 2026-05-24 | CSN8027 | CAN → SVO | May 24, 13:35 UTC | May 25, 10:15 UTC | 20h 40m |
| 2026-05-24 | CSN8027 | CAN → SVO | May 24, 13:25 UTC | May 25, 10:15 UTC | 20h 50m |
| 2026-05-23 | CSN8027 | CAN → SVO | May 23, 15:40 UTC | May 24, 10:00 UTC | 18h 20m |
| 2026-05-23 | CSN8027 | CAN → SVO | May 23, 13:35 UTC | May 24, 10:00 UTC | 20h 25m |
| 2026-05-22 | CSN8027 | CAN → SVO | May 22, 15:50 UTC | May 23, 09:40 UTC | 17h 50m |
| 2026-05-22 | CSN8027 | CAN → SVO | May 22, 09:15 UTC | May 22, 09:45 UTC | 30m |
| 2026-05-22 | CSN8027 | CAN → SVO | May 22, 05:25 UTC | May 22, 08:40 UTC | 3h 15m |
| 2026-05-21 | CSN302 | SYD → CAN | May 21, 11:50 UTC | May 21, 20:25 UTC | 8h 35m |
| 2026-05-21 | CSN301 | CAN → SYD | May 21, 00:40 UTC | May 21, 09:00 UTC | 8h 20m |
| 2026-05-20 | CSN656A | - | May 20, 02:00 UTC | May 20, 05:50 UTC | 3h 51m |
| 2026-05-18 | CSN655 | CAN → SVO | May 18, 14:50 UTC | May 18, 15:20 UTC | 30m |
| 2026-05-18 | CSN655 | CAN → SVO | May 18, 11:00 UTC | May 18, 14:15 UTC | 3h 15m |
| 2026-05-16 | CSN656 | SVO → CAN | May 16, 18:35 UTC | May 16, 20:05 UTC | 1h 30m |
| 2026-05-15 | CSN655 | CAN → SVO | May 15, 19:35 UTC | May 16, 15:45 UTC | 20h 11m |
| 2026-05-15 | CSN655 | CAN → SVO | May 15, 18:35 UTC | May 16, 15:45 UTC | 21h 11m |
| 2026-05-14 | CSN655 | CAN → SVO | May 14, 19:35 UTC | May 15, 15:30 UTC | 19h 54m |
| 2026-05-14 | CSN655 | CAN → SVO | May 14, 18:45 UTC | May 15, 15:30 UTC | 20h 44m |
| 2026-05-13 | CSN655 | CAN → SVO | May 13, 21:40 UTC | May 14, 16:25 UTC | 18h 45m |
| 2026-05-13 | CSN655 | CAN → SVO | May 13, 19:35 UTC | May 14, 16:25 UTC | 20h 50m |
| 2026-05-13 | CSN655 | CAN → SVO | May 13, 18:35 UTC | May 14, 16:25 UTC | 21h 50m |
| 2026-05-13 | CSN655 | CAN → SVO | May 13, 11:00 UTC | May 13, 15:30 UTC | 4h 30m |
| 2026-05-09 | CSN656 | SVO → CAN | May 9, 18:40 UTC | May 9, 22:10 UTC | 3h 30m |
| 2026-05-09 | CSN655 | CAN → SVO | May 9, 15:20 UTC | May 9, 15:55 UTC | 35m |
| 2026-05-08 | CSN655 | CAN → SVO | May 8, 19:35 UTC | May 9, 14:50 UTC | 19h 15m |
| 2026-05-08 | CSN656 | SVO → CAN | May 8, 18:45 UTC | May 9, 14:50 UTC | 20h 5m |
| 2026-05-07 | CSN656 | SVO → CAN | May 7, 19:45 UTC | May 8, 13:45 UTC | 18h 0m |
| 2026-05-07 | CSN656 | SVO → CAN | May 7, 18:55 UTC | May 8, 13:45 UTC | 18h 50m |
| 2026-05-07 | CSN655 | CAN → SVO | May 7, 16:00 UTC | May 7, 16:40 UTC | 40m |
| 2026-05-06 | CSN655 | CAN → SVO | May 6, 19:35 UTC | May 7, 14:40 UTC | 19h 6m |
| 2026-05-06 | CSN655 | CAN → SVO | May 6, 18:40 UTC | May 7, 14:40 UTC | 20h 1m |
| 2026-05-06 | CSN655 | CAN → SVO | May 6, 11:05 UTC | May 6, 15:30 UTC | 4h 25m |
| 2026-05-04 | CSN656 | SVO → CAN | May 4, 18:40 UTC | May 4, 20:50 UTC | 2h 10m |
| 2026-05-04 | CSN655 | CAN → SVO | May 4, 15:25 UTC | May 4, 15:45 UTC | 20m |
| 2026-05-04 | CSN655 | CAN → SVO | May 4, 11:20 UTC | May 4, 14:40 UTC | 3h 20m |
| 2026-05-02 | CSN656 | SVO → CAN | May 2, 18:40 UTC | May 2, 22:15 UTC | 3h 35m |
| 2026-05-01 | CSN655 | CAN → SVO | May 1, 19:35 UTC | May 2, 15:25 UTC | 19h 51m |
| 2026-05-01 | CSN655 | CAN → SVO | May 1, 18:30 UTC | May 2, 15:25 UTC | 20h 55m |
| 2026-05-01 | CSN655 | CAN → SVO | May 1, 10:55 UTC | May 1, 15:05 UTC | 4h 10m |
| 2026-04-29 | CSN656 | SVO → CAN | Apr 29, 18:25 UTC | Apr 29, 22:10 UTC | 3h 45m |
| 2026-04-29 | CSN655 | CAN → SVO | Apr 29, 11:05 UTC | Apr 29, 15:25 UTC | 4h 20m |
| 2026-04-27 | CSN656 | SVO → CAN | Apr 27, 19:15 UTC | Apr 27, 22:55 UTC | 3h 40m |
| 2026-04-27 | CSN655 | CAN → SVO | Apr 27, 11:10 UTC | Apr 27, 15:45 UTC | 4h 35m |
| 2026-04-26 | CSN655 | CAN → SVO | Apr 26, 16:20 UTC | Apr 27, 15:30 UTC | 23h 10m |
| 2026-04-26 | CSN8028 | SVO → CAN | Apr 26, 13:35 UTC | Apr 27, 13:30 UTC | 23h 55m |
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-30EA page for operator, model, and routing details .