sensors Mode-S transponder
7802E3
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5191 · BOEING 737-800
- Hex
- 7802E3
- Octal
- 36001343
- Decimal
- 7,865,059
- Country
- CN
- Tail
- B-5191
- Type
- B738
- Flights observed
- 50
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 7802E3 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 |
|---|---|---|---|
| CSN5052 | China Southern Airlines | 7 | 2026-06-06 |
| CSN5051 | China Southern Airlines | 5 | 2026-06-06 |
| CSN8280 | - | 3 | 2026-07-07 |
| CSN3368 | China Southern Airlines | 3 | 2026-07-22 |
| CSN8476 | China Southern Airlines | 2 | 2026-05-29 |
| CSN3631 | - | 2 | 2026-07-02 |
| CSN3536 | China Southern Airlines | 2 | 2026-07-24 |
| CSN3140 | China Southern Airlines | 2 | 2026-05-17 |
| CSN8475 | China Southern Airlines | 1 | 2026-05-20 |
| CSN8464 | China Southern Airlines | 1 | 2026-04-28 |
| CSN8463 | China Southern Airlines | 1 | 2026-04-27 |
| CSN8279 | - | 1 | 2026-07-14 |
| CSN6594 | China Southern Airlines | 1 | 2026-07-25 |
| CSN6590 | China Southern Airlines | 1 | 2026-05-01 |
| CSN6080 | China Southern Airlines | 1 | 2026-06-12 |
| CSN6079 | China Southern Airlines | 1 | 2026-06-12 |
| CSN6050 | China Southern Airlines | 1 | 2026-06-05 |
| CSN6049 | China Southern Airlines | 1 | 2026-06-05 |
| CSN5627 | - | 1 | 2026-07-12 |
| CSN3872 | China Southern Airlines | 1 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | CSN6594 | CGO → CAN | Jul 25, 15:50 UTC | Jul 25, 16:00 UTC | 10m |
| 2026-07-24 | CSN3536 | TAO → CAN | Jul 24, 11:25 UTC | Jul 24, 11:40 UTC | 15m |
| 2026-07-24 | CSN3872 | NKG → CAN | Jul 24, 02:35 UTC | Jul 24, 02:45 UTC | 10m |
| 2026-07-22 | CSN3871 | - | Jul 22, 12:30 UTC | Jul 22, 12:40 UTC | 10m |
| 2026-07-22 | CSN3368 | WUH → CAN | Jul 22, 02:05 UTC | Jul 22, 02:15 UTC | 10m |
| 2026-07-17 | CSN3368 | WUH → CAN | Jul 17, 01:45 UTC | Jul 17, 01:55 UTC | 10m |
| 2026-07-14 | CSN8279 | - | Jul 14, 09:15 UTC | Jul 14, 13:05 UTC | 3h 50m |
| 2026-07-14 | - | - | Jul 14, 02:20 UTC | Jul 14, 02:30 UTC | 10m |
| 2026-07-13 | CSN3536 | - | Jul 13, 10:30 UTC | Jul 13, 10:45 UTC | 15m |
| 2026-07-13 | - | - | Jul 13, 01:40 UTC | Jul 13, 01:50 UTC | 10m |
| 2026-07-12 | CSN5627 | - | Jul 12, 09:50 UTC | Jul 12, 14:20 UTC | 4h 30m |
| 2026-07-09 | CSN3345 | WUH → CAN | Jul 9, 11:40 UTC | Jul 9, 11:55 UTC | 15m |
| 2026-07-07 | CSN8280 | - | Jul 7, 10:50 UTC | Jul 7, 14:15 UTC | 3h 25m |
| 2026-07-02 | CSN3631 | - | Jul 2, 01:20 UTC | Jul 2, 01:40 UTC | 20m |
| 2026-06-30 | - | - | Jun 30, 03:45 UTC | Jun 30, 03:55 UTC | 10m |
| 2026-06-28 | CSN3368 | - | Jun 28, 03:14 UTC | Jun 28, 03:29 UTC | 15m |
| 2026-06-23 | CSN8280 | - | Jun 23, 09:20 UTC | Jun 23, 12:49 UTC | 3h 30m |
| 2026-06-22 | CSN3631 | - | Jun 22, 01:25 UTC | Jun 22, 05:44 UTC | 4h 20m |
| 2026-06-20 | CSN3355 | - | Jun 20, 11:20 UTC | Jun 20, 11:40 UTC | 20m |
| 2026-06-12 | CSN6080 | ICN → WUH | Jun 12, 05:45 UTC | Jun 12, 06:10 UTC | 25m |
| 2026-06-12 | CSN6079 | WUH → ICN | Jun 12, 03:05 UTC | Jun 12, 03:40 UTC | 35m |
| 2026-06-11 | CSN3774 | TNA → ZUH | Jun 11, 08:00 UTC | Jun 11, 08:10 UTC | 10m |
| 2026-06-06 | CSN5052 | MNL → CAN | Jun 6, 21:54 UTC | Jun 6, 22:05 UTC | 10m |
| 2026-06-06 | CSN5052 | MNL → CAN | Jun 6, 20:05 UTC | Jun 6, 20:39 UTC | 35m |
| 2026-06-06 | CSN5051 | YYZ → CAN | Jun 6, 17:24 UTC | Jun 6, 18:29 UTC | 1h 5m |
| 2026-06-06 | CSN5051 | YYZ → CAN | Jun 6, 16:30 UTC | Jun 6, 16:39 UTC | 10m |
| 2026-06-05 | CSN6050 | CXR → CAN | Jun 5, 10:45 UTC | Jun 5, 11:05 UTC | 20m |
| 2026-06-05 | CSN6049 | CAN → CXR | Jun 5, 06:05 UTC | Jun 5, 06:15 UTC | 10m |
| 2026-05-29 | CSN3303 | YIW → CAN | May 29, 17:45 UTC | May 29, 17:55 UTC | 10m |
| 2026-05-29 | CSN8476 | CXR → CAN | May 29, 01:20 UTC | May 29, 06:10 UTC | 4h 50m |
| 2026-05-27 | CSN3821 | CAN → NKG | May 27, 05:35 UTC | May 27, 05:45 UTC | 10m |
| 2026-05-25 | CSN8280 | SHE → WUH | May 25, 12:25 UTC | May 25, 12:40 UTC | 15m |
| 2026-05-20 | CSN5052 | MNL → CAN | May 20, 20:00 UTC | May 20, 20:30 UTC | 30m |
| 2026-05-20 | CSN5051 | YYZ → CAN | May 20, 16:50 UTC | May 20, 18:40 UTC | 1h 50m |
| 2026-05-20 | CSN8476 | CXR → CAN | May 20, 06:05 UTC | May 20, 06:25 UTC | 20m |
| 2026-05-20 | CSN8475 | CAN → CXR | May 20, 01:25 UTC | May 20, 01:35 UTC | 10m |
| 2026-05-17 | CSN3140 | PKX → WUH | May 17, 12:45 UTC | May 17, 13:01 UTC | 15m |
| 2026-05-15 | CSN5052 | MNL → CAN | May 15, 21:25 UTC | May 15, 21:45 UTC | 20m |
| 2026-05-15 | CSN5052 | MNL → CAN | May 15, 20:00 UTC | May 15, 20:30 UTC | 30m |
| 2026-05-15 | CSN5051 | YYZ → CAN | May 15, 16:15 UTC | May 15, 18:05 UTC | 1h 50m |
| 2026-05-09 | CSN3780 | NGB → CAN | May 9, 00:50 UTC | May 9, 04:30 UTC | 3h 40m |
| 2026-05-06 | CSN3140 | PKX → WUH | May 6, 12:01 UTC | May 6, 12:20 UTC | 20m |
| 2026-05-06 | CSN3724 | - | May 6, 02:40 UTC | May 6, 02:50 UTC | 10m |
| 2026-05-04 | CSN5052 | MNL → CAN | May 4, 21:50 UTC | May 4, 22:20 UTC | 30m |
| 2026-05-04 | CSN5052 | MNL → CAN | May 4, 20:20 UTC | May 4, 20:50 UTC | 30m |
| 2026-05-04 | CSN5051 | YYZ → CAN | May 4, 16:15 UTC | May 4, 17:55 UTC | 1h 40m |
| 2026-05-03 | - | - | May 3, 07:30 UTC | May 3, 07:40 UTC | 10m |
| 2026-05-01 | CSN6590 | WUH → CAN | May 1, 03:55 UTC | May 1, 04:05 UTC | 10m |
| 2026-04-28 | CSN8464 | SZX → WUH | Apr 28, 00:25 UTC | Apr 28, 00:35 UTC | 10m |
| 2026-04-27 | CSN8463 | WUH → SZX | Apr 27, 15:25 UTC | Apr 27, 15:45 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-5191 page for operator, model, and routing details .