sensors Mode-S transponder

782253

ICAO 24-bit transponder address · allocated to China

Currently assigned to B-32M0 · AIRBUS A-321neo

Hex
782253
Octal
36021123
Decimal
7,873,107
Country
CN
Tail
B-32M0
Type
A21N
No current signal · last broadcast 18h ago
Flights observed
48
Distinct callsigns
4
Country
CN
Last broadcast
18h ago

Last known position

Most recent position reported by Mode-S 782253.

Country allocation

The ICAO 24-bit address 782253 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 4 distinct

Callsign Airline Flights Last seen
LKE9683 - 20 2026-07-01
LKE9684 - 15 2026-07-01
LKE9691 - 9 2026-07-04
LKE9692 - 4 2026-07-03

Recent flights last 48

DateFlightRouteTakeoffLandingDuration
2026-07-04 LKE9691 - Jul 4, 02:50 UTCJul 4, 06:05 UTC3h 15m
2026-07-03 LKE9692 - Jul 3, 00:25 UTCJul 3, 03:50 UTC3h 25m
2026-07-01 LKE9684 - Jul 1, 09:40 UTCJul 1, 09:50 UTC10m
2026-07-01 LKE9683 - Jul 1, 05:35 UTCJul 1, 05:50 UTC15m
2026-06-30 LKE9684 - Jun 30, 07:20 UTCJun 30, 07:35 UTC15m
2026-06-30 LKE9683 - Jun 30, 03:00 UTCJun 30, 03:20 UTC20m
2026-06-29 LKE9684 - Jun 29, 07:20 UTCJun 29, 07:40 UTC20m
2026-06-29 LKE9683 - Jun 29, 03:05 UTCJun 29, 03:20 UTC15m
2026-06-28 LKE9684 - Jun 28, 07:20 UTCJun 28, 07:29 UTC10m
2026-06-28 LKE9683 - Jun 28, 03:00 UTCJun 28, 03:14 UTC15m
2026-06-27 LKE9684 SJW → TFU Jun 27, 07:19 UTCJun 27, 07:34 UTC15m
2026-06-27 LKE9683 - Jun 27, 02:59 UTCJun 27, 03:15 UTC15m
2026-06-26 LKE9684 SJW → TFU Jun 26, 07:30 UTCJun 26, 07:39 UTC10m
2026-06-26 LKE9683 TFU → SJW Jun 26, 03:05 UTCJun 26, 03:20 UTC15m
2026-06-25 LKE9684 SJW → TFU Jun 25, 07:25 UTCJun 25, 07:34 UTC10m
2026-06-25 LKE9683 TFU → SJW Jun 25, 03:10 UTCJun 25, 03:24 UTC15m
2026-06-23 LKE9683 TFU → SJW Jun 23, 03:09 UTCJun 23, 07:49 UTC4h 40m
2026-06-21 LKE9683 TFU → SJW Jun 21, 02:55 UTCJun 21, 03:10 UTC15m
2026-06-20 LKE9692 SYX → TFU Jun 20, 05:34 UTCJun 21, 03:10 UTC21h 35m
2026-06-20 LKE9691 TFU → SYX Jun 20, 02:14 UTCJun 20, 02:49 UTC35m
2026-06-16 LKE9691 TFU → SYX Jun 16, 03:20 UTCJun 16, 06:40 UTC3h 20m
2026-06-13 LKE9684 SJW → TFU Jun 13, 07:45 UTCJun 13, 07:55 UTC10m
2026-06-13 LKE9683 TFU → SJW Jun 13, 03:20 UTCJun 13, 03:30 UTC10m
2026-06-12 LKE9684 SJW → TFU Jun 12, 07:20 UTCJun 12, 07:30 UTC10m
2026-06-12 LKE9683 TFU → SJW Jun 12, 03:10 UTCJun 12, 03:25 UTC15m
2026-06-11 LKE9692 SYX → TFU Jun 11, 07:35 UTCJun 12, 03:25 UTC19h 51m
2026-06-11 LKE9691 TFU → SYX Jun 11, 04:55 UTCJun 11, 05:20 UTC25m
2026-06-10 LKE9691 TFU → SYX Jun 10, 06:50 UTCJun 11, 05:20 UTC22h 30m
2026-06-09 LKE9691 TFU → SYX Jun 9, 13:15 UTCJun 10, 07:00 UTC17h 45m
2026-06-09 LKE9691 TFU → SYX Jun 9, 10:50 UTCJun 10, 07:00 UTC20h 10m
2026-06-06 LKE9692 SYX → TFU Jun 6, 04:40 UTCJun 6, 05:10 UTC30m
2026-06-06 LKE9691 TFU → SYX Jun 6, 02:20 UTCJun 6, 02:50 UTC30m
2026-06-02 LKE9691 TFU → SYX Jun 2, 02:20 UTCJun 2, 05:25 UTC3h 5m
2026-05-29 LKE9684 SJW → TFU May 29, 07:15 UTCMay 29, 07:25 UTC10m
2026-05-29 LKE9683 TFU → SJW May 29, 03:05 UTCMay 29, 03:20 UTC15m
2026-05-28 LKE9683 TFU → SJW May 28, 03:10 UTCMay 28, 03:25 UTC15m
2026-05-27 LKE9684 SJW → TFU May 27, 07:30 UTCMay 27, 07:40 UTC10m
2026-05-27 LKE9683 TFU → SJW May 27, 02:54 UTCMay 27, 03:09 UTC15m
2026-05-26 LKE9684 SJW → TFU May 26, 07:10 UTCMay 26, 07:19 UTC10m
2026-05-26 LKE9683 TFU → SJW May 26, 03:05 UTCMay 26, 03:19 UTC15m
2026-05-22 LKE9683 TFU → SJW May 22, 03:00 UTCMay 22, 03:20 UTC20m
2026-05-20 LKE9684 SJW → TFU May 20, 07:10 UTCMay 20, 07:20 UTC10m
2026-05-20 LKE9683 TFU → SJW May 20, 03:05 UTCMay 20, 03:20 UTC15m
2026-05-18 LKE9684 SJW → TFU May 18, 07:35 UTCMay 18, 07:45 UTC10m
2026-05-18 LKE9683 TFU → SJW May 18, 03:01 UTCMay 18, 03:20 UTC20m
2026-05-09 LKE9684 SJW → TFU May 9, 07:15 UTCMay 9, 07:25 UTC10m
2026-05-09 LKE9683 TFU → SJW May 9, 03:00 UTCMay 9, 03:20 UTC20m
2026-05-06 LKE9683 TFU → SJW May 6, 03:20 UTCMay 6, 03:35 UTC15m

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

Mode-S 782253 frequently asked

What is Mode-S code 782253?
782253 is an ICAO 24-bit transponder address. Allocated to China. Assigned to B-32M0.
Where is Mode-S 782253 registered?
Mode-S code 782253 is allocated to China (CN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 782253 broadcasting right now?
No active broadcast right now. Last signal was 18h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 782253, octal 36021123, decimal 7,873,107.
What flights does 782253 operate?
Mode-S 782253 has broadcast 4 distinct callsigns, including LKE9683, LKE9684, LKE9691, LKE9692.