sensors Mode-S transponder
7802F4
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5195 · BOEING 737-800
- Hex
- 7802F4
- Octal
- 36001364
- Decimal
- 7,865,076
- Country
- CN
- Tail
- B-5195
- Type
- B738
- Flights observed
- 35
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address 7802F4 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSN3279 | China Southern Airlines | 8 | 2026-05-30 |
| CSN3280 | China Southern Airlines | 5 | 2026-05-18 |
| CSN6050 | - | 3 | 2026-06-25 |
| CSN3793 | China Southern Airlines | 3 | 2026-05-15 |
| CSN3659 | - | 2 | 2026-07-17 |
| CSN8519 | China Southern Airlines | 1 | 2026-06-07 |
| CSN8476 | - | 1 | 2026-06-22 |
| CSN8475 | - | 1 | 2026-06-22 |
| CSN8262 | - | 1 | 2026-06-03 |
| CSN8261 | - | 1 | 2026-06-20 |
| CSN6632 | - | 1 | 2026-07-10 |
| CSN6049 | - | 1 | 2026-06-25 |
| CSN5885 | - | 1 | 2026-07-22 |
| CSN3794 | China Southern Airlines | 1 | 2026-05-29 |
| CSN3536 | China Southern Airlines | 1 | 2026-06-10 |
| CSN3518 | China Southern Airlines | 1 | 2026-06-01 |
| CSN3292 | China Southern Airlines | 1 | 2026-06-06 |
| CSN3270 | - | 1 | 2026-07-13 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | CSN5885 | - | Jul 22, 11:35 UTC | Jul 22, 14:10 UTC | 2h 35m |
| 2026-07-17 | CSN3659 | - | Jul 17, 01:20 UTC | Jul 17, 01:29 UTC | 10m |
| 2026-07-16 | CSN3659 | - | Jul 16, 01:30 UTC | Jul 16, 01:45 UTC | 15m |
| 2026-07-13 | CSN3270 | - | Jul 13, 14:10 UTC | Jul 13, 14:30 UTC | 20m |
| 2026-07-10 | CSN6632 | - | Jul 10, 14:50 UTC | Jul 10, 15:00 UTC | 10m |
| 2026-06-25 | CSN6050 | - | Jun 25, 15:40 UTC | Jun 25, 15:54 UTC | 15m |
| 2026-06-25 | CSN6050 | - | Jun 25, 11:54 UTC | Jun 25, 12:04 UTC | 10m |
| 2026-06-25 | CSN6050 | - | Jun 25, 10:39 UTC | Jun 25, 10:59 UTC | 20m |
| 2026-06-25 | CSN6049 | - | Jun 25, 06:09 UTC | Jun 25, 06:20 UTC | 10m |
| 2026-06-22 | CSN8476 | - | Jun 22, 06:00 UTC | Jun 22, 06:19 UTC | 20m |
| 2026-06-22 | CSN8475 | - | Jun 22, 01:10 UTC | Jun 22, 01:19 UTC | 10m |
| 2026-06-20 | CSN8261 | - | Jun 20, 13:44 UTC | Jun 20, 13:55 UTC | 10m |
| 2026-06-10 | CSN3536 | TAO → CAN | Jun 10, 10:30 UTC | Jun 10, 10:40 UTC | 10m |
| 2026-06-07 | CSN8519 | WUH → CAN | Jun 7, 17:10 UTC | Jun 7, 17:20 UTC | 10m |
| 2026-06-06 | CSN3292 | NNY → CAN | Jun 6, 02:30 UTC | Jun 6, 02:45 UTC | 15m |
| 2026-06-03 | CSN8262 | - | Jun 3, 01:15 UTC | Jun 3, 01:40 UTC | 25m |
| 2026-06-01 | CSN3518 | NGB → CAN | Jun 1, 08:30 UTC | Jun 1, 08:45 UTC | 15m |
| 2026-05-30 | CSN3279 | SZX → XIY | May 30, 03:20 UTC | May 30, 03:30 UTC | 10m |
| 2026-05-29 | CSN3794 | XIY → SZX | May 29, 15:25 UTC | May 29, 15:45 UTC | 20m |
| 2026-05-18 | CSN3279 | SZX → XIY | May 18, 03:10 UTC | May 18, 03:20 UTC | 10m |
| 2026-05-18 | CSN3280 | XIY → SZX | May 18, 01:15 UTC | May 18, 01:25 UTC | 10m |
| 2026-05-16 | CSN3279 | SZX → XIY | May 16, 03:10 UTC | May 16, 03:20 UTC | 10m |
| 2026-05-16 | CSN3280 | XIY → SZX | May 16, 01:25 UTC | May 16, 01:35 UTC | 10m |
| 2026-05-15 | CSN3793 | SZX → XIY | May 15, 16:40 UTC | May 15, 16:50 UTC | 10m |
| 2026-05-11 | CSN3793 | SZX → XIY | May 11, 14:25 UTC | May 11, 14:35 UTC | 10m |
| 2026-05-10 | CSN3279 | SZX → XIY | May 10, 03:10 UTC | May 10, 03:20 UTC | 10m |
| 2026-05-10 | CSN3280 | XIY → SZX | May 10, 01:14 UTC | May 10, 01:30 UTC | 15m |
| 2026-05-08 | CSN3279 | SZX → XIY | May 8, 03:09 UTC | May 8, 03:19 UTC | 10m |
| 2026-05-08 | CSN3280 | XIY → SZX | May 8, 01:35 UTC | May 8, 01:45 UTC | 10m |
| 2026-05-07 | CSN3279 | SZX → XIY | May 7, 03:20 UTC | May 7, 03:35 UTC | 15m |
| 2026-05-04 | CSN3793 | SZX → XIY | May 4, 14:30 UTC | May 4, 14:45 UTC | 15m |
| 2026-05-01 | CSN3279 | SZX → XIY | May 1, 03:30 UTC | May 1, 03:40 UTC | 10m |
| 2026-05-01 | CSN3280 | XIY → SZX | May 1, 01:45 UTC | May 1, 01:55 UTC | 10m |
| 2026-04-30 | - | - | Apr 30, 10:20 UTC | Apr 30, 10:30 UTC | 10m |
| 2026-04-29 | CSN3279 | SZX → XIY | Apr 29, 03:24 UTC | Apr 29, 03:34 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-5195 page for operator, model, and routing details .