sensors Mode-S transponder
06A15A
ICAO 24-bit transponder address · allocated to Qatar
Currently assigned to A7-AJG · AIRBUS A-321neo
- Hex
- 06A15A
- Octal
- 01520532
- Decimal
- 434,522
- Country
- QA
- Tail
- A7-AJG
- Type
- A21N
- Flights observed
- 172
- Distinct callsigns
- 17
- Country
- QA
- Last broadcast
- Jul 5, 20:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 06A15A falls within the block assigned to Qatar (QA) by ICAO Annex 10, Volume III. Every aircraft registered in Qatar 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| IGO1316 | - | 32 | 2026-07-03 |
| IGO32Y | - | 22 | 2026-07-04 |
| IGO1322 | IndiGo Airlines | 20 | 2026-06-22 |
| IGO25H | - | 18 | 2026-07-03 |
| IGO19M | - | 18 | 2026-06-28 |
| IGO1321 | IndiGo Airlines | 10 | 2026-06-22 |
| IGO1323 | IndiGo Airlines | 9 | 2026-06-14 |
| IGO51C | IndiGo Airlines | 8 | 2026-06-14 |
| IGO46V | - | 8 | 2026-06-21 |
| IGO41U | IndiGo Airlines | 7 | 2026-06-21 |
| IGO1313 | IndiGo Airlines | 6 | 2026-06-27 |
| IGO28F | - | 3 | 2026-06-07 |
| IGO15H | - | 3 | 2026-06-07 |
| IGO1326 | IndiGo Airlines | 3 | 2026-06-08 |
| IGO53M | IndiGo Airlines | 2 | 2026-06-24 |
| IGO1315 | IndiGo Airlines | 2 | 2026-05-02 |
| QTR3169 | - | 1 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-05 | QTR3169 | DEL → DIA | Jul 5, 17:15 UTC | Jul 5, 20:55 UTC | 3h 40m |
| 2026-07-04 | IGO32Y | - | Jul 4, 09:15 UTC | Jul 4, 10:05 UTC | 50m |
| 2026-07-04 | IGO32Y | - | Jul 4, 06:05 UTC | Jul 4, 07:00 UTC | 55m |
| 2026-07-03 | IGO1316 | - | Jul 3, 17:40 UTC | Jul 4, 03:00 UTC | 9h 20m |
| 2026-07-03 | IGO25H | - | Jul 3, 11:25 UTC | Jul 3, 15:00 UTC | 3h 35m |
| 2026-07-03 | IGO32Y | DOH → DEL | Jul 3, 06:10 UTC | Jul 3, 09:45 UTC | 3h 35m |
| 2026-07-02 | IGO1316 | - | Jul 2, 17:45 UTC | Jul 3, 03:00 UTC | 9h 15m |
| 2026-07-02 | IGO25H | - | Jul 2, 12:00 UTC | Jul 2, 15:35 UTC | 3h 35m |
| 2026-07-02 | IGO32Y | - | Jul 2, 06:15 UTC | Jul 2, 10:00 UTC | 3h 45m |
| 2026-07-01 | IGO1316 | - | Jul 1, 18:00 UTC | Jul 2, 03:15 UTC | 9h 15m |
| 2026-07-01 | IGO25H | DEL → DOH | Jul 1, 11:20 UTC | Jul 1, 15:05 UTC | 3h 45m |
| 2026-07-01 | IGO32Y | - | Jul 1, 06:00 UTC | Jul 1, 09:40 UTC | 3h 40m |
| 2026-06-30 | IGO1316 | DOH → HYD | Jun 30, 17:50 UTC | Jul 1, 03:00 UTC | 9h 10m |
| 2026-06-30 | IGO25H | - | Jun 30, 11:20 UTC | Jun 30, 15:00 UTC | 3h 40m |
| 2026-06-30 | IGO32Y | DOH → DEL | Jun 30, 05:25 UTC | Jun 30, 09:25 UTC | 4h 0m |
| 2026-06-29 | IGO1316 | DOH → HYD | Jun 29, 17:59 UTC | Jun 30, 03:00 UTC | 9h 1m |
| 2026-06-29 | IGO25H | DXB → BOM | Jun 29, 10:55 UTC | Jun 29, 14:25 UTC | 3h 30m |
| 2026-06-29 | IGO32Y | DOH → DEL | Jun 29, 05:24 UTC | Jun 29, 09:14 UTC | 3h 50m |
| 2026-06-28 | IGO19M | DOH → DOH | Jun 28, 05:29 UTC | Jun 28, 14:39 UTC | 9h 10m |
| 2026-06-27 | IGO1313 | HYD → DOH | Jun 27, 19:34 UTC | Jun 28, 02:44 UTC | 7h 10m |
| 2026-06-27 | IGO1316 | DOH → HYD | Jun 27, 17:44 UTC | Jun 27, 18:39 UTC | 55m |
| 2026-06-27 | IGO19M | - | Jun 27, 05:10 UTC | Jun 27, 14:05 UTC | 8h 55m |
| 2026-06-26 | IGO1316 | DOH → HYD | Jun 26, 17:50 UTC | Jun 27, 02:55 UTC | 9h 5m |
| 2026-06-26 | IGO19M | DOH → DOH | Jun 26, 05:44 UTC | Jun 26, 14:50 UTC | 9h 5m |
| 2026-06-25 | IGO1316 | DOH → HYD | Jun 25, 17:54 UTC | Jun 26, 02:50 UTC | 8h 55m |
| 2026-06-25 | IGO25H | DXB → BOM | Jun 25, 10:55 UTC | Jun 25, 14:39 UTC | 3h 45m |
| 2026-06-25 | IGO32Y | DOH → DEL | Jun 25, 05:20 UTC | Jun 25, 09:10 UTC | 3h 50m |
| 2026-06-24 | IGO1316 | DOH → HYD | Jun 24, 17:59 UTC | Jun 25, 03:10 UTC | 9h 10m |
| 2026-06-24 | IGO53M | BOM → LHR | Jun 24, 05:24 UTC | Jun 24, 14:20 UTC | 8h 55m |
| 2026-06-23 | IGO1313 | HYD → DOH | Jun 23, 18:04 UTC | Jun 24, 03:00 UTC | 8h 55m |
| 2026-06-22 | IGO1321 | MAA → DOH | Jun 22, 22:54 UTC | Jun 23, 02:55 UTC | 4h 0m |
| 2026-06-22 | IGO1322 | DOH → MAA | Jun 22, 16:50 UTC | Jun 22, 20:34 UTC | 3h 45m |
| 2026-06-22 | IGO25H | DXB → BOM | Jun 22, 10:49 UTC | Jun 22, 14:34 UTC | 3h 45m |
| 2026-06-22 | IGO32Y | DOH → DEL | Jun 22, 05:20 UTC | Jun 22, 09:04 UTC | 3h 45m |
| 2026-06-21 | IGO41U | HYD → DED | Jun 21, 23:10 UTC | Jun 22, 02:04 UTC | 2h 55m |
| 2026-06-21 | IGO46V | - | Jun 21, 18:10 UTC | Jun 21, 21:10 UTC | 3h 0m |
| 2026-06-21 | IGO25H | DXB → BOM | Jun 21, 11:49 UTC | Jun 21, 15:30 UTC | 3h 40m |
| 2026-06-21 | IGO32Y | - | Jun 21, 05:59 UTC | Jun 21, 09:44 UTC | 3h 45m |
| 2026-06-20 | IGO1321 | MAA → DOH | Jun 20, 22:45 UTC | Jun 21, 02:40 UTC | 3h 55m |
| 2026-06-20 | IGO1322 | DOH → MAA | Jun 20, 16:55 UTC | Jun 20, 20:34 UTC | 3h 40m |
| 2026-06-20 | IGO25H | DXB → BOM | Jun 20, 14:14 UTC | Jun 20, 14:29 UTC | 15m |
| 2026-06-20 | IGO25H | DXB → BOM | Jun 20, 10:49 UTC | Jun 20, 12:34 UTC | 1h 45m |
| 2026-06-19 | IGO32Y | - | Jun 19, 23:29 UTC | Jun 20, 09:14 UTC | 9h 45m |
| 2026-06-19 | IGO1322 | DOH → MAA | Jun 19, 11:20 UTC | Jun 19, 21:19 UTC | 10h 0m |
| 2026-06-18 | IGO32Y | - | Jun 18, 19:35 UTC | Jun 19, 09:34 UTC | 13h 59m |
| 2026-06-18 | IGO32Y | - | Jun 18, 12:35 UTC | Jun 19, 09:34 UTC | 20h 59m |
| 2026-06-18 | IGO32Y | DEL → DEL | Jun 18, 11:05 UTC | Jun 19, 09:34 UTC | 22h 29m |
| 2026-06-17 | IGO32Y | - | Jun 17, 22:50 UTC | Jun 18, 09:15 UTC | 10h 25m |
| 2026-06-17 | IGO25H | DXB → BOM | Jun 17, 11:05 UTC | Jun 17, 20:35 UTC | 9h 30m |
| 2026-06-16 | IGO1316 | DOH → HYD | Jun 16, 19:40 UTC | Jun 17, 09:05 UTC | 13h 26m |
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 A7-AJG page for operator, model, and routing details .