Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

60111C

ICAO 24-bit transponder address · allocated to Kyrgyzstan

Currently assigned to EX-32014 · AIRBUS A-320

Hex
60111C
Octal
30010434
Decimal
6,295,836
Country
KG
Tail
EX-32014
Type
A320
No current signal · last broadcast 2d ago
Flights observed
112
Distinct callsigns
8
Country
KG
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 60111C.

Country allocation

The ICAO 24-bit address 60111C falls within the block assigned to Kyrgyzstan (KG) by ICAO Annex 10, Volume III. Every aircraft registered in Kyrgyzstan 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 8 distinct

Callsign Airline Flights Last seen
AVJ960 - 30 2026-07-08
AVJ880 - 25 2026-07-11
AVJ879 - 18 2026-07-11
AVJ884 - 16 2026-06-16
AVJ959 Avia Traffic Company 12 2026-07-01
AVJ883 Avia Traffic Company 7 2026-06-26
AVJ761 - 3 2026-07-12
AVJ762 Avia Traffic Company 1 2026-07-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-12 AVJ761 - Jul 12, 03:35 UTCJul 12, 07:50 UTC4h 15m
2026-07-11 AVJ880 - Jul 11, 08:20 UTCJul 11, 08:40 UTC20m
2026-07-11 AVJ879 - Jul 11, 06:05 UTCJul 11, 06:15 UTC10m
2026-07-08 AVJ960 - Jul 8, 11:35 UTCJul 8, 11:45 UTC10m
2026-07-05 AVJ762 OVB → FRU Jul 5, 03:35 UTCJul 5, 07:50 UTC4h 15m
2026-07-04 AVJ880 - Jul 4, 08:30 UTCJul 4, 08:55 UTC25m
2026-07-01 AVJ959 FRU → DME Jul 1, 16:40 UTCJul 2, 08:55 UTC16h 15m
2026-06-30 AVJ959 FRU → DME Jun 30, 22:00 UTCJul 1, 16:55 UTC18h 55m
2026-06-30 AVJ880 - Jun 30, 09:00 UTCJun 30, 09:10 UTC10m
2026-06-28 AVJ761 - Jun 28, 03:29 UTCJun 28, 20:39 UTC17h 10m
2026-06-26 AVJ883 FRU → DME Jun 26, 04:55 UTCJun 26, 20:50 UTC15h 55m
2026-06-22 AVJ960 - Jun 22, 20:34 UTCJun 22, 20:44 UTC10m
2026-06-21 AVJ761 - Jun 21, 03:25 UTCJun 21, 20:05 UTC16h 40m
2026-06-20 AVJ880 - Jun 20, 08:34 UTCJun 20, 08:49 UTC15m
2026-06-19 AVJ883 FRU → DME Jun 19, 07:19 UTCJun 19, 13:20 UTC6h 0m
2026-06-18 AVJ883 FRU → DME Jun 18, 11:20 UTCJun 18, 11:40 UTC20m
2026-06-16 AVJ884 - Jun 16, 10:15 UTCJun 16, 21:00 UTC10h 46m
2026-06-16 AVJ883 FRU → DME Jun 16, 07:05 UTCJun 16, 07:15 UTC10m
2026-06-15 AVJ960 - Jun 15, 19:25 UTCJun 15, 19:45 UTC20m
2026-06-13 AVJ880 LED → FRU Jun 13, 08:30 UTCJun 13, 21:10 UTC12h 40m
2026-06-12 AVJ884 DME → FRU Jun 12, 08:30 UTCJun 12, 17:20 UTC8h 50m
2026-06-11 AVJ959 FRU → DME Jun 11, 17:10 UTCJun 11, 21:35 UTC4h 25m
2026-06-11 AVJ880 LED → FRU Jun 11, 08:30 UTCJun 11, 08:50 UTC20m
2026-06-10 AVJ960 DME → FRU Jun 10, 20:35 UTCJun 10, 21:35 UTC1h 0m
2026-06-10 AVJ884 DME → FRU Jun 10, 09:15 UTCJun 10, 09:45 UTC30m
2026-06-09 AVJ959 FRU → DME Jun 9, 20:45 UTCJun 9, 21:00 UTC15m
2026-06-09 AVJ883 FRU → DME Jun 9, 05:05 UTCJun 9, 05:15 UTC10m
2026-06-07 AVJ884 DME → FRU Jun 7, 08:50 UTCJun 7, 20:30 UTC11h 40m
2026-06-05 AVJ959 FRU → DME Jun 5, 05:05 UTCJun 5, 21:30 UTC16h 25m
2026-06-04 AVJ959 FRU → DME Jun 4, 21:00 UTCJun 5, 17:20 UTC20h 20m
2026-06-04 AVJ883 FRU → DME Jun 4, 10:00 UTCJun 5, 05:20 UTC19h 20m
2026-06-04 AVJ879 FRU → LED Jun 4, 04:50 UTCJun 4, 21:00 UTC16h 10m
2026-06-03 AVJ884 DME → FRU Jun 3, 08:35 UTCJun 4, 05:10 UTC20h 35m
2026-06-02 AVJ884 DME → FRU Jun 2, 17:20 UTCJun 3, 09:00 UTC15h 40m
2026-06-02 AVJ884 DME → FRU Jun 2, 10:35 UTCJun 3, 09:00 UTC22h 25m
2026-06-02 AVJ880 LED → FRU Jun 2, 09:10 UTCJun 2, 09:25 UTC15m
2026-06-01 AVJ960 DME → FRU Jun 1, 08:55 UTCJun 1, 20:40 UTC11h 45m
2026-05-31 AVJ960 DME → FRU May 31, 21:05 UTCJun 1, 20:40 UTC23h 35m
2026-05-31 AVJ960 DME → FRU May 31, 20:55 UTCJun 1, 09:10 UTC12h 15m
2026-05-31 AVJ960 DME → FRU May 31, 08:40 UTCMay 31, 21:10 UTC12h 30m
2026-05-30 AVJ880 LED → FRU May 30, 10:05 UTCMay 31, 08:45 UTC22h 40m
2026-05-30 AVJ880 LED → FRU May 30, 08:30 UTCMay 30, 08:45 UTC15m
2026-05-29 AVJ960 DME → FRU May 29, 20:35 UTCMay 30, 03:45 UTC7h 10m
2026-05-29 AVJ960 DME → FRU May 29, 09:00 UTCMay 30, 03:45 UTC18h 45m
2026-05-28 AVJ880 LED → FRU May 28, 11:15 UTCMay 29, 09:00 UTC21h 45m
2026-05-28 AVJ880 LED → FRU May 28, 10:10 UTCMay 29, 09:00 UTC22h 50m
2026-05-27 AVJ879 FRU → LED May 27, 20:30 UTCMay 28, 11:20 UTC14h 50m
2026-05-27 AVJ879 FRU → LED May 27, 08:40 UTCMay 28, 05:05 UTC20h 25m
2026-05-27 AVJ884 DME → FRU May 27, 07:40 UTCMay 27, 07:55 UTC15m
2026-05-26 AVJ880 LED → FRU May 26, 09:59 UTCMay 26, 21:20 UTC11h 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 EX-32014 page for operator, model, and routing details .

Mode-S 60111C frequently asked

What is Mode-S code 60111C?
60111C is an ICAO 24-bit transponder address. Allocated to Kyrgyzstan. Assigned to EX-32014.
Where is Mode-S 60111C registered?
Mode-S code 60111C is allocated to Kyrgyzstan (KG). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 60111C broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 60111C, octal 30010434, decimal 6,295,836.
What flights does 60111C operate?
Mode-S 60111C has broadcast 8 distinct callsigns, including AVJ960, AVJ880, AVJ879, AVJ884, AVJ959.