sensors Mode-S transponder
781089
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-8733 · AIRBUS A-320
- Hex
- 781089
- Octal
- 36010211
- Decimal
- 7,868,553
- Country
- CN
- Tail
- B-8733
- Type
- A320
- Flights observed
- 36
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 781089 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 |
|---|---|---|---|
| CBG8969 | Guangxi Beibu Gulf Airlines | 3 | 2026-06-10 |
| CBG8928 | - | 3 | 2026-07-16 |
| CBG8840 | - | 3 | 2026-07-14 |
| CBG8963 | Guangxi Beibu Gulf Airlines | 2 | 2026-07-07 |
| CBG8872 | - | 2 | 2026-04-23 |
| CBG8871 | - | 2 | 2026-05-06 |
| CBG8850 | - | 2 | 2026-07-04 |
| CBG8823 | - | 2 | 2026-06-11 |
| CBG8815 | - | 2 | 2026-07-14 |
| CBG8976 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-19 |
| CBG8970 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-08 |
| CBG8962 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-07 |
| CBG8950 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-16 |
| CBG8918 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-23 |
| CBG8917 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-23 |
| CBG8906 | - | 1 | 2026-05-05 |
| CBG8849 | - | 1 | 2026-06-30 |
| CBG8847 | - | 1 | 2026-06-28 |
| CBG8822 | - | 1 | 2026-06-26 |
| CBG8820 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-06 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | CBG8928 | - | Jul 16, 09:35 UTC | Jul 16, 12:44 UTC | 3h 10m |
| 2026-07-14 | CBG8815 | - | Jul 14, 10:25 UTC | Jul 14, 10:35 UTC | 10m |
| 2026-07-14 | CBG8840 | - | Jul 14, 06:30 UTC | Jul 14, 06:45 UTC | 15m |
| 2026-07-08 | - | - | Jul 8, 08:40 UTC | Jul 8, 08:50 UTC | 10m |
| 2026-07-07 | CBG8963 | SYX → JNG | Jul 7, 12:25 UTC | Jul 8, 08:50 UTC | 20h 25m |
| 2026-07-07 | CBG8963 | SYX → JNG | Jul 7, 08:55 UTC | Jul 7, 12:35 UTC | 3h 40m |
| 2026-07-04 | CBG8850 | - | Jul 4, 08:55 UTC | Jul 4, 12:20 UTC | 3h 25m |
| 2026-06-30 | CBG8850 | - | Jun 30, 08:25 UTC | Jun 30, 08:35 UTC | 10m |
| 2026-06-30 | CBG8849 | - | Jun 30, 04:50 UTC | Jun 30, 05:00 UTC | 10m |
| 2026-06-28 | CBG8847 | - | Jun 28, 08:34 UTC | Jun 29, 06:09 UTC | 21h 35m |
| 2026-06-26 | CBG8822 | - | Jun 26, 15:05 UTC | Jun 26, 15:25 UTC | 20m |
| 2026-06-23 | CBG8918 | HAN → KWL | Jun 23, 08:45 UTC | Jun 24, 01:55 UTC | 17h 10m |
| 2026-06-23 | CBG8917 | KWL → HAN | Jun 23, 06:24 UTC | Jun 23, 06:55 UTC | 30m |
| 2026-06-19 | CBG8976 | LYA → SYX | Jun 19, 08:24 UTC | Jun 19, 08:44 UTC | 20m |
| 2026-06-13 | CBG8928 | VTE → NNG | Jun 13, 09:35 UTC | Jun 13, 12:35 UTC | 3h 0m |
| 2026-06-12 | CBG8928 | VTE → NNG | Jun 12, 17:35 UTC | Jun 13, 12:35 UTC | 18h 59m |
| 2026-06-11 | CBG8823 | - | Jun 11, 06:10 UTC | Jun 11, 10:40 UTC | 4h 30m |
| 2026-06-10 | CBG8823 | - | Jun 10, 13:05 UTC | Jun 11, 10:40 UTC | 21h 35m |
| 2026-06-10 | CBG8969 | HAK → ZUH | Jun 10, 02:10 UTC | Jun 10, 02:20 UTC | 10m |
| 2026-06-09 | CBG8840 | SQD → HRB | Jun 9, 01:10 UTC | Jun 9, 04:25 UTC | 3h 15m |
| 2026-06-08 | CBG8970 | ZUH → HAK | Jun 8, 07:35 UTC | Jun 8, 07:50 UTC | 15m |
| 2026-06-08 | CBG8969 | HAK → ZUH | Jun 8, 02:05 UTC | Jun 8, 02:15 UTC | 10m |
| 2026-06-07 | CBG8962 | HDG → HAK | Jun 7, 07:20 UTC | Jun 7, 07:30 UTC | 10m |
| 2026-06-06 | CBG8820 | TSN → YIH | Jun 6, 10:00 UTC | Jun 6, 10:14 UTC | 15m |
| 2026-06-06 | CBG8819 | ZUH → LYA | Jun 6, 04:10 UTC | Jun 6, 04:20 UTC | 10m |
| 2026-05-06 | CBG8871 | - | May 6, 11:50 UTC | May 6, 12:01 UTC | 10m |
| 2026-05-06 | CBG8969 | HAK → ZUH | May 6, 02:10 UTC | May 6, 02:25 UTC | 15m |
| 2026-05-05 | CBG8906 | - | May 5, 04:50 UTC | May 5, 05:00 UTC | 10m |
| 2026-05-03 | CBG7860 | - | May 3, 07:55 UTC | May 3, 08:05 UTC | 10m |
| 2026-05-03 | CBG7859 | - | May 3, 01:35 UTC | May 3, 01:50 UTC | 15m |
| 2026-04-28 | CBG8815 | ZUH → HIA | Apr 28, 09:20 UTC | Apr 28, 09:35 UTC | 15m |
| 2026-04-28 | CBG8840 | SQD → HRB | Apr 28, 02:00 UTC | Apr 28, 05:05 UTC | 3h 5m |
| 2026-04-23 | CBG8872 | - | Apr 23, 01:00 UTC | Apr 23, 17:10 UTC | 16h 10m |
| 2026-04-21 | CBG8871 | - | Apr 21, 00:50 UTC | Apr 21, 16:10 UTC | 15h 20m |
| 2026-04-20 | CBG8872 | - | Apr 20, 16:30 UTC | Apr 21, 16:10 UTC | 23h 40m |
| 2026-04-16 | CBG8950 | KOW → NNG | Apr 16, 09:24 UTC | Apr 16, 09:39 UTC | 15m |
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-8733 page for operator, model, and routing details .