sensors Mode-S transponder
801506
ICAO 24-bit transponder address · allocated to India
Currently assigned to VT-IIX · AIRBUS A-320neo
- Hex
- 801506
- Octal
- 40012406
- Decimal
- 8,393,990
- Country
- IN
- Tail
- VT-IIX
- Type
- A20N
- Flights observed
- 176
- Distinct callsigns
- 20
- Country
- IN
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 801506 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| IGO1038 | IndiGo Airlines | 4 | 2026-06-17 |
| IGO1008 | IndiGo Airlines | 4 | 2026-06-12 |
| IGO1007 | IndiGo Airlines | 4 | 2026-06-12 |
| IGO098 | IndiGo Airlines | 4 | 2026-06-16 |
| IGO362P | - | 3 | 2026-06-10 |
| IGO1068 | IndiGo Airlines | 3 | 2026-06-12 |
| IGO1067 | IndiGo Airlines | 3 | 2026-06-11 |
| IGO1037 | - | 3 | 2026-06-17 |
| IGO1028 | IndiGo Airlines | 3 | 2026-06-09 |
| IGO085 | - | 3 | 2026-06-18 |
| IGO967 | - | 2 | 2026-05-14 |
| IGO955 | - | 2 | 2026-05-22 |
| IGO9205 | - | 2 | 2026-05-13 |
| IGO746Y | - | 2 | 2026-06-23 |
| IGO6966 | IndiGo Airlines | 2 | 2026-05-15 |
| IGO670E | - | 2 | 2026-06-22 |
| IGO6302 | IndiGo Airlines | 2 | 2026-05-10 |
| IGO6102 | IndiGo Airlines | 2 | 2026-05-15 |
| IGO6030 | - | 2 | 2026-05-22 |
| IGO6029 | - | 2 | 2026-06-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-23 | IGO373H | BOM → MAA | Jun 23, 13:50 UTC | Jun 23, 17:30 UTC | 3h 40m |
| 2026-06-23 | IGO394 | - | Jun 23, 10:55 UTC | Jun 23, 12:35 UTC | 1h 40m |
| 2026-06-23 | IGO394 | - | Jun 23, 09:05 UTC | Jun 23, 09:45 UTC | 40m |
| 2026-06-23 | IGO207 | - | Jun 23, 07:40 UTC | Jun 23, 08:15 UTC | 35m |
| 2026-06-23 | IGO207 | - | Jun 23, 04:35 UTC | Jun 23, 06:24 UTC | 1h 50m |
| 2026-06-23 | IGO746Y | - | Jun 23, 01:35 UTC | Jun 23, 03:09 UTC | 1h 35m |
| 2026-06-22 | IGO93VE | - | Jun 22, 16:24 UTC | Jun 22, 17:10 UTC | 45m |
| 2026-06-22 | IGO6029 | - | Jun 22, 06:00 UTC | Jun 22, 07:14 UTC | 1h 15m |
| 2026-06-22 | IGO670E | - | Jun 22, 04:19 UTC | Jun 22, 04:34 UTC | 15m |
| 2026-06-22 | IGO564V | - | Jun 22, 02:00 UTC | Jun 22, 02:10 UTC | 10m |
| 2026-06-21 | IGO060 | - | Jun 21, 12:49 UTC | Jun 21, 23:40 UTC | 10h 50m |
| 2026-06-21 | IGO060 | - | Jun 21, 02:15 UTC | Jun 21, 23:30 UTC | 21h 15m |
| 2026-06-20 | IGO1426 | - | Jun 20, 22:05 UTC | Jun 21, 00:04 UTC | 2h 0m |
| 2026-06-20 | IGO1426 | - | Jun 20, 20:00 UTC | Jun 20, 20:25 UTC | 25m |
| 2026-06-20 | IGO1421 | - | Jun 20, 18:34 UTC | Jun 20, 18:40 UTC | 5m |
| 2026-06-20 | IGO5936 | - | Jun 20, 10:25 UTC | Jun 20, 16:39 UTC | 6h 15m |
| 2026-06-20 | IGO5935 | - | Jun 20, 05:04 UTC | Jun 20, 08:49 UTC | 3h 45m |
| 2026-06-18 | IGO086 | - | Jun 18, 22:55 UTC | Jun 19, 06:35 UTC | 7h 39m |
| 2026-06-18 | IGO085 | - | Jun 18, 21:00 UTC | Jun 18, 21:10 UTC | 10m |
| 2026-06-18 | IGO371F | - | Jun 18, 06:55 UTC | Jun 18, 18:25 UTC | 11h 30m |
| 2026-06-18 | IGO367P | - | Jun 18, 02:45 UTC | Jun 18, 05:45 UTC | 3h 0m |
| 2026-06-17 | IGO1038 | KUL → BLR | Jun 17, 17:30 UTC | Jun 17, 17:45 UTC | 15m |
| 2026-06-17 | IGO1038 | KUL → BLR | Jun 17, 14:15 UTC | Jun 17, 14:35 UTC | 20m |
| 2026-06-17 | IGO1037 | - | Jun 17, 08:50 UTC | Jun 17, 12:40 UTC | 3h 50m |
| 2026-06-17 | IGO142 | - | Jun 17, 05:30 UTC | Jun 17, 05:40 UTC | 10m |
| 2026-06-16 | IGO098 | DMM → LKO | Jun 16, 12:25 UTC | Jun 16, 12:35 UTC | 10m |
| 2026-06-16 | IGO098 | DMM → LKO | Jun 16, 08:20 UTC | Jun 16, 11:25 UTC | 3h 5m |
| 2026-06-15 | IGO088 | DMM → CCJ | Jun 15, 21:14 UTC | Jun 15, 22:20 UTC | 1h 5m |
| 2026-06-15 | IGO097 | LKO → DMM | Jun 15, 16:40 UTC | Jun 15, 17:25 UTC | 45m |
| 2026-06-15 | IGO098 | DMM → LKO | Jun 15, 12:30 UTC | Jun 15, 12:39 UTC | 10m |
| 2026-06-15 | IGO098 | DMM → LKO | Jun 15, 08:20 UTC | Jun 15, 11:19 UTC | 3h 0m |
| 2026-06-15 | IGO087 | CCJ → DMM | Jun 15, 06:20 UTC | Jun 15, 06:30 UTC | 10m |
| 2026-06-13 | IGO086 | - | Jun 13, 23:55 UTC | Jun 14, 06:45 UTC | 6h 50m |
| 2026-06-13 | IGO085 | - | Jun 13, 02:05 UTC | Jun 13, 21:15 UTC | 19h 9m |
| 2026-06-12 | IGO085 | - | Jun 12, 19:35 UTC | Jun 13, 18:45 UTC | 23h 9m |
| 2026-06-12 | IGO1008 | SIN → TRZ | Jun 12, 19:00 UTC | Jun 13, 07:40 UTC | 12h 39m |
| 2026-06-12 | IGO1007 | TRZ → SIN | Jun 12, 16:25 UTC | Jun 12, 17:15 UTC | 50m |
| 2026-06-12 | IGO1068 | BKK → HYD | Jun 12, 05:30 UTC | Jun 12, 11:00 UTC | 5h 30m |
| 2026-06-11 | IGO1067 | HYD → BKK | Jun 11, 15:30 UTC | Jun 12, 03:45 UTC | 12h 16m |
| 2026-06-10 | IGO362P | - | Jun 10, 19:35 UTC | Jun 11, 14:30 UTC | 18h 55m |
| 2026-06-10 | IGO1008 | SIN → TRZ | Jun 10, 19:00 UTC | Jun 11, 14:30 UTC | 19h 30m |
| 2026-06-10 | IGO1007 | TRZ → SIN | Jun 10, 10:35 UTC | Jun 10, 17:15 UTC | 6h 40m |
| 2026-06-09 | IGO1028 | SIN → HYD | Jun 9, 11:35 UTC | Jun 10, 10:50 UTC | 23h 15m |
| 2026-06-09 | IGO1028 | SIN → HYD | Jun 9, 11:10 UTC | Jun 9, 12:05 UTC | 55m |
| 2026-06-08 | IGO1029 | VGA → SIN | Jun 8, 22:10 UTC | Jun 9, 08:35 UTC | 10h 25m |
| 2026-06-08 | IGO1027 | HYD → SIN | Jun 8, 13:00 UTC | Jun 8, 20:50 UTC | 7h 50m |
| 2026-06-08 | IGO34ME | BBI → HYD | Jun 8, 06:35 UTC | Jun 8, 11:55 UTC | 5h 20m |
| 2026-06-07 | IGO6395 | IXC → AMD | Jun 7, 14:00 UTC | Jun 8, 11:55 UTC | 21h 55m |
| 2026-06-07 | IGO313K | DED → JAI | Jun 7, 12:30 UTC | Jun 7, 12:55 UTC | 25m |
| 2026-06-07 | IGO6390 | IDR → DEL | Jun 7, 08:15 UTC | Jun 7, 11:25 UTC | 3h 10m |
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-IIX page for operator, model, and routing details .