sensors Mode-S transponder
7803E5
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6325 · AIRBUS A-320
- Hex
- 7803E5
- Octal
- 36001745
- Decimal
- 7,865,317
- Country
- CN
- Tail
- B-6325
- Type
- A320
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 7803E5 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 |
|---|---|---|---|
| CSC8834 | - | 3 | 2026-07-13 |
| CSC8833 | - | 3 | 2026-07-05 |
| CSC8832 | - | 2 | 2026-07-01 |
| CSC3960 | Sichuan Airlines | 2 | 2026-05-10 |
| CSC3959 | Sichuan Airlines | 2 | 2026-05-10 |
| CSC3940 | Sichuan Airlines | 2 | 2026-06-24 |
| CSC3939 | Sichuan Airlines | 2 | 2026-06-14 |
| CSC3532 | - | 2 | 2026-07-11 |
| CSC3531 | - | 2 | 2026-07-13 |
| CSC3125 | - | 2 | 2026-07-10 |
| CSC8830 | - | 1 | 2026-07-01 |
| CSC8708 | Sichuan Airlines | 1 | 2026-04-18 |
| CSC8707 | Sichuan Airlines | 1 | 2026-04-18 |
| CSC8706 | Sichuan Airlines | 1 | 2026-04-21 |
| CSC8471 | Sichuan Airlines | 1 | 2026-04-24 |
| CSC8061 | - | 1 | 2026-07-02 |
| CSC8004 | - | 1 | 2026-06-26 |
| CSC6727 | Sichuan Airlines | 1 | 2026-06-09 |
| CSC3906 | Sichuan Airlines | 1 | 2026-06-02 |
| CSC3905 | Sichuan Airlines | 1 | 2026-06-01 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CSC8834 | - | Jul 13, 15:10 UTC | Jul 13, 15:30 UTC | 20m |
| 2026-07-13 | CSC3531 | - | Jul 13, 12:30 UTC | Jul 13, 12:55 UTC | 25m |
| 2026-07-11 | CSC3532 | - | Jul 11, 17:15 UTC | Jul 11, 17:40 UTC | 25m |
| 2026-07-11 | CSC3126 | - | Jul 11, 10:10 UTC | Jul 11, 10:35 UTC | 25m |
| 2026-07-10 | CSC3125 | - | Jul 10, 23:55 UTC | Jul 11, 00:20 UTC | 25m |
| 2026-07-09 | CSC3360 | - | Jul 9, 10:10 UTC | Jul 9, 10:30 UTC | 20m |
| 2026-07-07 | CSC3125 | - | Jul 7, 00:05 UTC | Jul 7, 00:25 UTC | 20m |
| 2026-07-06 | CSC3531 | - | Jul 6, 14:25 UTC | Jul 6, 14:50 UTC | 25m |
| 2026-07-05 | CSC3532 | - | Jul 5, 16:20 UTC | Jul 5, 16:45 UTC | 25m |
| 2026-07-05 | CSC8833 | - | Jul 5, 12:35 UTC | Jul 5, 12:50 UTC | 15m |
| 2026-07-04 | CSC3208 | - | Jul 4, 11:55 UTC | Jul 4, 12:05 UTC | 10m |
| 2026-07-02 | CSC8061 | - | Jul 2, 11:05 UTC | Jul 2, 16:25 UTC | 5h 20m |
| 2026-07-01 | CSC8832 | - | Jul 1, 10:50 UTC | Jul 1, 11:05 UTC | 15m |
| 2026-07-01 | CSC8830 | - | Jul 1, 03:10 UTC | Jul 1, 03:30 UTC | 20m |
| 2026-06-30 | CSC8834 | - | Jun 30, 15:15 UTC | Jun 30, 15:35 UTC | 20m |
| 2026-06-30 | CSC8833 | - | Jun 30, 13:25 UTC | Jun 30, 13:45 UTC | 20m |
| 2026-06-29 | CSC8834 | - | Jun 29, 15:04 UTC | Jun 29, 15:30 UTC | 25m |
| 2026-06-29 | CSC8833 | - | Jun 29, 11:20 UTC | Jun 29, 11:35 UTC | 15m |
| 2026-06-26 | CSC8832 | - | Jun 26, 11:40 UTC | Jun 26, 11:55 UTC | 15m |
| 2026-06-26 | CSC8004 | - | Jun 26, 01:29 UTC | Jun 26, 03:39 UTC | 2h 10m |
| 2026-06-24 | CSC3940 | CXR → TFU | Jun 24, 09:19 UTC | Jun 24, 14:15 UTC | 4h 55m |
| 2026-06-15 | CSC3940 | CXR → TFU | Jun 15, 09:25 UTC | Jun 15, 14:30 UTC | 5h 5m |
| 2026-06-14 | CSC3939 | TFU → CXR | Jun 14, 13:40 UTC | Jun 15, 10:00 UTC | 20h 20m |
| 2026-06-14 | CSC3939 | TFU → CXR | Jun 14, 09:30 UTC | Jun 14, 14:05 UTC | 4h 35m |
| 2026-06-09 | CSC6727 | TFU → SYX | Jun 9, 14:00 UTC | Jun 9, 14:25 UTC | 25m |
| 2026-06-04 | CSC3121 | PEK → URC | Jun 4, 13:10 UTC | Jun 4, 13:25 UTC | 15m |
| 2026-06-04 | CSC3122 | URC → PEK | Jun 4, 11:05 UTC | Jun 4, 11:25 UTC | 20m |
| 2026-06-02 | CSC3906 | HAN → TFU | Jun 2, 02:15 UTC | Jun 2, 02:30 UTC | 15m |
| 2026-06-01 | CSC3905 | TFU → HAN | Jun 1, 14:40 UTC | Jun 1, 15:05 UTC | 25m |
| 2026-05-10 | CSC3960 | HKG → TFU | May 10, 10:49 UTC | May 10, 11:15 UTC | 25m |
| 2026-05-10 | CSC3959 | TFU → HKG | May 10, 08:40 UTC | May 10, 09:10 UTC | 30m |
| 2026-05-07 | CSC3272 | DYG → XIY | May 7, 03:05 UTC | May 7, 03:20 UTC | 15m |
| 2026-05-05 | CSC3291 | XIY → CGQ | May 5, 01:15 UTC | May 5, 01:35 UTC | 20m |
| 2026-04-27 | CSC3348 | CGO → HRB | Apr 27, 12:55 UTC | Apr 28, 03:40 UTC | 14h 45m |
| 2026-04-24 | CSC8471 | CTU → HRB | Apr 24, 00:55 UTC | Apr 24, 01:15 UTC | 20m |
| 2026-04-21 | CSC8706 | SZX → CTU | Apr 21, 08:50 UTC | Apr 21, 09:05 UTC | 15m |
| 2026-04-18 | CSC8708 | SZX → CTU | Apr 18, 11:30 UTC | Apr 18, 11:40 UTC | 10m |
| 2026-04-18 | CSC8707 | CTU → SZX | Apr 18, 09:45 UTC | Apr 18, 09:55 UTC | 10m |
| 2026-04-14 | CSC3960 | HKG → TFU | Apr 14, 11:00 UTC | Apr 14, 11:15 UTC | 15m |
| 2026-04-14 | CSC3959 | TFU → HKG | Apr 14, 09:20 UTC | Apr 14, 09:45 UTC | 25m |
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-6325 page for operator, model, and routing details .