Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

6010B0

ICAO 24-bit transponder address · allocated to Kyrgyzstan

Currently assigned to EX-32007 · AIRBUS A-320

Hex
6010B0
Octal
30010260
Decimal
6,295,728
Country
KG
Tail
EX-32007
Type
A320
No current signal · last broadcast 1h ago
Flights observed
59
Distinct callsigns
7
Country
KG
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 6010B0.

Country allocation

The ICAO 24-bit address 6010B0 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 7 distinct

Callsign Airline Flights Last seen
AVJ879 - 15 2026-07-23
AVJ880 - 12 2026-07-23
AVJ883 - 10 2026-07-12
AVJ884 - 8 2026-07-13
AVJ959 Avia Traffic Company 7 2026-07-12
AVJ960 - 6 2026-07-08
AVJ4028 - 1 2026-06-04

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-23 AVJ880 - Jul 23, 08:25 UTCJul 23, 10:00 UTC1h 35m
2026-07-23 AVJ879 - Jul 23, 04:25 UTCJul 23, 06:25 UTC2h 0m
2026-07-21 AVJ880 - Jul 21, 09:10 UTCJul 21, 11:00 UTC1h 50m
2026-07-21 AVJ879 - Jul 21, 04:50 UTCJul 21, 07:25 UTC2h 35m
2026-07-18 AVJ880 - Jul 18, 08:25 UTCJul 18, 10:50 UTC2h 25m
2026-07-18 AVJ879 - Jul 18, 06:35 UTCJul 18, 06:45 UTC10m
2026-07-18 AVJ879 - Jul 18, 04:15 UTCJul 18, 05:45 UTC1h 30m
2026-07-16 AVJ880 - Jul 16, 08:35 UTCJul 16, 10:25 UTC1h 50m
2026-07-16 AVJ879 - Jul 16, 04:40 UTCJul 16, 06:40 UTC2h 0m
2026-07-14 AVJ880 - Jul 14, 08:25 UTCJul 14, 09:35 UTC1h 10m
2026-07-14 AVJ879 - Jul 14, 04:00 UTCJul 14, 06:30 UTC2h 30m
2026-07-13 AVJ884 - Jul 13, 08:20 UTCJul 14, 06:30 UTC22h 10m
2026-07-12 AVJ883 - Jul 12, 19:55 UTCJul 13, 06:55 UTC11h 0m
2026-07-12 AVJ959 FRU → DME Jul 12, 16:40 UTCJul 12, 18:01 UTC1h 20m
2026-07-11 AVJ884 - Jul 11, 08:05 UTCJul 11, 09:25 UTC1h 20m
2026-07-11 AVJ883 - Jul 11, 05:01 UTCJul 11, 06:15 UTC1h 15m
2026-07-09 AVJ880 - Jul 9, 08:30 UTCJul 9, 10:55 UTC2h 25m
2026-07-08 AVJ960 - Jul 8, 19:35 UTCJul 9, 06:50 UTC11h 15m
2026-07-08 AVJ959 FRU → DME Jul 8, 16:45 UTCJul 8, 18:00 UTC1h 15m
2026-07-07 AVJ880 - Jul 7, 08:20 UTCJul 7, 08:45 UTC25m
2026-07-07 AVJ879 - Jul 7, 03:55 UTCJul 7, 06:25 UTC2h 30m
2026-07-06 AVJ884 - Jul 6, 08:05 UTCJul 7, 06:25 UTC22h 20m
2026-07-06 AVJ883 FRU → DME Jul 6, 06:15 UTCJul 6, 06:35 UTC20m
2026-07-06 AVJ883 FRU → DME Jul 6, 05:05 UTCJul 6, 05:25 UTC20m
2026-07-02 AVJ880 - Jul 2, 08:20 UTCJul 2, 10:30 UTC2h 10m
2026-07-02 AVJ879 - Jul 2, 06:15 UTCJul 2, 06:35 UTC20m
2026-07-02 AVJ879 - Jul 2, 05:10 UTCJul 2, 05:30 UTC20m
2026-06-30 AVJ884 - Jun 30, 08:45 UTCJun 30, 09:55 UTC1h 10m
2026-06-30 AVJ883 FRU → DME Jun 30, 05:00 UTCJun 30, 07:00 UTC2h 0m
2026-06-29 AVJ883 FRU → DME Jun 29, 08:04 UTCJun 30, 07:00 UTC22h 55m
2026-06-29 AVJ884 - Jun 29, 07:59 UTCJun 30, 06:00 UTC22h 1m
2026-06-29 AVJ883 FRU → DME Jun 29, 04:50 UTCJun 29, 06:05 UTC1h 15m
2026-06-27 AVJ960 - Jun 27, 20:04 UTCJun 27, 21:34 UTC1h 30m
2026-06-27 AVJ959 FRU → DME Jun 27, 16:55 UTCJun 27, 18:29 UTC1h 35m
2026-06-25 AVJ880 - Jun 25, 08:30 UTCJun 25, 10:45 UTC2h 15m
2026-06-25 AVJ879 - Jun 25, 04:04 UTCJun 25, 06:35 UTC2h 30m
2026-06-23 AVJ880 - Jun 23, 08:30 UTCJun 23, 10:59 UTC2h 30m
2026-06-23 AVJ879 FRU → LED Jun 23, 05:04 UTCJun 23, 06:19 UTC1h 15m
2026-06-22 AVJ884 - Jun 22, 08:04 UTCJun 23, 06:19 UTC22h 15m
2026-06-22 AVJ883 FRU → DME Jun 22, 04:54 UTCJun 22, 06:19 UTC1h 25m
2026-06-19 AVJ960 - Jun 19, 19:45 UTCJun 19, 20:55 UTC1h 10m
2026-06-19 AVJ959 FRU → DME Jun 19, 16:44 UTCJun 19, 17:44 UTC1h 0m
2026-06-18 AVJ960 - Jun 18, 20:05 UTCJun 19, 17:44 UTC21h 39m
2026-06-18 AVJ959 FRU → DME Jun 18, 08:25 UTCJun 18, 18:10 UTC9h 45m
2026-06-18 AVJ879 FRU → LED Jun 18, 03:50 UTCJun 18, 06:15 UTC2h 25m
2026-06-16 AVJ880 LED → FRU Jun 16, 08:30 UTCJun 16, 09:50 UTC1h 20m
2026-06-16 AVJ879 FRU → LED Jun 16, 05:25 UTCJun 16, 06:30 UTC1h 5m
2026-06-15 AVJ884 DME → FRU Jun 15, 08:15 UTCJun 16, 06:30 UTC22h 15m
2026-06-14 AVJ960 - Jun 14, 20:25 UTCJun 15, 06:49 UTC10h 24m
2026-06-14 AVJ959 FRU → DME Jun 14, 03:25 UTCJun 14, 18:55 UTC15h 30m

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

Mode-S 6010B0 frequently asked

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