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