sensors Mode-S transponder
780653
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6670 · AIRBUS A-320
- Hex
- 780653
- Octal
- 36003123
- Decimal
- 7,865,939
- Country
- CN
- Tail
- B-6670
- Type
- A320
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address 780653 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 |
|---|---|---|---|
| CBG8964 | - | 3 | 2026-06-20 |
| CBG8950 | - | 3 | 2026-07-16 |
| CBG8823 | - | 3 | 2026-05-26 |
| CBG8889 | - | 2 | 2026-06-22 |
| CBG8871 | - | 2 | 2026-07-23 |
| CBG7859 | - | 2 | 2026-05-20 |
| CBG8980 | - | 1 | 2026-07-02 |
| CBG8978 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-12 |
| CBG8976 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-17 |
| CBG8975 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-17 |
| CBG8969 | Guangxi Beibu Gulf Airlines | 1 | 2026-05-01 |
| CBG8949 | - | 1 | 2026-06-27 |
| CBG8932 | - | 1 | 2026-07-08 |
| CBG8930 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-11 |
| CBG8927 | Guangxi Beibu Gulf Airlines | 1 | 2026-07-25 |
| CBG8906 | - | 1 | 2026-05-16 |
| CBG8905 | - | 1 | 2026-04-30 |
| CBG8847 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-08 |
| CBG8840 | - | 1 | 2026-07-07 |
| CBG8839 | Guangxi Beibu Gulf Airlines | 1 | 2026-07-23 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | CBG8927 | NNG → VTE | Jul 25, 09:50 UTC | Jul 25, 12:30 UTC | 2h 40m |
| 2026-07-23 | CBG8871 | - | Jul 23, 23:25 UTC | Jul 24, 18:35 UTC | 19h 10m |
| 2026-07-23 | CBG8815 | ZUH → HIA | Jul 23, 09:40 UTC | Jul 23, 09:55 UTC | 15m |
| 2026-07-23 | CBG8839 | HRB → SQD | Jul 23, 02:20 UTC | Jul 23, 05:30 UTC | 3h 10m |
| 2026-07-16 | CBG8950 | - | Jul 16, 00:00 UTC | Jul 16, 09:35 UTC | 9h 35m |
| 2026-07-15 | CBG8813 | - | Jul 15, 05:35 UTC | Jul 15, 05:50 UTC | 15m |
| 2026-07-14 | CBG8950 | - | Jul 14, 10:50 UTC | Jul 14, 11:00 UTC | 10m |
| 2026-07-08 | CBG8932 | - | Jul 8, 16:45 UTC | Jul 8, 16:55 UTC | 10m |
| 2026-07-07 | CBG8840 | - | Jul 7, 05:15 UTC | Jul 7, 05:35 UTC | 20m |
| 2026-07-02 | CBG8980 | - | Jul 2, 15:50 UTC | Jul 2, 16:10 UTC | 20m |
| 2026-06-30 | CBG8824 | - | Jun 30, 06:00 UTC | Jun 30, 10:50 UTC | 4h 50m |
| 2026-06-27 | CBG8949 | - | Jun 27, 00:10 UTC | Jun 27, 10:00 UTC | 9h 50m |
| 2026-06-23 | CBG8871 | - | Jun 23, 00:54 UTC | Jun 23, 13:24 UTC | 12h 30m |
| 2026-06-22 | CBG8889 | - | Jun 22, 04:15 UTC | Jun 22, 15:59 UTC | 11h 45m |
| 2026-06-21 | CBG8889 | - | Jun 21, 16:25 UTC | Jun 22, 06:39 UTC | 14h 15m |
| 2026-06-20 | CBG8964 | - | Jun 20, 08:55 UTC | Jun 20, 09:05 UTC | 10m |
| 2026-06-17 | CBG8975 | SYX → LYA | Jun 17, 11:15 UTC | Jun 17, 11:30 UTC | 15m |
| 2026-06-17 | CBG8976 | LYA → SYX | Jun 17, 08:25 UTC | Jun 17, 08:50 UTC | 25m |
| 2026-06-14 | CBG8822 | - | Jun 14, 15:20 UTC | Jun 14, 15:40 UTC | 20m |
| 2026-06-13 | CBG8964 | - | Jun 13, 09:00 UTC | Jun 13, 11:30 UTC | 2h 30m |
| 2026-06-12 | CBG8978 | KOW → NNG | Jun 12, 00:20 UTC | Jun 12, 09:20 UTC | 9h 0m |
| 2026-06-11 | CBG8930 | HDG → SYX | Jun 11, 06:55 UTC | Jun 12, 00:30 UTC | 17h 35m |
| 2026-06-09 | CBG8950 | KOW → NNG | Jun 9, 00:05 UTC | Jun 9, 10:00 UTC | 9h 55m |
| 2026-06-08 | CBG8847 | NNG → FOC | Jun 8, 08:00 UTC | Jun 9, 00:05 UTC | 16h 5m |
| 2026-05-28 | CBG8964 | JNG → SYX | May 28, 09:10 UTC | May 28, 09:25 UTC | 15m |
| 2026-05-26 | CBG8823 | - | May 26, 03:50 UTC | May 26, 08:24 UTC | 4h 35m |
| 2026-05-20 | CBG7860 | - | May 20, 08:10 UTC | May 20, 08:20 UTC | 10m |
| 2026-05-20 | CBG7859 | - | May 20, 01:50 UTC | May 20, 02:00 UTC | 10m |
| 2026-05-16 | CBG8906 | - | May 16, 04:40 UTC | May 16, 04:55 UTC | 15m |
| 2026-05-06 | CBG7859 | - | May 6, 01:40 UTC | May 6, 01:55 UTC | 15m |
| 2026-05-02 | CBG8823 | - | May 2, 06:10 UTC | May 2, 11:00 UTC | 4h 50m |
| 2026-05-01 | CBG8823 | - | May 1, 11:50 UTC | May 2, 10:45 UTC | 22h 55m |
| 2026-05-01 | CBG8969 | HAK → ZUH | May 1, 02:25 UTC | May 1, 02:35 UTC | 10m |
| 2026-04-30 | CBG8905 | - | Apr 30, 04:55 UTC | Apr 30, 06:55 UTC | 2h 0m |
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-6670 page for operator, model, and routing details .