sensors Mode-S transponder
780E05
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-2029 · BOEING 777-300ER
- Hex
- 780E05
- Octal
- 36007005
- Decimal
- 7,867,909
- Country
- CN
- Tail
- B-2029
- Type
- B77W
- Flights observed
- 111
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 780E05 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 |
|---|---|---|---|
| CSN3098 | - | 15 | 2026-07-13 |
| CSN3097 | - | 15 | 2026-07-13 |
| CSN3095 | China Southern Airlines | 8 | 2026-05-03 |
| CSN660 | - | 6 | 2026-07-14 |
| CSN659 | - | 6 | 2026-07-13 |
| CSN348 | China Southern Airlines | 6 | 2026-07-07 |
| CSN328 | - | 6 | 2026-07-05 |
| CSN327 | - | 6 | 2026-07-04 |
| CSN657 | China Southern Airlines | 5 | 2026-06-13 |
| CSN312 | - | 5 | 2026-07-12 |
| CSN311 | - | 5 | 2026-07-11 |
| CSN385 | - | 4 | 2026-06-13 |
| CSN347 | China Southern Airlines | 4 | 2026-07-06 |
| CSN3096 | China Southern Airlines | 4 | 2026-05-03 |
| CSN658 | China Southern Airlines | 3 | 2026-06-14 |
| CSN386 | China Southern Airlines | 3 | 2026-06-04 |
| CSN699 | China Southern Airlines | 1 | 2026-06-19 |
| CSN6890 | - | 1 | 2026-06-26 |
| CSN600 | China Southern Airlines | 1 | 2026-06-20 |
| CSN330 | - | 1 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CSN660 | - | Jul 14, 07:50 UTC | Jul 14, 08:20 UTC | 30m |
| 2026-07-13 | CSN659 | - | Jul 13, 17:30 UTC | Jul 14, 04:20 UTC | 10h 50m |
| 2026-07-13 | CSN3098 | - | Jul 13, 07:20 UTC | Jul 13, 08:35 UTC | 1h 15m |
| 2026-07-13 | CSN3097 | - | Jul 13, 03:50 UTC | Jul 13, 05:31 UTC | 1h 40m |
| 2026-07-12 | CSN312 | - | Jul 12, 05:35 UTC | Jul 12, 18:01 UTC | 12h 25m |
| 2026-07-11 | CSN311 | - | Jul 11, 22:55 UTC | Jul 12, 01:55 UTC | 3h 0m |
| 2026-07-10 | CSN312 | - | Jul 10, 05:25 UTC | Jul 10, 17:55 UTC | 12h 30m |
| 2026-07-09 | CSN311 | - | Jul 9, 13:40 UTC | Jul 10, 01:50 UTC | 12h 10m |
| 2026-07-07 | CSN348 | CDG → CAN | Jul 7, 10:35 UTC | Jul 7, 16:55 UTC | 6h 20m |
| 2026-07-06 | CSN347 | CAN → CDG | Jul 6, 22:10 UTC | Jul 7, 04:55 UTC | 6h 45m |
| 2026-07-05 | CSN328 | - | Jul 5, 06:55 UTC | Jul 5, 18:30 UTC | 11h 35m |
| 2026-07-04 | CSN327 | - | Jul 4, 17:00 UTC | Jul 5, 03:35 UTC | 10h 35m |
| 2026-07-04 | CSN3098 | - | Jul 4, 11:05 UTC | Jul 4, 11:30 UTC | 25m |
| 2026-07-04 | CSN3097 | - | Jul 4, 08:05 UTC | Jul 4, 09:40 UTC | 1h 35m |
| 2026-07-03 | CSN660 | - | Jul 3, 07:45 UTC | Jul 3, 19:00 UTC | 11h 15m |
| 2026-07-02 | CSN659 | - | Jul 2, 17:15 UTC | Jul 3, 02:55 UTC | 9h 40m |
| 2026-07-01 | CSN3098 | - | Jul 1, 08:00 UTC | Jul 1, 08:25 UTC | 25m |
| 2026-07-01 | CSN3097 | - | Jul 1, 06:10 UTC | Jul 1, 06:35 UTC | 25m |
| 2026-07-01 | CSN3097 | - | Jul 1, 05:15 UTC | Jul 1, 05:35 UTC | 20m |
| 2026-07-01 | - | - | Jul 1, 01:20 UTC | Jul 1, 01:30 UTC | 10m |
| 2026-06-30 | CSN660 | - | Jun 30, 07:45 UTC | Jun 30, 19:10 UTC | 11h 25m |
| 2026-06-29 | CSN659 | - | Jun 29, 17:19 UTC | Jun 30, 02:55 UTC | 9h 36m |
| 2026-06-28 | CSN328 | - | Jun 28, 06:55 UTC | Jun 28, 19:04 UTC | 12h 10m |
| 2026-06-27 | CSN327 | - | Jun 27, 16:24 UTC | Jun 28, 02:34 UTC | 10h 10m |
| 2026-06-26 | CSN6890 | - | Jun 26, 09:59 UTC | Jun 26, 10:10 UTC | 10m |
| 2026-06-22 | CSN3098 | - | Jun 22, 07:04 UTC | Jun 22, 07:30 UTC | 25m |
| 2026-06-22 | CSN3097 | - | Jun 22, 03:35 UTC | Jun 22, 04:59 UTC | 1h 25m |
| 2026-06-20 | CSN600 | JFK → CAN | Jun 20, 05:04 UTC | Jun 20, 18:10 UTC | 13h 5m |
| 2026-06-19 | CSN699 | CAN → JFK | Jun 19, 01:34 UTC | Jun 19, 03:05 UTC | 1h 30m |
| 2026-06-17 | CSN330 | - | Jun 17, 08:15 UTC | Jun 17, 19:30 UTC | 11h 15m |
| 2026-06-16 | CSN329 | - | Jun 16, 19:25 UTC | Jun 17, 04:40 UTC | 9h 16m |
| 2026-06-14 | CSN658 | SFO → CAN | Jun 14, 07:40 UTC | Jun 14, 19:00 UTC | 11h 20m |
| 2026-06-13 | CSN657 | HRB → NRT | Jun 13, 07:20 UTC | Jun 14, 02:55 UTC | 19h 35m |
| 2026-06-13 | CSN657 | HRB → NRT | Jun 13, 06:50 UTC | Jun 14, 02:55 UTC | 20h 5m |
| 2026-06-13 | CSN385 | - | Jun 13, 03:20 UTC | Jun 13, 04:45 UTC | 1h 24m |
| 2026-06-12 | CSN312 | YYZ → CAN | Jun 12, 05:35 UTC | Jun 12, 17:35 UTC | 12h 0m |
| 2026-06-11 | CSN311 | - | Jun 11, 13:40 UTC | Jun 12, 01:40 UTC | 12h 1m |
| 2026-06-09 | CSN660 | SFO → WUH | Jun 9, 07:55 UTC | Jun 9, 19:45 UTC | 11h 50m |
| 2026-06-08 | CSN659 | WUH → SFO | Jun 8, 17:40 UTC | Jun 9, 03:00 UTC | 9h 20m |
| 2026-06-04 | CSN386 | HND → CAN | Jun 4, 07:00 UTC | Jun 4, 08:15 UTC | 1h 15m |
| 2026-06-04 | CSN385 | CAN → HND | Jun 4, 03:25 UTC | Jun 4, 04:40 UTC | 1h 15m |
| 2026-06-03 | CSN3098 | TPE → CAN | Jun 3, 07:25 UTC | Jun 3, 08:20 UTC | 55m |
| 2026-06-03 | CSN3097 | CAN → TPE | Jun 3, 03:45 UTC | Jun 3, 05:10 UTC | 1h 25m |
| 2026-06-01 | CSN312 | YYZ → CAN | Jun 1, 05:40 UTC | Jun 1, 12:25 UTC | 6h 45m |
| 2026-05-31 | CSN311 | CAN → YYZ | May 31, 19:35 UTC | Jun 1, 01:55 UTC | 6h 20m |
| 2026-05-30 | CSN3024 | TPE → CGO | May 30, 03:55 UTC | May 30, 04:15 UTC | 20m |
| 2026-05-30 | CSN3023 | CGO → TPE | May 30, 02:00 UTC | May 30, 02:30 UTC | 30m |
| 2026-05-27 | CSN312 | YYZ → CAN | May 27, 05:35 UTC | May 27, 18:05 UTC | 12h 30m |
| 2026-05-26 | CSN311 | CAN → YYZ | May 26, 13:29 UTC | May 27, 01:49 UTC | 12h 20m |
| 2026-05-24 | CSN3098 | TPE → CAN | May 24, 07:05 UTC | May 24, 08:15 UTC | 1h 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-2029 page for operator, model, and routing details .