sensors Mode-S transponder
781623
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-306M · AIRBUS A-320neo
- Hex
- 781623
- Octal
- 36013043
- Decimal
- 7,869,987
- Country
- CN
- Tail
- B-306M
- Type
- A20N
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 781623 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 |
|---|---|---|---|
| CSN3605 | China Southern Airlines | 10 | 2026-07-04 |
| CSN6074 | - | 8 | 2026-07-14 |
| CSN6073 | China Southern Airlines | 8 | 2026-07-19 |
| CSN688 | - | 7 | 2026-07-20 |
| CSN637 | - | 7 | 2026-07-16 |
| CSN687 | China Southern Airlines | 6 | 2026-07-19 |
| CSN6851 | China Southern Airlines | 5 | 2026-06-06 |
| CSN638 | - | 5 | 2026-07-16 |
| CSN3606 | China Southern Airlines | 5 | 2026-07-03 |
| CSN6358 | - | 4 | 2026-07-09 |
| CSN6357 | - | 4 | 2026-07-09 |
| CSN6341 | China Southern Airlines | 4 | 2026-06-04 |
| CSN6545 | China Southern Airlines | 3 | 2026-04-23 |
| CSN6168 | - | 3 | 2026-06-29 |
| CSN6852 | China Southern Airlines | 2 | 2026-05-06 |
| CSN6442 | China Southern Airlines | 2 | 2026-04-24 |
| CSN6377 | China Southern Airlines | 2 | 2026-06-05 |
| CSN6194 | China Southern Airlines | 2 | 2026-06-24 |
| CSN6146 | China Southern Airlines | 2 | 2026-04-27 |
| CSN8460 | China Southern Airlines | 1 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | CSN688 | - | Jul 20, 06:00 UTC | Jul 20, 11:05 UTC | 5h 5m |
| 2026-07-19 | CSN6073 | YNJ → ICN | Jul 19, 12:25 UTC | Jul 20, 04:30 UTC | 16h 5m |
| 2026-07-19 | CSN8141 | YNJ → ICN | Jul 19, 04:30 UTC | Jul 19, 10:45 UTC | 6h 15m |
| 2026-07-19 | CSN687 | CGQ → ICN | Jul 19, 01:40 UTC | Jul 19, 02:40 UTC | 1h 0m |
| 2026-07-18 | CSN687 | CGQ → ICN | Jul 18, 06:40 UTC | Jul 19, 02:40 UTC | 20h 0m |
| 2026-07-16 | CSN638 | - | Jul 16, 10:40 UTC | Jul 16, 11:05 UTC | 25m |
| 2026-07-16 | CSN637 | - | Jul 16, 05:05 UTC | Jul 16, 08:55 UTC | 3h 50m |
| 2026-07-15 | CSN8459 | - | Jul 15, 09:55 UTC | Jul 16, 05:25 UTC | 19h 30m |
| 2026-07-15 | CSN688 | - | Jul 15, 05:50 UTC | Jul 15, 06:05 UTC | 15m |
| 2026-07-14 | CSN6073 | - | Jul 14, 15:20 UTC | Jul 15, 04:05 UTC | 12h 44m |
| 2026-07-14 | CSN6073 | - | Jul 14, 04:50 UTC | Jul 15, 04:05 UTC | 23h 14m |
| 2026-07-14 | CSN6074 | - | Jul 14, 04:30 UTC | Jul 14, 15:20 UTC | 10h 50m |
| 2026-07-14 | CSN687 | - | Jul 14, 02:20 UTC | Jul 14, 02:40 UTC | 20m |
| 2026-07-09 | CSN6179 | - | Jul 9, 12:50 UTC | Jul 9, 13:00 UTC | 10m |
| 2026-07-09 | CSN6358 | - | Jul 9, 09:05 UTC | Jul 9, 09:25 UTC | 20m |
| 2026-07-09 | CSN6358 | - | Jul 9, 06:30 UTC | Jul 9, 06:45 UTC | 15m |
| 2026-07-09 | CSN6357 | - | Jul 9, 03:55 UTC | Jul 9, 04:20 UTC | 25m |
| 2026-07-09 | CSN6357 | - | Jul 9, 01:35 UTC | Jul 9, 01:50 UTC | 15m |
| 2026-07-04 | CSN3605 | CGQ → CAN | Jul 4, 02:55 UTC | Jul 4, 12:00 UTC | 9h 5m |
| 2026-07-03 | CSN3606 | CAN → CGQ | Jul 3, 11:30 UTC | Jul 4, 03:10 UTC | 15h 40m |
| 2026-07-03 | CSN3606 | CAN → CGQ | Jul 3, 03:20 UTC | Jul 3, 11:50 UTC | 8h 30m |
| 2026-07-02 | CSN3606 | CAN → CGQ | Jul 2, 12:50 UTC | Jul 3, 11:50 UTC | 23h 0m |
| 2026-07-02 | CSN3606 | CAN → CGQ | Jul 2, 12:30 UTC | Jul 3, 03:35 UTC | 15h 5m |
| 2026-07-01 | CSN3606 | CAN → CGQ | Jul 1, 10:55 UTC | Jul 1, 11:10 UTC | 15m |
| 2026-07-01 | CSN3605 | CGQ → CAN | Jul 1, 05:30 UTC | Jul 1, 05:50 UTC | 20m |
| 2026-07-01 | CSN3605 | CGQ → CAN | Jul 1, 02:55 UTC | Jul 1, 03:15 UTC | 20m |
| 2026-06-30 | CSN6074 | - | Jun 30, 10:30 UTC | Jun 30, 10:45 UTC | 15m |
| 2026-06-30 | CSN637 | - | Jun 30, 08:40 UTC | Jun 30, 09:00 UTC | 20m |
| 2026-06-30 | CSN688 | - | Jun 30, 04:45 UTC | Jun 30, 08:05 UTC | 3h 20m |
| 2026-06-30 | CSN687 | - | Jun 30, 02:25 UTC | Jun 30, 02:45 UTC | 20m |
| 2026-06-29 | CSN6168 | - | Jun 29, 12:39 UTC | Jun 29, 12:49 UTC | 10m |
| 2026-06-29 | CSN638 | - | Jun 29, 05:45 UTC | Jun 29, 06:05 UTC | 20m |
| 2026-06-28 | CSN6073 | - | Jun 28, 11:35 UTC | Jun 29, 03:54 UTC | 16h 20m |
| 2026-06-26 | CSN6074 | - | Jun 26, 10:35 UTC | Jun 27, 04:19 UTC | 17h 45m |
| 2026-06-26 | CSN637 | - | Jun 26, 08:34 UTC | Jun 26, 09:00 UTC | 25m |
| 2026-06-26 | CSN688 | - | Jun 26, 04:55 UTC | Jun 26, 05:10 UTC | 15m |
| 2026-06-26 | CSN687 | - | Jun 26, 02:09 UTC | Jun 26, 02:30 UTC | 20m |
| 2026-06-24 | CSN6194 | PKX → CGQ | Jun 24, 09:15 UTC | Jun 24, 09:24 UTC | 10m |
| 2026-06-13 | CSN3605 | CGQ → CAN | Jun 13, 06:00 UTC | Jun 13, 06:10 UTC | 10m |
| 2026-06-12 | CSN6074 | ICN → YNJ | Jun 12, 10:30 UTC | Jun 13, 03:10 UTC | 16h 40m |
| 2026-06-12 | CSN637 | CGQ → ICN | Jun 12, 03:45 UTC | Jun 12, 08:55 UTC | 5h 10m |
| 2026-06-12 | CSN6145 | CGQ → PKX | Jun 12, 01:25 UTC | Jun 12, 01:35 UTC | 10m |
| 2026-06-10 | CSN8256 | CKG → CGQ | Jun 10, 12:35 UTC | Jun 11, 00:10 UTC | 11h 35m |
| 2026-06-09 | CSN6364 | CKG → CGQ | Jun 9, 07:25 UTC | Jun 9, 07:50 UTC | 25m |
| 2026-06-06 | CSN6851 | CGQ → CAN | Jun 6, 03:30 UTC | Jun 6, 14:45 UTC | 11h 15m |
| 2026-06-05 | CSN6851 | CGQ → CAN | Jun 5, 12:50 UTC | Jun 6, 07:45 UTC | 18h 55m |
| 2026-06-05 | CSN6377 | CGQ → CAN | Jun 5, 12:25 UTC | Jun 6, 07:45 UTC | 19h 20m |
| 2026-06-05 | CSN6377 | CGQ → CAN | Jun 5, 08:25 UTC | Jun 6, 03:45 UTC | 19h 20m |
| 2026-06-04 | CSN6341 | CGQ → CAN | Jun 4, 07:20 UTC | Jun 5, 01:30 UTC | 18h 10m |
| 2026-06-02 | CSN6168 | PKX → CGQ | Jun 2, 12:40 UTC | Jun 2, 13:00 UTC | 20m |
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-306M page for operator, model, and routing details .