Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

801611

ICAO 24-bit transponder address · allocated to India

Currently assigned to VT-IKY · AIRBUS A-321neo

Hex
801611
Octal
40013021
Decimal
8,394,257
Country
IN
Tail
VT-IKY
Type
A21N
No current signal · last broadcast 1d ago
Flights observed
152
Distinct callsigns
15
Country
IN
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 801611.

Country allocation

The ICAO 24-bit address 801611 falls within the block assigned to India (IN) by ICAO Annex 10, Volume III. Every aircraft registered in India 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 15 distinct

Callsign Airline Flights Last seen
IGO9631 - 32 2026-07-12
IGO9268 - 26 2026-07-12
IGO9269 - 21 2026-07-12
IGO9302 - 17 2026-07-11
IGO9301 - 17 2026-07-11
IGO9265 - 12 2026-07-02
IGO9632 - 9 2026-07-01
IGO9267 - 9 2026-07-02
IGO9271 IndiGo Airlines 2 2026-05-19
IGO9087 - 2 2026-05-29
IGO9262 IndiGo Airlines 1 2026-05-29
IGO9257 IndiGo Airlines 1 2026-05-16
IGO9159 - 1 2026-05-19
IGO9086 - 1 2026-05-28
IG09269 - 1 2026-06-07

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-12 IGO9631 CCU → CCU Jul 12, 19:05 UTCJul 13, 01:40 UTC6h 35m
2026-07-12 IGO9269 - Jul 12, 14:01 UTCJul 12, 15:30 UTC1h 30m
2026-07-12 IGO9268 CCU → RGN Jul 12, 10:55 UTCJul 12, 12:35 UTC1h 40m
2026-07-11 IGO9302 - Jul 11, 11:20 UTCJul 11, 11:55 UTC35m
2026-07-11 IGO9301 CCU → DAC Jul 11, 08:50 UTCJul 11, 09:30 UTC40m
2026-07-10 IGO9631 CCU → CCU Jul 10, 18:25 UTCJul 11, 00:45 UTC6h 20m
2026-07-09 IGO9269 - Jul 9, 09:15 UTCJul 9, 10:50 UTC1h 35m
2026-07-09 IGO9268 CCU → RGN Jul 9, 05:50 UTCJul 9, 07:35 UTC1h 45m
2026-07-08 IGO9631 CCU → CCU Jul 8, 19:00 UTCJul 9, 01:10 UTC6h 10m
2026-07-05 IGO9631 CCU → CCU Jul 5, 19:10 UTCJul 6, 01:10 UTC6h 0m
2026-07-05 IGO9269 - Jul 5, 13:20 UTCJul 5, 15:00 UTC1h 40m
2026-07-05 IGO9268 CCU → RGN Jul 5, 10:40 UTCJul 5, 12:20 UTC1h 40m
2026-07-04 IGO9269 - Jul 4, 16:15 UTCJul 4, 17:35 UTC1h 20m
2026-07-04 IGO9268 CCU → RGN Jul 4, 12:45 UTCJul 4, 14:45 UTC2h 0m
2026-07-03 IGO9631 CCU → CCU Jul 3, 19:05 UTCJul 4, 01:30 UTC6h 25m
2026-07-02 IGO9267 - Jul 2, 17:25 UTCJul 2, 18:50 UTC1h 25m
2026-07-02 IGO9265 CCU → RGN Jul 2, 14:30 UTCJul 2, 16:10 UTC1h 40m
2026-07-02 IGO9269 - Jul 2, 08:40 UTCJul 2, 10:10 UTC1h 30m
2026-07-02 IGO9268 CCU → RGN Jul 2, 05:45 UTCJul 2, 07:40 UTC1h 55m
2026-07-01 IGO9632 - Jul 1, 18:55 UTCJul 2, 01:30 UTC6h 35m
2026-07-01 IGO9302 DAC → CCU Jul 1, 11:10 UTCJul 1, 11:50 UTC40m
2026-07-01 IGO9301 CCU → DAC Jul 1, 08:50 UTCJul 1, 09:25 UTC35m
2026-06-30 IGO9631 CCU → CCU Jun 30, 19:45 UTCJul 1, 02:05 UTC6h 20m
2026-06-28 IGO9631 CCU → CCU Jun 28, 18:44 UTCJun 29, 01:00 UTC6h 15m
2026-06-28 IGO9269 - Jun 28, 14:04 UTCJun 28, 15:34 UTC1h 30m
2026-06-28 IGO9268 CCU → RGN Jun 28, 11:14 UTCJun 28, 12:39 UTC1h 25m
2026-06-28 IGO9302 DAC → CCU Jun 28, 01:50 UTCJun 28, 02:20 UTC30m
2026-06-27 IGO9301 CCU → DAC Jun 27, 23:45 UTCJun 28, 00:15 UTC30m
2026-06-27 IGO9267 RGN → CCU Jun 27, 17:44 UTCJun 27, 19:15 UTC1h 30m
2026-06-27 IGO9265 - Jun 27, 14:45 UTCJun 27, 16:14 UTC1h 30m
2026-06-26 IGO9631 CCU → CCU Jun 26, 19:00 UTCJun 27, 01:19 UTC6h 20m
2026-06-25 IGO9269 - Jun 25, 07:54 UTCJun 25, 09:14 UTC1h 20m
2026-06-25 IGO9268 - Jun 25, 06:09 UTCJun 25, 06:20 UTC10m
2026-06-25 IGO9268 - Jun 25, 04:49 UTCJun 25, 05:29 UTC40m
2026-06-24 IGO9302 DAC → CCU Jun 24, 13:30 UTCJun 24, 14:04 UTC35m
2026-06-24 IGO9301 CCU → DAC Jun 24, 11:05 UTCJun 24, 11:39 UTC35m
2026-06-23 IGO9631 CCU → CCU Jun 23, 19:00 UTCJun 24, 01:24 UTC6h 25m
2026-06-22 IGO9269 RGN → CCU Jun 22, 08:10 UTCJun 22, 09:40 UTC1h 30m
2026-06-22 IGO9268 MAA → BOM Jun 22, 06:29 UTCJun 22, 06:39 UTC10m
2026-06-22 IGO9268 MAA → BOM Jun 22, 05:10 UTCJun 22, 05:49 UTC40m
2026-06-21 IGO9631 BOM → DXB Jun 21, 18:54 UTCJun 22, 01:05 UTC6h 10m
2026-06-21 IGO9269 RGN → CCU Jun 21, 13:20 UTCJun 21, 14:40 UTC1h 20m
2026-06-21 IGO9268 MAA → BOM Jun 21, 10:40 UTCJun 21, 12:04 UTC1h 25m
2026-06-20 IGO9269 - Jun 20, 13:55 UTCJun 20, 14:39 UTC45m
2026-06-20 IGO9268 MAA → BOM Jun 20, 11:40 UTCJun 20, 11:49 UTC10m
2026-06-20 IGO9268 MAA → BOM Jun 20, 10:25 UTCJun 20, 11:05 UTC40m
2026-06-20 IGO9302 DAC → CCU Jun 20, 06:54 UTCJun 20, 07:24 UTC30m
2026-06-20 IGO9301 CCU → DAC Jun 20, 04:49 UTCJun 20, 05:24 UTC35m
2026-06-19 IGO9631 BOM → DXB Jun 19, 19:04 UTCJun 20, 01:29 UTC6h 25m
2026-06-18 IGO9269 - Jun 18, 05:30 UTCJun 18, 10:15 UTC4h 45m

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

Mode-S 801611 frequently asked

What is Mode-S code 801611?
801611 is an ICAO 24-bit transponder address. Allocated to India. Assigned to VT-IKY.
Where is Mode-S 801611 registered?
Mode-S code 801611 is allocated to India (IN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 801611 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 801611, octal 40013021, decimal 8,394,257.
What flights does 801611 operate?
Mode-S 801611 has broadcast 15 distinct callsigns, including IGO9631, IGO9268, IGO9269, IGO9302, IGO9301.