sensors Mode-S transponder
780773
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5598 · BOEING 737-800
- Hex
- 780773
- Octal
- 36003563
- Decimal
- 7,866,227
- Country
- CN
- Tail
- B-5598
- Type
- B738
- Flights observed
- 39
- Distinct callsigns
- 10
- Country
- CN
- Last broadcast
- 17m ago
Current position
Country allocation
The ICAO 24-bit address 780773 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 10 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSN5104 | - | 16 | 2026-07-14 |
| CSN6222 | - | 8 | 2026-07-07 |
| CSN5103 | - | 4 | 2026-07-12 |
| CSN3987 | - | 2 | 2026-07-09 |
| CSN3581 | China Southern Airlines | 2 | 2026-04-14 |
| CSN3292 | China Southern Airlines | 2 | 2026-04-25 |
| CSN3278 | China Southern Airlines | 2 | 2026-06-06 |
| CSN6318 | China Southern Airlines | 1 | 2026-04-29 |
| CSN3988 | - | 1 | 2026-07-09 |
| CSN3296 | China Southern Airlines | 1 | 2026-04-15 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CSN5104 | - | Jul 14, 14:30 UTC | Jul 14, 14:40 UTC | 10m |
| 2026-07-13 | CSN5104 | - | Jul 13, 14:50 UTC | Jul 14, 12:10 UTC | 21h 20m |
| 2026-07-13 | CSN5104 | - | Jul 13, 14:30 UTC | Jul 14, 12:10 UTC | 21h 40m |
| 2026-07-12 | CSN5104 | - | Jul 12, 14:50 UTC | Jul 13, 12:05 UTC | 21h 15m |
| 2026-07-12 | CSN5104 | - | Jul 12, 14:20 UTC | Jul 12, 15:05 UTC | 45m |
| 2026-07-12 | CSN5103 | - | Jul 12, 11:40 UTC | Jul 12, 11:55 UTC | 15m |
| 2026-07-10 | CSN5104 | - | Jul 10, 13:05 UTC | Jul 11, 09:45 UTC | 20h 41m |
| 2026-07-09 | CSN3988 | - | Jul 9, 09:40 UTC | Jul 9, 09:50 UTC | 10m |
| 2026-07-09 | CSN3987 | - | Jul 9, 05:30 UTC | Jul 9, 05:50 UTC | 20m |
| 2026-07-08 | CSN5104 | - | Jul 8, 14:25 UTC | Jul 8, 14:55 UTC | 30m |
| 2026-07-08 | CSN5103 | - | Jul 8, 00:45 UTC | Jul 8, 12:15 UTC | 11h 30m |
| 2026-07-07 | CSN6222 | - | Jul 7, 03:40 UTC | Jul 8, 00:50 UTC | 21h 10m |
| 2026-07-06 | CSN6222 | - | Jul 6, 04:55 UTC | Jul 6, 05:35 UTC | 40m |
| 2026-07-05 | CSN3987 | - | Jul 5, 05:50 UTC | Jul 6, 01:35 UTC | 19h 45m |
| 2026-07-04 | CSN5104 | - | Jul 4, 11:50 UTC | Jul 5, 06:05 UTC | 18h 15m |
| 2026-07-03 | CSN6222 | - | Jul 3, 12:10 UTC | Jul 4, 05:00 UTC | 16h 50m |
| 2026-07-02 | CSN6222 | - | Jul 2, 01:05 UTC | Jul 2, 04:45 UTC | 3h 40m |
| 2026-07-01 | CSN5104 | - | Jul 1, 11:45 UTC | Jul 1, 15:10 UTC | 3h 25m |
| 2026-06-28 | CSN5104 | - | Jun 28, 12:05 UTC | Jun 28, 15:40 UTC | 3h 35m |
| 2026-06-27 | CSN5104 | - | Jun 27, 11:59 UTC | Jun 27, 15:49 UTC | 3h 50m |
| 2026-06-26 | CSN5104 | - | Jun 26, 14:55 UTC | Jun 26, 15:45 UTC | 50m |
| 2026-06-25 | CSN5104 | - | Jun 25, 14:34 UTC | Jun 25, 15:20 UTC | 45m |
| 2026-06-25 | CSN5103 | - | Jun 25, 12:19 UTC | Jun 25, 12:35 UTC | 15m |
| 2026-06-22 | CSN6222 | - | Jun 22, 01:05 UTC | Jun 22, 04:19 UTC | 3h 15m |
| 2026-06-15 | CSN5104 | - | Jun 15, 12:00 UTC | Jun 15, 16:35 UTC | 4h 35m |
| 2026-06-06 | CSN3278 | PKX → NNG | Jun 6, 04:55 UTC | Jun 6, 05:05 UTC | 10m |
| 2026-06-05 | CSN6222 | XMN → NNG | Jun 5, 01:15 UTC | Jun 5, 04:55 UTC | 3h 40m |
| 2026-05-29 | CSN5104 | - | May 29, 14:45 UTC | May 29, 15:20 UTC | 35m |
| 2026-05-29 | CSN5103 | - | May 29, 12:20 UTC | May 29, 12:40 UTC | 20m |
| 2026-05-23 | CSN5104 | - | May 23, 11:50 UTC | May 23, 15:00 UTC | 3h 10m |
| 2026-04-29 | CSN6318 | HRB → WUH | Apr 29, 04:29 UTC | Apr 29, 09:05 UTC | 4h 36m |
| 2026-04-26 | CSN3278 | PKX → NNG | Apr 26, 05:00 UTC | Apr 26, 05:10 UTC | 10m |
| 2026-04-25 | CSN3292 | NNY → CAN | Apr 25, 02:05 UTC | Apr 25, 02:15 UTC | 10m |
| 2026-04-19 | CSN6222 | XMN → NNG | Apr 19, 02:00 UTC | Apr 19, 05:10 UTC | 3h 10m |
| 2026-04-17 | CSN6222 | XMN → NNG | Apr 17, 04:35 UTC | Apr 17, 05:00 UTC | 25m |
| 2026-04-15 | CSN3296 | CAN → NNG | Apr 15, 13:40 UTC | Apr 15, 13:50 UTC | 10m |
| 2026-04-15 | CSN3292 | NNY → CAN | Apr 15, 02:05 UTC | Apr 15, 02:15 UTC | 10m |
| 2026-04-14 | CSN3581 | CAN → SHA | Apr 14, 11:05 UTC | Apr 14, 11:25 UTC | 20m |
| 2026-04-14 | CSN3581 | CAN → SHA | Apr 14, 10:25 UTC | Apr 14, 10:35 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-5598 page for operator, model, and routing details .