sensors Mode-S transponder
7803B1
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6909 · AIRBUS A-320
- Hex
- 7803B1
- Octal
- 36001661
- Decimal
- 7,865,265
- Country
- CN
- Tail
- B-6909
- Type
- A320
- Flights observed
- 81
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7803B1 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 |
|---|---|---|---|
| CSN6364 | - | 7 | 2026-07-03 |
| CSN6194 | - | 6 | 2026-07-04 |
| CSN6620 | - | 5 | 2026-07-10 |
| CSN6603 | - | 5 | 2026-04-27 |
| CSN6619 | - | 4 | 2026-07-09 |
| CSN6358 | - | 4 | 2026-07-11 |
| CSN6357 | - | 4 | 2026-07-11 |
| CSN6155 | - | 4 | 2026-07-13 |
| CSN6146 | - | 4 | 2026-07-13 |
| CSN6541 | - | 3 | 2026-06-25 |
| CSN5470 | - | 3 | 2026-06-18 |
| CSN8256 | China Southern Airlines | 2 | 2026-06-30 |
| CSN6610 | China Southern Airlines | 2 | 2026-05-31 |
| CSN6420 | - | 2 | 2026-07-07 |
| CSN6400 | China Southern Airlines | 2 | 2026-05-01 |
| CSN6341 | China Southern Airlines | 2 | 2026-06-08 |
| CSN6180 | - | 2 | 2026-06-24 |
| CSN6168 | - | 2 | 2026-07-12 |
| CSN8460 | China Southern Airlines | 1 | 2026-06-20 |
| CSN8459 | China Southern Airlines | 1 | 2026-06-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CSN6155 | - | Jul 13, 07:20 UTC | Jul 13, 08:05 UTC | 45m |
| 2026-07-13 | CSN6146 | - | Jul 13, 03:55 UTC | Jul 13, 04:05 UTC | 10m |
| 2026-07-12 | CSN6168 | - | Jul 12, 12:35 UTC | Jul 12, 12:45 UTC | 10m |
| 2026-07-11 | CSN6179 | - | Jul 11, 12:45 UTC | Jul 11, 13:00 UTC | 15m |
| 2026-07-11 | CSN6358 | - | Jul 11, 06:25 UTC | Jul 11, 06:40 UTC | 15m |
| 2026-07-11 | CSN6357 | - | Jul 11, 03:55 UTC | Jul 11, 04:15 UTC | 20m |
| 2026-07-10 | CSN6357 | - | Jul 10, 13:00 UTC | Jul 11, 01:55 UTC | 12h 55m |
| 2026-07-10 | CSN6620 | - | Jul 10, 09:05 UTC | Jul 10, 09:15 UTC | 10m |
| 2026-07-09 | CSN6619 | - | Jul 9, 14:40 UTC | Jul 10, 02:20 UTC | 11h 40m |
| 2026-07-09 | CSN6620 | - | Jul 9, 10:35 UTC | Jul 9, 10:50 UTC | 15m |
| 2026-07-08 | CSN6476 | - | Jul 8, 15:10 UTC | Jul 9, 01:40 UTC | 10h 30m |
| 2026-07-07 | CSN6420 | - | Jul 7, 17:45 UTC | Jul 8, 09:30 UTC | 15h 45m |
| 2026-07-06 | CSN8255 | - | Jul 6, 06:35 UTC | Jul 6, 14:05 UTC | 7h 30m |
| 2026-07-04 | CSN6194 | - | Jul 4, 09:10 UTC | Jul 5, 01:00 UTC | 15h 50m |
| 2026-07-03 | CSN6364 | - | Jul 3, 07:25 UTC | Jul 3, 07:45 UTC | 20m |
| 2026-07-01 | CSN6442 | - | Jul 1, 08:05 UTC | Jul 1, 08:20 UTC | 15m |
| 2026-06-30 | CSN8256 | CKG → CGQ | Jun 30, 13:30 UTC | Jul 1, 08:20 UTC | 18h 50m |
| 2026-06-29 | CSN6194 | - | Jun 29, 09:25 UTC | Jun 29, 09:34 UTC | 10m |
| 2026-06-27 | CSN6420 | - | Jun 27, 08:20 UTC | Jun 28, 01:04 UTC | 16h 45m |
| 2026-06-26 | CSN5954 | CGO → CGQ | Jun 26, 13:04 UTC | Jun 27, 01:09 UTC | 12h 5m |
| 2026-06-25 | CSN5953 | CGO → HAK | Jun 25, 21:10 UTC | Jun 26, 06:35 UTC | 9h 25m |
| 2026-06-25 | CSN6541 | - | Jun 25, 01:35 UTC | Jun 25, 02:10 UTC | 35m |
| 2026-06-24 | CSN6180 | - | Jun 24, 00:59 UTC | Jun 24, 01:09 UTC | 10m |
| 2026-06-20 | CSN8460 | CAN → CGQ | Jun 20, 04:59 UTC | Jun 20, 05:24 UTC | 25m |
| 2026-06-18 | CSN5470 | - | Jun 18, 05:30 UTC | Jun 18, 06:00 UTC | 30m |
| 2026-06-17 | CSN5470 | - | Jun 17, 07:45 UTC | Jun 18, 06:00 UTC | 22h 15m |
| 2026-06-12 | CSN6541 | - | Jun 12, 07:15 UTC | Jun 13, 02:00 UTC | 18h 45m |
| 2026-06-11 | CSN6358 | SZX → CGQ | Jun 11, 08:55 UTC | Jun 12, 07:45 UTC | 22h 50m |
| 2026-06-11 | CSN6358 | SZX → CGQ | Jun 11, 06:30 UTC | Jun 11, 06:40 UTC | 10m |
| 2026-06-11 | CSN6357 | CGQ → SZX | Jun 11, 03:55 UTC | Jun 11, 04:05 UTC | 10m |
| 2026-06-10 | CSN6357 | CGQ → SZX | Jun 10, 07:20 UTC | Jun 11, 01:40 UTC | 18h 20m |
| 2026-06-09 | CSN8256 | CKG → CGQ | Jun 9, 12:25 UTC | Jun 10, 07:45 UTC | 19h 20m |
| 2026-06-08 | CSN6342 | CAN → CGQ | Jun 8, 07:15 UTC | Jun 8, 07:25 UTC | 10m |
| 2026-06-08 | CSN6341 | CGQ → CAN | Jun 8, 01:00 UTC | Jun 8, 01:20 UTC | 20m |
| 2026-06-07 | CSN6341 | CGQ → CAN | Jun 7, 05:00 UTC | Jun 8, 01:20 UTC | 20h 20m |
| 2026-06-03 | CSN8459 | CGQ → CAN | Jun 3, 12:55 UTC | Jun 4, 03:25 UTC | 14h 30m |
| 2026-06-03 | CSN6541 | CGQ → PVG | Jun 3, 01:40 UTC | Jun 3, 01:55 UTC | 15m |
| 2026-06-02 | CSN6358 | SZX → CGQ | Jun 2, 06:25 UTC | Jun 2, 06:35 UTC | 10m |
| 2026-05-31 | CSN6610 | SZX → CGQ | May 31, 09:00 UTC | May 31, 09:15 UTC | 15m |
| 2026-05-31 | CSN6180 | PKX → CGQ | May 31, 00:45 UTC | May 31, 00:55 UTC | 10m |
| 2026-05-29 | CSN6168 | PKX → CGQ | May 29, 12:35 UTC | May 30, 07:45 UTC | 19h 10m |
| 2026-05-29 | CSN6146 | PKX → CGQ | May 29, 03:50 UTC | May 29, 04:00 UTC | 10m |
| 2026-05-28 | CSN6146 | PKX → CGQ | May 28, 03:45 UTC | May 28, 04:00 UTC | 15m |
| 2026-05-27 | CSN6194 | PKX → CGQ | May 27, 09:50 UTC | May 27, 10:00 UTC | 10m |
| 2026-05-26 | CSN6364 | CKG → CGQ | May 26, 07:24 UTC | May 26, 07:45 UTC | 20m |
| 2026-05-25 | CSN6364 | CKG → CGQ | May 25, 09:45 UTC | May 26, 07:45 UTC | 21h 59m |
| 2026-05-21 | CSN6545 | CGQ → HGH | May 21, 00:15 UTC | May 21, 00:55 UTC | 40m |
| 2026-05-19 | CSN6364 | CKG → CGQ | May 19, 07:35 UTC | May 19, 07:55 UTC | 20m |
| 2026-05-18 | CSN6364 | CKG → CGQ | May 18, 12:00 UTC | May 19, 07:55 UTC | 19h 54m |
| 2026-05-18 | CSN6620 | ZUH → WUH | May 18, 07:55 UTC | May 18, 08:05 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-6909 page for operator, model, and routing details .