sensors Mode-S transponder
801804
ICAO 24-bit transponder address · allocated to India
- Hex
- 801804
- Octal
- 40014004
- Decimal
- 8,394,756
- Country
- IN
- Flights observed
- 251
- Distinct callsigns
- 20
- Country
- IN
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 801804 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 |
|---|---|---|---|
| IGO1021 | IndiGo Airlines | 14 | 2026-05-20 |
| IGO1022 | IndiGo Airlines | 13 | 2026-05-21 |
| IGO19K | - | 9 | 2026-05-21 |
| IGO255K | - | 7 | 2026-05-29 |
| IGO1064 | IndiGo Airlines | 7 | 2026-04-23 |
| IGO611H | IndiGo Airlines | 6 | 2026-05-29 |
| IGO1060 | IndiGo Airlines | 6 | 2026-04-23 |
| IGO1053 | IndiGo Airlines | 6 | 2026-04-23 |
| IGO89KA | - | 4 | 2026-05-02 |
| IGO609Y | - | 4 | 2026-05-29 |
| IGO316P | - | 4 | 2026-05-22 |
| IGO137P | IndiGo Airlines | 4 | 2026-05-02 |
| IGO1051 | IndiGo Airlines | 4 | 2026-04-23 |
| IGO1011 | IndiGo Airlines | 4 | 2026-04-14 |
| IGO1002 | IndiGo Airlines | 4 | 2026-05-29 |
| IGO1001 | IndiGo Airlines | 4 | 2026-05-29 |
| IGO6676 | IndiGo Airlines | 3 | 2026-05-12 |
| IGO6349 | IndiGo Airlines | 3 | 2026-05-29 |
| IGO6225 | IndiGo Airlines | 3 | 2026-05-02 |
| IGO5337 | IndiGo Airlines | 3 | 2026-05-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | IGO1002 | SIN → MAA | May 29, 21:25 UTC | May 30, 04:15 UTC | 6h 50m |
| 2026-05-29 | IGO1001 | MAA → SIN | May 29, 13:35 UTC | May 29, 19:10 UTC | 5h 35m |
| 2026-05-29 | IGO255K | - | May 29, 12:45 UTC | May 29, 12:50 UTC | 5m |
| 2026-05-29 | IGO611H | MAA → BOM | May 29, 07:35 UTC | May 29, 11:30 UTC | 3h 55m |
| 2026-05-29 | IGO6349 | BOM → MAA | May 29, 06:50 UTC | May 29, 07:00 UTC | 10m |
| 2026-05-29 | IGO609Y | - | May 29, 04:55 UTC | May 29, 05:20 UTC | 25m |
| 2026-05-28 | IGO1002 | SIN → MAA | May 28, 21:00 UTC | May 29, 04:10 UTC | 7h 10m |
| 2026-05-28 | IGO1001 | MAA → SIN | May 28, 13:35 UTC | May 28, 19:10 UTC | 5h 35m |
| 2026-05-28 | IGO255K | - | May 28, 12:40 UTC | May 28, 12:50 UTC | 10m |
| 2026-05-28 | IGO611H | MAA → BOM | May 28, 10:45 UTC | May 28, 11:25 UTC | 40m |
| 2026-05-28 | IGO611H | MAA → BOM | May 28, 07:50 UTC | May 28, 10:05 UTC | 2h 15m |
| 2026-05-28 | IGO609Y | - | May 28, 04:50 UTC | May 28, 05:15 UTC | 25m |
| 2026-05-27 | IGO255K | - | May 27, 13:30 UTC | May 28, 04:05 UTC | 14h 35m |
| 2026-05-27 | IGO255K | - | May 27, 12:35 UTC | May 27, 12:40 UTC | 5m |
| 2026-05-27 | IGO611H | MAA → BOM | May 27, 10:50 UTC | May 27, 11:25 UTC | 35m |
| 2026-05-27 | IGO611H | MAA → BOM | May 27, 07:50 UTC | May 27, 10:10 UTC | 2h 20m |
| 2026-05-27 | IGO6349 | BOM → MAA | May 27, 06:49 UTC | May 27, 07:00 UTC | 11m |
| 2026-05-27 | IGO609Y | - | May 27, 04:55 UTC | May 27, 05:19 UTC | 25m |
| 2026-05-26 | IGO1002 | SIN → MAA | May 26, 21:09 UTC | May 27, 04:19 UTC | 7h 10m |
| 2026-05-26 | IGO1001 | MAA → SIN | May 26, 13:45 UTC | May 26, 19:30 UTC | 5h 45m |
| 2026-05-26 | IGO255K | - | May 26, 12:50 UTC | May 26, 13:00 UTC | 10m |
| 2026-05-26 | IGO611H | MAA → BOM | May 26, 11:00 UTC | May 26, 11:24 UTC | 25m |
| 2026-05-26 | IGO6349 | BOM → MAA | May 26, 07:49 UTC | May 26, 10:14 UTC | 2h 25m |
| 2026-05-26 | IGO609Y | - | May 26, 05:00 UTC | May 26, 05:30 UTC | 30m |
| 2026-05-25 | IGO1002 | SIN → MAA | May 25, 22:05 UTC | May 26, 04:20 UTC | 6h 15m |
| 2026-05-25 | IGO1001 | MAA → SIN | May 25, 19:44 UTC | May 25, 20:30 UTC | 45m |
| 2026-05-25 | IGO255K | - | May 25, 14:40 UTC | May 25, 14:55 UTC | 15m |
| 2026-05-25 | IGO255K | - | May 25, 13:40 UTC | May 25, 13:50 UTC | 10m |
| 2026-05-25 | IGO69TA | - | May 25, 11:55 UTC | May 25, 12:15 UTC | 20m |
| 2026-05-25 | IGO246F | - | May 25, 05:30 UTC | May 25, 05:50 UTC | 20m |
| 2026-05-25 | IGO5194 | CCU → BOM | May 25, 03:00 UTC | May 25, 03:15 UTC | 15m |
| 2026-05-24 | IGO930 | GAU → DEL | May 24, 21:20 UTC | May 24, 21:45 UTC | 25m |
| 2026-05-24 | IGO145F | - | May 24, 16:55 UTC | May 24, 19:15 UTC | 2h 20m |
| 2026-05-24 | IGO354M | BOM → NAG | May 24, 15:35 UTC | May 24, 15:50 UTC | 15m |
| 2026-05-24 | IGO354M | BOM → NAG | May 24, 13:30 UTC | May 24, 14:05 UTC | 35m |
| 2026-05-24 | IGO29YP | - | May 24, 09:25 UTC | May 24, 11:55 UTC | 2h 30m |
| 2026-05-24 | IGO121V | DEL → BLR | May 24, 07:45 UTC | May 24, 07:55 UTC | 10m |
| 2026-05-24 | IGO121V | DEL → BLR | May 24, 05:40 UTC | May 24, 06:15 UTC | 35m |
| 2026-05-24 | IGO863V | BLR → DEL | May 24, 01:10 UTC | May 24, 03:35 UTC | 2h 25m |
| 2026-05-23 | IGO426L | CCU → HYD | May 23, 23:50 UTC | May 24, 00:00 UTC | 10m |
| 2026-05-23 | IGO426L | CCU → HYD | May 23, 21:50 UTC | May 23, 22:25 UTC | 35m |
| 2026-05-23 | IGO461L | - | May 23, 18:50 UTC | May 23, 20:35 UTC | 1h 45m |
| 2026-05-23 | IGO182E | - | May 23, 15:45 UTC | May 23, 17:35 UTC | 1h 50m |
| 2026-05-23 | IGO315 | DEL → COK | May 23, 11:55 UTC | May 23, 13:40 UTC | 1h 45m |
| 2026-05-23 | IGO390M | DEL → BOM | May 23, 08:45 UTC | May 23, 10:30 UTC | 1h 45m |
| 2026-05-23 | IGO671W | - | May 23, 05:30 UTC | May 23, 07:15 UTC | 1h 45m |
| 2026-05-23 | IGO769Y | BBI → BLR | May 23, 02:10 UTC | May 23, 03:50 UTC | 1h 39m |
| 2026-05-22 | IGO647Y | NAG → BLR | May 22, 14:50 UTC | May 22, 16:35 UTC | 1h 45m |
| 2026-05-22 | IGO316P | - | May 22, 12:25 UTC | May 22, 12:55 UTC | 30m |
| 2026-05-22 | IGO316P | - | May 22, 10:55 UTC | May 22, 11:40 UTC | 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.