sensors Mode-S transponder
78163D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-306Q · AIRBUS A-320neo
- Hex
- 78163D
- Octal
- 36013075
- Decimal
- 7,870,013
- Country
- CN
- Tail
- B-306Q
- Type
- A20N
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 78163D 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 |
|---|---|---|---|
| CBG8950 | Guangxi Beibu Gulf Airlines | 3 | 2026-06-06 |
| CBG8822 | - | 3 | 2026-06-06 |
| CBG7860 | - | 3 | 2026-06-08 |
| CBG7859 | - | 3 | 2026-06-08 |
| CBG8977 | Guangxi Beibu Gulf Airlines | 2 | 2026-05-08 |
| CBG8932 | - | 2 | 2026-06-02 |
| CBG8928 | Guangxi Beibu Gulf Airlines | 2 | 2026-06-04 |
| CBG8927 | Guangxi Beibu Gulf Airlines | 2 | 2026-06-18 |
| CBG8821 | - | 2 | 2026-05-07 |
| CBG8980 | - | 1 | 2026-06-17 |
| CBG8978 | Guangxi Beibu Gulf Airlines | 1 | 2026-05-08 |
| CBG8969 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-03 |
| CBG8962 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-14 |
| CBG8949 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-21 |
| CBG8931 | - | 1 | 2026-06-02 |
| CBG8918 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-13 |
| CBG8917 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-13 |
| CBG8916 | Guangxi Beibu Gulf Airlines | 1 | 2026-05-27 |
| CBG8915 | Guangxi Beibu Gulf Airlines | 1 | 2026-06-01 |
| CBG8908 | Guangxi Beibu Gulf Airlines | 1 | 2026-05-15 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-18 | CBG8927 | NNG → VTE | Jun 18, 09:30 UTC | Jun 18, 12:35 UTC | 3h 5m |
| 2026-06-17 | CBG8980 | - | Jun 17, 16:10 UTC | Jun 17, 16:30 UTC | 20m |
| 2026-06-14 | CBG8962 | HDG → HAK | Jun 14, 01:35 UTC | Jun 14, 07:25 UTC | 5h 51m |
| 2026-06-13 | CBG8918 | HAN → KWL | Jun 13, 06:20 UTC | Jun 13, 16:45 UTC | 10h 25m |
| 2026-06-13 | CBG8917 | KWL → HAN | Jun 13, 04:20 UTC | Jun 13, 04:45 UTC | 25m |
| 2026-06-08 | CBG7860 | - | Jun 8, 08:00 UTC | Jun 8, 08:10 UTC | 10m |
| 2026-06-08 | CBG7859 | - | Jun 8, 01:45 UTC | Jun 8, 02:00 UTC | 15m |
| 2026-06-06 | CBG8822 | - | Jun 6, 14:40 UTC | Jun 6, 15:25 UTC | 45m |
| 2026-06-06 | CBG8950 | KOW → NNG | Jun 6, 00:05 UTC | Jun 6, 09:45 UTC | 9h 40m |
| 2026-06-05 | CBG7860 | - | Jun 5, 09:25 UTC | Jun 5, 09:35 UTC | 10m |
| 2026-06-05 | CBG7859 | - | Jun 5, 02:35 UTC | Jun 5, 02:50 UTC | 15m |
| 2026-06-04 | CBG8928 | VTE → NNG | Jun 4, 11:45 UTC | Jun 4, 12:35 UTC | 50m |
| 2026-06-04 | CBG8927 | NNG → VTE | Jun 4, 09:20 UTC | Jun 4, 10:00 UTC | 40m |
| 2026-06-03 | CBG8896 | NNY → HAK | Jun 3, 16:20 UTC | Jun 3, 16:30 UTC | 10m |
| 2026-06-03 | CBG8969 | HAK → ZUH | Jun 3, 02:20 UTC | Jun 3, 02:30 UTC | 10m |
| 2026-06-02 | CBG8932 | - | Jun 2, 15:40 UTC | Jun 2, 15:50 UTC | 10m |
| 2026-06-02 | CBG8931 | - | Jun 2, 12:15 UTC | Jun 2, 12:25 UTC | 10m |
| 2026-06-01 | CBG8915 | HAK → NAO | Jun 1, 23:45 UTC | Jun 2, 09:55 UTC | 10h 10m |
| 2026-05-30 | CBG8871 | - | May 30, 00:40 UTC | May 30, 12:25 UTC | 11h 45m |
| 2026-05-29 | CBG8890 | - | May 29, 15:30 UTC | May 29, 15:40 UTC | 10m |
| 2026-05-28 | CBG8932 | - | May 28, 12:10 UTC | May 28, 16:00 UTC | 3h 50m |
| 2026-05-27 | CBG8916 | HFE → NAO | May 27, 23:45 UTC | May 28, 10:15 UTC | 10h 30m |
| 2026-05-19 | CBG8823 | - | May 19, 04:00 UTC | May 19, 08:30 UTC | 4h 30m |
| 2026-05-18 | CBG7860 | - | May 18, 08:15 UTC | May 18, 08:25 UTC | 10m |
| 2026-05-18 | CBG7859 | - | May 18, 01:30 UTC | May 18, 01:45 UTC | 15m |
| 2026-05-16 | CBG8950 | KOW → NNG | May 16, 09:16 UTC | May 16, 09:31 UTC | 15m |
| 2026-05-15 | CBG8908 | BKK → NNG | May 15, 14:15 UTC | May 16, 09:31 UTC | 19h 15m |
| 2026-05-15 | CBG8907 | NNG → BKK | May 15, 11:50 UTC | May 15, 13:00 UTC | 1h 10m |
| 2026-05-12 | CBG8928 | VTE → NNG | May 12, 12:05 UTC | May 12, 12:15 UTC | 10m |
| 2026-05-08 | CBG8978 | KOW → NNG | May 8, 09:19 UTC | May 9, 04:50 UTC | 19h 30m |
| 2026-05-08 | CBG8977 | NNG → KOW | May 8, 00:25 UTC | May 8, 16:35 UTC | 16h 10m |
| 2026-05-07 | CBG8977 | NNG → KOW | May 7, 15:20 UTC | May 8, 09:39 UTC | 18h 19m |
| 2026-05-07 | CBG8822 | - | May 7, 15:05 UTC | May 8, 09:39 UTC | 18h 35m |
| 2026-05-07 | CBG8821 | - | May 7, 12:10 UTC | May 7, 12:30 UTC | 20m |
| 2026-05-07 | CBG8950 | KOW → NNG | May 7, 09:30 UTC | May 7, 09:45 UTC | 15m |
| 2026-05-05 | CBG8872 | - | May 5, 00:50 UTC | May 5, 12:05 UTC | 11h 15m |
| 2026-04-22 | CBG8822 | - | Apr 22, 14:55 UTC | Apr 22, 15:30 UTC | 35m |
| 2026-04-22 | CBG8821 | - | Apr 22, 11:55 UTC | Apr 22, 12:05 UTC | 10m |
| 2026-04-21 | CBG8949 | NNG → KOW | Apr 21, 00:00 UTC | Apr 21, 09:25 UTC | 9h 25m |
| 2026-04-19 | CBG8847 | NNG → FOC | Apr 19, 08:30 UTC | Apr 19, 08:45 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-306Q page for operator, model, and routing details .