sensors Mode-S transponder

782168

ICAO 24-bit transponder address · allocated to China

Currently assigned to B-32J1 · AIRBUS A-320neo

Hex
782168
Octal
36020550
Decimal
7,872,872
Country
CN
Tail
B-32J1
Type
A20N
No current signal · last broadcast 16h ago
Flights observed
85
Distinct callsigns
11
Country
CN
Last broadcast
16h ago

Last known position

Most recent position reported by Mode-S 782168.

Country allocation

The ICAO 24-bit address 782168 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 11 distinct

Callsign Airline Flights Last seen
CBG8822 - 26 2026-07-15
CBG8907 - 25 2026-07-17
CBG8908 - 14 2026-07-17
CBG8978 - 8 2026-07-13
CBG8977 - 4 2026-07-12
CBG8821 - 3 2026-07-15
CBG8969 - 1 2026-06-19
CBG8950 Guangxi Beibu Gulf Airlines 1 2026-05-05
CBG8936 Guangxi Beibu Gulf Airlines 1 2026-04-17
CBG8814 Guangxi Beibu Gulf Airlines 1 2026-04-19
CBG3211 - 1 2026-06-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 CBG8908 - Jul 17, 14:15 UTCJul 17, 15:49 UTC1h 35m
2026-07-17 CBG8907 - Jul 17, 12:40 UTCJul 17, 13:05 UTC25m
2026-07-17 CBG8907 - Jul 17, 11:20 UTCJul 17, 11:30 UTC10m
2026-07-15 CBG8822 - Jul 15, 14:55 UTCJul 15, 15:25 UTC30m
2026-07-15 CBG8821 - Jul 15, 00:25 UTCJul 15, 12:40 UTC12h 15m
2026-07-14 CBG8822 - Jul 14, 12:15 UTCJul 14, 15:15 UTC3h 0m
2026-07-13 CBG8822 - Jul 13, 12:35 UTCJul 13, 15:45 UTC3h 10m
2026-07-13 CBG8978 - Jul 13, 00:10 UTCJul 13, 09:45 UTC9h 35m
2026-07-12 CBG8822 - Jul 12, 14:40 UTCJul 12, 15:25 UTC45m
2026-07-12 CBG8977 - Jul 12, 00:15 UTCJul 12, 09:30 UTC9h 15m
2026-07-10 CBG8908 - Jul 10, 14:05 UTCJul 10, 15:40 UTC1h 35m
2026-07-10 CBG8907 - Jul 10, 11:05 UTCJul 10, 12:50 UTC1h 45m
2026-07-09 CBG8822 - Jul 9, 15:55 UTCJul 9, 16:40 UTC45m
2026-07-08 CBG8822 - Jul 8, 14:55 UTCJul 9, 13:35 UTC22h 40m
2026-07-08 CBG8821 - Jul 8, 09:10 UTCJul 8, 12:35 UTC3h 25m
2026-07-07 CBG8822 - Jul 7, 14:45 UTCJul 8, 12:35 UTC21h 50m
2026-07-06 CBG8978 - Jul 6, 01:55 UTCJul 6, 10:30 UTC8h 35m
2026-07-05 CBG8822 - Jul 5, 00:15 UTCJul 5, 16:10 UTC15h 55m
2026-07-04 CBG8822 - Jul 4, 15:05 UTCJul 5, 12:55 UTC21h 50m
2026-07-04 CBG8822 - Jul 4, 12:10 UTCJul 5, 00:25 UTC12h 15m
2026-07-03 CBG8977 - Jul 3, 00:15 UTCJul 3, 11:20 UTC11h 5m
2026-07-01 CBG8822 - Jul 1, 12:15 UTCJul 1, 15:50 UTC3h 35m
2026-07-01 CBG8978 - Jul 1, 00:15 UTCJul 1, 09:30 UTC9h 15m
2026-06-29 CBG8908 - Jun 29, 14:09 UTCJun 29, 15:49 UTC1h 40m
2026-06-29 CBG8907 - Jun 29, 11:04 UTCJun 29, 12:49 UTC1h 45m
2026-06-28 CBG8908 - Jun 28, 14:09 UTCJun 28, 15:44 UTC1h 35m
2026-06-28 CBG8907 - Jun 28, 11:04 UTCJun 28, 13:00 UTC1h 55m
2026-06-27 CBG8907 - Jun 27, 15:30 UTCJun 28, 13:00 UTC21h 30m
2026-06-27 CBG8907 - Jun 27, 12:04 UTCJun 28, 11:35 UTC23h 30m
2026-06-26 CBG8908 - Jun 26, 14:15 UTCJun 26, 15:49 UTC1h 35m
2026-06-26 CBG8907 - Jun 26, 11:00 UTCJun 26, 12:44 UTC1h 45m
2026-06-24 CBG8978 KOW → NNG Jun 24, 00:25 UTCJun 24, 18:44 UTC18h 20m
2026-06-22 CBG8822 - Jun 22, 12:15 UTCJun 22, 15:54 UTC3h 40m
2026-06-22 CBG8978 KOW → NNG Jun 22, 00:20 UTCJun 22, 09:34 UTC9h 15m
2026-06-21 CBG8822 - Jun 21, 12:19 UTCJun 21, 15:44 UTC3h 25m
2026-06-21 CBG8978 KOW → NNG Jun 21, 00:14 UTCJun 21, 09:29 UTC9h 15m
2026-06-19 CBG8969 - Jun 19, 02:39 UTCJun 19, 02:50 UTC10m
2026-06-18 CBG3211 - Jun 18, 08:25 UTCJun 18, 08:55 UTC30m
2026-06-12 CBG8908 BKK → NNG Jun 12, 14:05 UTCJun 12, 15:45 UTC1h 40m
2026-06-12 CBG8907 - Jun 12, 10:50 UTCJun 12, 12:25 UTC1h 35m
2026-06-10 CBG8908 BKK → NNG Jun 10, 14:05 UTCJun 10, 15:40 UTC1h 35m
2026-06-10 CBG8907 NNG → BKK Jun 10, 11:00 UTCJun 10, 12:50 UTC1h 50m
2026-06-09 CBG8907 NNG → BKK Jun 9, 15:00 UTCJun 10, 12:50 UTC21h 50m
2026-06-09 CBG8907 NNG → BKK Jun 9, 12:05 UTCJun 10, 11:30 UTC23h 25m
2026-06-08 CBG8908 BKK → NNG Jun 8, 14:35 UTCJun 9, 12:10 UTC21h 35m
2026-06-08 CBG8907 NNG → BKK Jun 8, 11:30 UTCJun 8, 13:20 UTC1h 50m
2026-06-08 CBG8977 NNG → KOW Jun 8, 00:10 UTCJun 8, 00:25 UTC15m
2026-06-05 CBG8822 - Jun 5, 14:15 UTCJun 5, 17:45 UTC3h 30m
2026-06-05 CBG8978 KOW → NNG Jun 5, 10:55 UTCJun 5, 11:05 UTC10m
2026-06-01 CBG8908 BKK → NNG Jun 1, 14:10 UTCJun 1, 15:45 UTC1h 35m

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-32J1 page for operator, model, and routing details .

Mode-S 782168 frequently asked

What is Mode-S code 782168?
782168 is an ICAO 24-bit transponder address. Allocated to China. Assigned to B-32J1.
Where is Mode-S 782168 registered?
Mode-S code 782168 is allocated to China (CN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 782168 broadcasting right now?
No active broadcast right now. Last signal was 16h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 782168, octal 36020550, decimal 7,872,872.
What flights does 782168 operate?
Mode-S 782168 has broadcast 11 distinct callsigns, including CBG8822, CBG8907, CBG8908, CBG8978, CBG8977.