sensors Mode-S transponder
780F13
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8341 · AIRBUS A-320
- Hex
- 780F13
- Octal
- 36007423
- Decimal
- 7,868,179
- Country
- CN
- Tail
- B-8341
- Type
- A320
- Flights observed
- 107
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 780F13 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 |
|---|---|---|---|
| CSN3978 | - | 13 | 2026-07-10 |
| CSN6584 | - | 11 | 2026-07-13 |
| CSN3977 | China Southern Airlines | 11 | 2026-07-10 |
| CSN6360 | - | 6 | 2026-06-22 |
| CSN6732 | - | 5 | 2026-07-01 |
| CSN6668 | - | 5 | 2026-07-10 |
| CSN6667 | - | 5 | 2026-07-05 |
| CSN6758 | - | 4 | 2026-07-02 |
| CSN6699 | China Southern Airlines | 4 | 2026-06-25 |
| CSN6757 | - | 3 | 2026-07-02 |
| CSN6190 | China Southern Airlines | 3 | 2026-06-25 |
| CSN6700 | China Southern Airlines | 2 | 2026-06-01 |
| CSN6669 | China Southern Airlines | 2 | 2026-04-22 |
| CSN6583 | - | 2 | 2026-07-03 |
| CSN6514 | - | 2 | 2026-06-23 |
| CSN6293 | China Southern Airlines | 2 | 2026-07-06 |
| CSN5685 | - | 2 | 2026-07-03 |
| CSN3836 | - | 2 | 2026-07-12 |
| CSN8857 | - | 1 | 2026-07-14 |
| CSN8751 | - | 1 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | CSN6736 | - | Jul 15, 16:25 UTC | Jul 15, 16:35 UTC | 10m |
| 2026-07-14 | CSN8857 | - | Jul 14, 05:35 UTC | Jul 14, 09:00 UTC | 3h 25m |
| 2026-07-13 | CSN6584 | - | Jul 13, 08:55 UTC | Jul 13, 15:10 UTC | 6h 15m |
| 2026-07-12 | CSN3836 | - | Jul 12, 05:05 UTC | Jul 12, 10:45 UTC | 5h 40m |
| 2026-07-11 | CSN3836 | - | Jul 11, 10:55 UTC | Jul 12, 10:45 UTC | 23h 50m |
| 2026-07-10 | CSN6668 | - | Jul 10, 13:50 UTC | Jul 10, 14:10 UTC | 20m |
| 2026-07-10 | CSN3978 | - | Jul 10, 04:25 UTC | Jul 10, 04:35 UTC | 10m |
| 2026-07-10 | CSN3977 | SYX → SZX | Jul 10, 00:10 UTC | Jul 10, 00:25 UTC | 15m |
| 2026-07-09 | CSN6624 | - | Jul 9, 05:35 UTC | Jul 9, 05:55 UTC | 20m |
| 2026-07-08 | CSN6623 | - | Jul 8, 09:15 UTC | Jul 9, 05:55 UTC | 20h 40m |
| 2026-07-08 | CSN8751 | - | Jul 8, 01:20 UTC | Jul 8, 05:50 UTC | 4h 30m |
| 2026-07-06 | CSN6936 | - | Jul 6, 15:10 UTC | Jul 7, 10:45 UTC | 19h 35m |
| 2026-07-06 | CSN6293 | SYX → KMG | Jul 6, 11:05 UTC | Jul 7, 10:45 UTC | 23h 40m |
| 2026-07-06 | CSN6584 | - | Jul 6, 05:00 UTC | Jul 6, 08:50 UTC | 3h 50m |
| 2026-07-05 | CSN6584 | - | Jul 5, 12:20 UTC | Jul 6, 08:50 UTC | 20h 30m |
| 2026-07-05 | CSN6667 | - | Jul 5, 07:25 UTC | Jul 6, 05:20 UTC | 21h 55m |
| 2026-07-05 | CSN6667 | - | Jul 5, 04:40 UTC | Jul 5, 12:40 UTC | 8h 0m |
| 2026-07-04 | CSN6667 | - | Jul 4, 09:05 UTC | Jul 5, 07:40 UTC | 22h 35m |
| 2026-07-03 | CSN5685 | - | Jul 3, 21:55 UTC | Jul 4, 09:15 UTC | 11h 20m |
| 2026-07-03 | CSN5685 | - | Jul 3, 04:50 UTC | Jul 4, 02:50 UTC | 22h 0m |
| 2026-07-03 | CSN6583 | - | Jul 3, 04:35 UTC | Jul 4, 02:45 UTC | 22h 10m |
| 2026-07-03 | CSN3978 | - | Jul 3, 01:45 UTC | Jul 3, 01:55 UTC | 10m |
| 2026-07-02 | CSN6758 | - | Jul 2, 17:15 UTC | Jul 2, 17:30 UTC | 15m |
| 2026-07-02 | CSN6757 | - | Jul 2, 14:15 UTC | Jul 2, 14:30 UTC | 15m |
| 2026-07-01 | CSN6668 | - | Jul 1, 07:45 UTC | Jul 2, 01:55 UTC | 18h 10m |
| 2026-07-01 | CSN6732 | - | Jul 1, 02:20 UTC | Jul 1, 14:00 UTC | 11h 40m |
| 2026-06-30 | CSN6792 | - | Jun 30, 11:15 UTC | Jun 30, 11:25 UTC | 10m |
| 2026-06-30 | CSN3493 | - | Jun 30, 02:30 UTC | Jun 30, 03:25 UTC | 55m |
| 2026-06-26 | CSN3120 | PKX → HAK | Jun 26, 08:05 UTC | Jun 26, 08:20 UTC | 15m |
| 2026-06-25 | CSN6190 | TFU → SYX | Jun 25, 11:59 UTC | Jun 26, 08:20 UTC | 20h 20m |
| 2026-06-25 | CSN6699 | SYX → KMG | Jun 25, 00:14 UTC | Jun 25, 12:30 UTC | 12h 15m |
| 2026-06-24 | CSN6584 | KMG → SYX | Jun 24, 02:00 UTC | Jun 24, 08:49 UTC | 6h 50m |
| 2026-06-23 | CSN3977 | SYX → SZX | Jun 23, 23:59 UTC | Jun 24, 00:09 UTC | 10m |
| 2026-06-23 | CSN6514 | - | Jun 23, 12:45 UTC | Jun 23, 13:05 UTC | 20m |
| 2026-06-22 | CSN6360 | - | Jun 22, 06:05 UTC | Jun 22, 15:45 UTC | 9h 40m |
| 2026-06-21 | CSN6360 | - | Jun 21, 15:40 UTC | Jun 21, 15:59 UTC | 20m |
| 2026-06-21 | CSN6359 | - | Jun 21, 01:39 UTC | Jun 21, 06:10 UTC | 4h 30m |
| 2026-06-20 | CSN6360 | - | Jun 20, 15:19 UTC | Jun 20, 15:34 UTC | 15m |
| 2026-06-20 | CSN6360 | - | Jun 20, 10:39 UTC | Jun 20, 10:49 UTC | 10m |
| 2026-06-19 | CSN6360 | - | Jun 19, 15:14 UTC | Jun 20, 01:55 UTC | 10h 40m |
| 2026-06-18 | CSN6360 | HRB → WUH | Jun 18, 01:40 UTC | Jun 18, 15:45 UTC | 14h 5m |
| 2026-06-17 | CSN6758 | - | Jun 17, 17:25 UTC | Jun 18, 15:45 UTC | 22h 20m |
| 2026-06-17 | CSN3978 | - | Jun 17, 02:25 UTC | Jun 17, 10:05 UTC | 7h 40m |
| 2026-06-16 | CSN3977 | SYX → SZX | Jun 16, 23:50 UTC | Jun 17, 00:00 UTC | 10m |
| 2026-06-15 | CSN5174 | CGQ → CSX | Jun 15, 01:15 UTC | Jun 15, 14:10 UTC | 12h 55m |
| 2026-06-14 | CSN6699 | SYX → KMG | Jun 14, 00:00 UTC | Jun 14, 04:30 UTC | 4h 30m |
| 2026-06-13 | CSN6699 | SYX → KMG | Jun 13, 06:45 UTC | Jun 14, 04:30 UTC | 21h 45m |
| 2026-06-13 | CSN6699 | SYX → KMG | Jun 13, 02:25 UTC | Jun 14, 00:30 UTC | 22h 4m |
| 2026-06-12 | CSN6935 | - | Jun 12, 13:45 UTC | Jun 13, 06:45 UTC | 16h 59m |
| 2026-06-12 | CSN6584 | KMG → SYX | Jun 12, 08:20 UTC | Jun 13, 06:45 UTC | 22h 24m |
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-8341 page for operator, model, and routing details .