sensors Mode-S transponder
7815CA
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-304W · AIRBUS A-320neo
- Hex
- 7815CA
- Octal
- 36012712
- Decimal
- 7,869,898
- Country
- CN
- Tail
- B-304W
- Type
- A20N
- Flights observed
- 36
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 7815CA 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 | 4 | 2026-05-29 |
| CBG8970 | Guangxi Beibu Gulf Airlines | 3 | 2026-04-26 |
| CBG8908 | Guangxi Beibu Gulf Airlines | 3 | 2026-05-13 |
| CBG8850 | Guangxi Beibu Gulf Airlines | 3 | 2026-05-26 |
| CBG8822 | - | 3 | 2026-05-21 |
| CBG8907 | Guangxi Beibu Gulf Airlines | 2 | 2026-05-13 |
| CBG8871 | - | 2 | 2026-04-26 |
| CBG8816 | - | 2 | 2026-04-16 |
| CBG8980 | - | 1 | 2026-05-29 |
| CBG8950 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-17 |
| CBG8949 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-18 |
| CBG8906 | - | 1 | 2026-04-23 |
| CBG8905 | - | 1 | 2026-04-23 |
| CBG8876 | Guangxi Beibu Gulf Airlines | 1 | 2026-05-28 |
| CBG8840 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-16 |
| CBG8839 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-16 |
| CBG8820 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-25 |
| CBG8819 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-25 |
| CBG8815 | Guangxi Beibu Gulf Airlines | 1 | 2026-04-16 |
| CBG7859 | - | 1 | 2026-04-20 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | CBG8980 | - | May 29, 13:55 UTC | May 29, 17:55 UTC | 4h 0m |
| 2026-05-29 | - | - | May 29, 09:50 UTC | May 29, 10:05 UTC | 15m |
| 2026-05-29 | CBG8969 | HAK → ZUH | May 29, 02:15 UTC | May 29, 02:35 UTC | 20m |
| 2026-05-28 | CBG8876 | TNA → DYG | May 28, 16:30 UTC | May 28, 16:40 UTC | 10m |
| 2026-05-26 | CBG8850 | SHE → DYG | May 26, 04:35 UTC | May 26, 07:45 UTC | 3h 10m |
| 2026-05-21 | CBG8822 | - | May 21, 16:10 UTC | May 21, 16:35 UTC | 25m |
| 2026-05-14 | CBG8822 | - | May 14, 13:35 UTC | May 14, 17:00 UTC | 3h 25m |
| 2026-05-13 | CBG8908 | BKK → NNG | May 13, 14:35 UTC | May 14, 13:45 UTC | 23h 10m |
| 2026-05-13 | CBG8908 | BKK → NNG | May 13, 14:25 UTC | May 13, 15:20 UTC | 55m |
| 2026-05-13 | CBG8907 | NNG → BKK | May 13, 11:50 UTC | May 13, 12:50 UTC | 1h 0m |
| 2026-05-12 | CBG8822 | - | May 12, 13:51 UTC | May 12, 17:30 UTC | 3h 40m |
| 2026-05-10 | CBG8908 | BKK → NNG | May 10, 14:04 UTC | May 10, 14:59 UTC | 55m |
| 2026-05-10 | CBG8907 | NNG → BKK | May 10, 11:35 UTC | May 10, 12:44 UTC | 1h 10m |
| 2026-04-28 | CBG8850 | SHE → DYG | Apr 28, 04:10 UTC | Apr 28, 07:50 UTC | 3h 40m |
| 2026-04-27 | CBG8850 | SHE → DYG | Apr 27, 08:35 UTC | Apr 28, 07:50 UTC | 23h 15m |
| 2026-04-26 | CBG8871 | - | Apr 26, 12:15 UTC | Apr 27, 08:35 UTC | 20h 20m |
| 2026-04-26 | CBG8970 | ZUH → HAK | Apr 26, 09:15 UTC | Apr 26, 09:25 UTC | 10m |
| 2026-04-26 | CBG8969 | HAK → ZUH | Apr 26, 02:10 UTC | Apr 26, 02:20 UTC | 10m |
| 2026-04-25 | CBG8820 | TSN → YIH | Apr 25, 08:45 UTC | Apr 25, 08:55 UTC | 10m |
| 2026-04-25 | CBG8819 | ZUH → LYA | Apr 25, 02:35 UTC | Apr 25, 02:45 UTC | 10m |
| 2026-04-23 | CBG8906 | - | Apr 23, 08:50 UTC | Apr 23, 09:01 UTC | 10m |
| 2026-04-23 | CBG8905 | - | Apr 23, 06:20 UTC | Apr 23, 06:45 UTC | 25m |
| 2026-04-20 | CBG7859 | - | Apr 20, 01:35 UTC | Apr 20, 01:50 UTC | 15m |
| 2026-04-18 | CBG8949 | NNG → KOW | Apr 18, 00:00 UTC | Apr 18, 00:15 UTC | 15m |
| 2026-04-17 | CBG8950 | KOW → NNG | Apr 17, 14:45 UTC | Apr 18, 09:40 UTC | 18h 55m |
| 2026-04-17 | CBG8970 | ZUH → HAK | Apr 17, 11:30 UTC | Apr 17, 11:40 UTC | 10m |
| 2026-04-17 | CBG8970 | ZUH → HAK | Apr 17, 07:35 UTC | Apr 17, 07:50 UTC | 15m |
| 2026-04-17 | CBG8969 | HAK → ZUH | Apr 17, 02:15 UTC | Apr 17, 02:35 UTC | 20m |
| 2026-04-16 | CBG8816 | - | Apr 16, 16:40 UTC | Apr 16, 16:55 UTC | 15m |
| 2026-04-16 | CBG8816 | - | Apr 16, 15:20 UTC | Apr 16, 15:40 UTC | 20m |
| 2026-04-16 | CBG8815 | ZUH → HIA | Apr 16, 09:29 UTC | Apr 16, 09:39 UTC | 10m |
| 2026-04-16 | CBG8840 | SQD → HRB | Apr 16, 04:40 UTC | Apr 16, 05:00 UTC | 20m |
| 2026-04-16 | CBG8839 | HRB → SQD | Apr 16, 01:20 UTC | Apr 16, 01:30 UTC | 10m |
| 2026-04-13 | CBG8871 | - | Apr 13, 11:55 UTC | Apr 13, 12:10 UTC | 15m |
| 2026-04-13 | - | - | Apr 13, 08:00 UTC | Apr 13, 08:10 UTC | 10m |
| 2026-04-13 | CBG8969 | HAK → ZUH | Apr 13, 02:20 UTC | Apr 13, 02:40 UTC | 20m |
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-304W page for operator, model, and routing details .