sensors Mode-S transponder
780E58
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8148 · AIRBUS A-320
- Hex
- 780E58
- Octal
- 36007130
- Decimal
- 7,867,992
- Country
- CN
- Tail
- B-8148
- Type
- A320
- Flights observed
- 43
- Distinct callsigns
- 15
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 780E58 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CDC8007 | - | 6 | 2026-07-07 |
| CDC8866 | - | 5 | 2026-07-04 |
| CDC6054 | - | 5 | 2026-07-15 |
| CDC8870 | - | 3 | 2026-07-13 |
| CDC8054 | - | 3 | 2026-07-15 |
| CDC8053 | - | 3 | 2026-07-15 |
| CDC8021 | Zhejiang Loong Airlines | 3 | 2026-04-17 |
| CDC8008 | - | 3 | 2026-07-07 |
| CDC6053 | - | 3 | 2026-07-15 |
| CDC8706 | Zhejiang Loong Airlines | 2 | 2026-06-09 |
| CDC8241 | - | 2 | 2026-07-10 |
| CDC8022 | Zhejiang Loong Airlines | 2 | 2026-04-17 |
| CDC8869 | - | 1 | 2026-06-08 |
| CDC8565 | - | 1 | 2026-05-17 |
| CDC8285 | Zhejiang Loong Airlines | 1 | 2026-04-25 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | CDC8054 | - | Jul 15, 11:25 UTC | Jul 15, 12:30 UTC | 1h 5m |
| 2026-07-15 | CDC8053 | - | Jul 15, 08:20 UTC | Jul 15, 09:10 UTC | 50m |
| 2026-07-15 | CDC6054 | - | Jul 15, 03:50 UTC | Jul 15, 04:00 UTC | 10m |
| 2026-07-15 | CDC6053 | - | Jul 15, 00:20 UTC | Jul 15, 00:40 UTC | 20m |
| 2026-07-13 | CDC8870 | - | Jul 13, 11:50 UTC | Jul 13, 12:05 UTC | 15m |
| 2026-07-12 | CDC8870 | - | Jul 12, 11:35 UTC | Jul 12, 11:55 UTC | 20m |
| 2026-07-10 | CDC8241 | - | Jul 10, 11:55 UTC | Jul 11, 05:01 UTC | 17h 6m |
| 2026-07-07 | CDC8008 | - | Jul 7, 06:15 UTC | Jul 7, 12:30 UTC | 6h 15m |
| 2026-07-07 | CDC8007 | - | Jul 7, 03:30 UTC | Jul 7, 04:20 UTC | 50m |
| 2026-07-06 | CDC8007 | - | Jul 6, 06:15 UTC | Jul 7, 04:20 UTC | 22h 5m |
| 2026-07-06 | CDC8007 | - | Jul 6, 03:20 UTC | Jul 6, 04:30 UTC | 1h 10m |
| 2026-07-04 | CDC8866 | - | Jul 4, 17:55 UTC | Jul 4, 18:35 UTC | 40m |
| 2026-07-02 | CDC8866 | - | Jul 2, 14:35 UTC | Jul 2, 15:05 UTC | 30m |
| 2026-06-27 | CDC6054 | - | Jun 27, 03:20 UTC | Jun 27, 03:34 UTC | 15m |
| 2026-06-27 | CDC6053 | - | Jun 27, 00:05 UTC | Jun 27, 00:20 UTC | 15m |
| 2026-06-26 | CDC6054 | - | Jun 26, 02:09 UTC | Jun 26, 02:20 UTC | 10m |
| 2026-06-25 | CDC6053 | - | Jun 25, 23:55 UTC | Jun 26, 00:15 UTC | 20m |
| 2026-06-25 | CDC8866 | - | Jun 25, 14:29 UTC | Jun 25, 14:59 UTC | 30m |
| 2026-06-24 | CDC8054 | - | Jun 24, 10:04 UTC | Jun 24, 11:14 UTC | 1h 10m |
| 2026-06-24 | CDC8053 | - | Jun 24, 08:09 UTC | Jun 24, 08:24 UTC | 15m |
| 2026-06-23 | CDC8866 | - | Jun 23, 14:19 UTC | Jun 23, 15:04 UTC | 45m |
| 2026-06-22 | CDC8054 | - | Jun 22, 09:49 UTC | Jun 22, 10:10 UTC | 20m |
| 2026-06-22 | CDC8053 | - | Jun 22, 07:34 UTC | Jun 22, 07:49 UTC | 15m |
| 2026-06-18 | CDC8008 | - | Jun 18, 12:10 UTC | Jun 18, 12:25 UTC | 15m |
| 2026-06-18 | CDC8007 | - | Jun 18, 08:25 UTC | Jun 18, 08:50 UTC | 25m |
| 2026-06-18 | CDC8007 | - | Jun 18, 04:15 UTC | Jun 18, 05:15 UTC | 1h 0m |
| 2026-06-17 | CDC8866 | - | Jun 17, 14:20 UTC | Jun 17, 15:00 UTC | 40m |
| 2026-06-12 | CDC6054 | ZUH → HGH | Jun 12, 02:40 UTC | Jun 12, 02:50 UTC | 10m |
| 2026-06-09 | CDC8706 | VTE → HGH | Jun 9, 07:30 UTC | Jun 9, 11:45 UTC | 4h 15m |
| 2026-06-08 | CDC8706 | VTE → HGH | Jun 8, 12:10 UTC | Jun 9, 11:45 UTC | 23h 35m |
| 2026-06-08 | CDC8870 | - | Jun 8, 08:05 UTC | Jun 9, 07:40 UTC | 23h 35m |
| 2026-06-08 | CDC8869 | - | Jun 8, 05:35 UTC | Jun 8, 05:45 UTC | 10m |
| 2026-06-05 | CDC8008 | HKG → HGH | Jun 5, 06:20 UTC | Jun 5, 15:20 UTC | 9h 0m |
| 2026-06-05 | CDC8007 | HGH → HKG | Jun 5, 03:40 UTC | Jun 5, 04:25 UTC | 45m |
| 2026-05-17 | CDC8565 | - | May 17, 01:20 UTC | May 17, 05:15 UTC | 3h 55m |
| 2026-05-03 | CDC6054 | ZUH → HGH | May 3, 02:45 UTC | May 3, 03:00 UTC | 15m |
| 2026-04-25 | CDC8285 | HGH → CAN | Apr 25, 16:45 UTC | Apr 25, 17:00 UTC | 15m |
| 2026-04-17 | CDC8022 | BKK → HGH | Apr 17, 12:55 UTC | Apr 17, 13:05 UTC | 10m |
| 2026-04-17 | CDC8022 | BKK → HGH | Apr 17, 10:55 UTC | Apr 17, 11:10 UTC | 15m |
| 2026-04-17 | CDC8021 | HGH → BKK | Apr 17, 09:20 UTC | Apr 17, 09:30 UTC | 10m |
| 2026-04-17 | CDC8021 | HGH → BKK | Apr 17, 09:00 UTC | Apr 17, 09:15 UTC | 15m |
| 2026-04-17 | CDC8021 | HGH → BKK | Apr 17, 06:50 UTC | Apr 17, 07:15 UTC | 25m |
| 2026-04-16 | CDC8241 | - | Apr 16, 05:20 UTC | Apr 16, 05:45 UTC | 25m |
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-8148 page for operator, model, and routing details .