sensors Mode-S transponder

78929F

ICAO 24-bit transponder address · allocated to China

Currently assigned to B-LPX · AIRBUS A-321

Hex
78929F
Octal
36111237
Decimal
7,901,855
Country
CN
Tail
B-LPX
Type
A321
Broadcasting now · callsign CRK546 · 25,250 ft
Flights observed
184
Distinct callsigns
20
Country
CN
Last broadcast
1h ago

Current position

78929F is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 78929F 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-03 CRK641 FUK → HKG Jun 3, 10:05 UTCJun 3, 10:20 UTC15m
2026-06-03 CRK641 FUK → HKG Jun 3, 08:55 UTCJun 3, 09:30 UTC35m
2026-06-03 CRK641 FUK → HKG Jun 3, 07:25 UTCJun 3, 07:35 UTC10m
2026-06-03 CRK640 HKG → FUK Jun 3, 05:05 UTCJun 3, 05:15 UTC10m
2026-06-03 CRK640 HKG → FUK Jun 3, 02:30 UTCJun 3, 03:55 UTC1h 25m
2026-06-02 CRK641 FUK → HKG Jun 2, 08:35 UTCJun 2, 10:00 UTC1h 25m
2026-06-02 CRK641 FUK → HKG Jun 2, 07:05 UTCJun 2, 07:15 UTC10m
2026-06-02 CRK640 HKG → FUK Jun 2, 02:35 UTCJun 2, 04:00 UTC1h 25m
2026-06-01 CRK641 FUK → HKG Jun 1, 11:00 UTCJun 1, 11:15 UTC15m
2026-06-01 CRK641 FUK → HKG Jun 1, 09:50 UTCJun 1, 10:25 UTC35m
2026-06-01 CRK641 FUK → HKG Jun 1, 08:20 UTCJun 1, 08:30 UTC10m
2026-06-01 CRK640 HKG → FUK Jun 1, 05:25 UTCJun 1, 05:35 UTC10m
2026-06-01 CRK640 HKG → FUK Jun 1, 02:50 UTCJun 1, 04:15 UTC1h 25m
2026-05-31 CRK641 FUK → HKG May 31, 09:10 UTCMay 31, 10:50 UTC1h 40m
2026-05-30 CRK641 FUK → HKG May 30, 10:20 UTCMay 30, 11:40 UTC1h 20m
2026-05-30 CRK641 FUK → HKG May 30, 08:45 UTCMay 30, 08:55 UTC10m
2026-05-30 CRK640 HKG → FUK May 30, 02:30 UTCMay 30, 03:55 UTC1h 25m
2026-05-29 CRK641 FUK → HKG May 29, 09:00 UTCMay 29, 10:15 UTC1h 15m
2026-05-29 CRK641 FUK → HKG May 29, 07:25 UTCMay 29, 07:35 UTC10m
2026-05-29 CRK640 HKG → FUK May 29, 05:05 UTCMay 29, 05:15 UTC10m
2026-05-29 CRK640 HKG → FUK May 29, 03:20 UTCMay 29, 03:55 UTC35m
2026-05-29 CRK640 HKG → FUK May 29, 02:30 UTCMay 29, 02:50 UTC20m
2026-05-28 CRK629 ICN → HKG May 28, 06:35 UTCMay 28, 09:40 UTC3h 5m
2026-05-28 CRK628 HKG → ICN May 28, 01:40 UTCMay 28, 04:55 UTC3h 15m
2026-05-27 CRK641 FUK → HKG May 27, 08:25 UTCMay 27, 09:50 UTC1h 25m
2026-05-27 CRK641 FUK → HKG May 27, 07:05 UTCMay 27, 07:15 UTC10m
2026-05-27 CRK640 HKG → FUK May 27, 02:29 UTCMay 27, 03:59 UTC1h 30m
2026-05-26 CRK641 FUK → HKG May 26, 08:45 UTCMay 26, 10:20 UTC1h 35m
2026-05-26 CRK640 HKG → FUK May 26, 02:29 UTCMay 26, 03:55 UTC1h 25m
2026-05-25 CRK641 FUK → HKG May 25, 08:50 UTCMay 25, 10:20 UTC1h 30m
2026-05-25 CRK641 FUK → HKG May 25, 07:25 UTCMay 25, 07:35 UTC10m
2026-05-25 CRK640 HKG → FUK May 25, 05:40 UTCMay 25, 05:55 UTC15m
2026-05-25 CRK640 HKG → FUK May 25, 03:55 UTCMay 25, 04:25 UTC30m
2026-05-25 CRK640 HKG → FUK May 25, 03:00 UTCMay 25, 03:20 UTC20m
2026-05-24 CRK641 FUK → HKG May 24, 10:15 UTCMay 24, 10:30 UTC15m
2026-05-24 CRK641 FUK → HKG May 24, 09:00 UTCMay 24, 09:40 UTC40m
2026-05-24 CRK640 HKG → FUK May 24, 05:15 UTCMay 24, 05:25 UTC10m
2026-05-24 CRK640 HKG → FUK May 24, 02:40 UTCMay 24, 04:05 UTC1h 25m
2026-05-23 CRK641 FUK → HKG May 23, 11:30 UTCMay 23, 13:00 UTC1h 30m
2026-05-23 CRK641 FUK → HKG May 23, 10:00 UTCMay 23, 10:10 UTC10m
2026-05-23 CRK640 HKG → FUK May 23, 05:00 UTCMay 23, 05:10 UTC10m
2026-05-23 CRK640 HKG → FUK May 23, 02:25 UTCMay 23, 03:50 UTC1h 24m
2026-05-22 CRK627 ICN → HKG May 22, 18:05 UTCMay 22, 21:20 UTC3h 15m
2026-05-22 CRK626 HKG → ICN May 22, 13:50 UTCMay 22, 16:55 UTC3h 5m
2026-05-22 CRK641 FUK → HKG May 22, 09:45 UTCMay 22, 11:15 UTC1h 30m
2026-05-22 CRK641 FUK → HKG May 22, 08:10 UTCMay 22, 08:20 UTC10m
2026-05-22 CRK640 HKG → FUK May 22, 05:05 UTCMay 22, 05:25 UTC20m
2026-05-22 CRK640 HKG → FUK May 22, 02:30 UTCMay 22, 03:55 UTC1h 25m
2026-05-21 CRK641 FUK → HKG May 21, 09:10 UTCMay 21, 10:30 UTC1h 20m
2026-05-21 CRK640 HKG → FUK May 21, 05:20 UTCMay 21, 05:40 UTC20m

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

Mode-S 78929F frequently asked

What is Mode-S code 78929F?
78929F is an ICAO 24-bit transponder address. Allocated to China. Assigned to B-LPX.
Where is Mode-S 78929F registered?
Mode-S code 78929F is allocated to China (CN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 78929F broadcasting right now?
Yes. Mode-S 78929F is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 78929F, octal 36111237, decimal 7,901,855.
What flights does 78929F operate?
Mode-S 78929F has broadcast 20 distinct callsigns, including CRK641, CRK640, CRK629, CRK628, CRK615.