sensors Mode-S transponder

800D00

ICAO 24-bit transponder address · allocated to India

Currently assigned to VT-IVY · AIRBUS A-320neo

Hex
800D00
Octal
40006400
Decimal
8,391,936
Country
IN
Tail
VT-IVY
Type
A20N
No current signal · last broadcast 1d ago
Flights observed
212
Distinct callsigns
20
Country
IN
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 800D00.

Country allocation

The ICAO 24-bit address 800D00 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
IGO5338 IndiGo Airlines 6 2026-06-03
IGO737 IndiGo Airlines 3 2026-06-03
IGO5316 - 3 2026-06-03
IGO512W - 3 2026-06-03
IGO2219 - 3 2026-06-15
IGO209H IndiGo Airlines 3 2026-06-15
IGO942 IndiGo Airlines 2 2026-06-27
IGO931P - 2 2026-05-24
IGO829 - 2 2026-07-02
IGO793 - 2 2026-05-31
IGO792 - 2 2026-07-03
IGO791 - 2 2026-07-03
IGO72H IndiGo Airlines 2 2026-05-28
IGO6902 IndiGo Airlines 2 2026-06-16
IGO658M IndiGo Airlines 2 2026-05-24
IGO6507 - 2 2026-06-24
IGO6469 IndiGo Airlines 2 2026-06-09
IGO6276 IndiGo Airlines 2 2026-05-24
IGO6224 IndiGo Airlines 2 2026-05-23
IGO6137 IndiGo Airlines 2 2026-06-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-05 IGO796 - Jul 5, 17:05 UTCJul 5, 17:35 UTC30m
2026-07-05 IGO6077 - Jul 5, 15:00 UTCJul 5, 15:20 UTC20m
2026-07-05 IGO96F - Jul 5, 07:40 UTCJul 5, 13:30 UTC5h 50m
2026-07-05 IGO17E - Jul 5, 05:45 UTCJul 5, 06:05 UTC20m
2026-07-05 IGO17E - Jul 5, 02:45 UTCJul 5, 04:05 UTC1h 20m
2026-07-04 IGO6744 - Jul 4, 17:45 UTCJul 4, 17:55 UTC10m
2026-07-04 IGO2169 - Jul 4, 14:25 UTCJul 4, 15:00 UTC35m
2026-07-04 IGO2416 - Jul 4, 12:30 UTCJul 4, 13:10 UTC40m
2026-07-04 IGO235H - Jul 4, 10:15 UTCJul 4, 10:45 UTC30m
2026-07-04 IGO6729 - Jul 4, 08:20 UTCJul 4, 09:15 UTC55m
2026-07-04 IGO127 - Jul 4, 06:35 UTCJul 4, 07:15 UTC40m
2026-07-04 IGO6793 - Jul 4, 04:50 UTCJul 4, 05:25 UTC35m
2026-07-03 IGO974H - Jul 3, 15:35 UTCJul 4, 03:00 UTC11h 25m
2026-07-03 IGO371W - Jul 3, 10:10 UTCJul 3, 14:30 UTC4h 20m
2026-07-03 IGO792 - Jul 3, 08:25 UTCJul 3, 08:35 UTC10m
2026-07-03 IGO791 - Jul 3, 04:55 UTCJul 3, 05:05 UTC10m
2026-07-02 IGO829 - Jul 2, 15:25 UTCJul 2, 15:40 UTC15m
2026-07-02 IGO1504 - Jul 2, 01:45 UTCJul 2, 14:50 UTC13h 5m
2026-07-01 IGO1501 - Jul 1, 21:00 UTCJul 1, 21:35 UTC35m
2026-07-01 IGO6619 - Jul 1, 19:00 UTCJul 1, 19:10 UTC10m
2026-07-01 IGO157H - Jul 1, 14:20 UTCJul 1, 14:30 UTC10m
2026-07-01 IGO5932 AIP → BOM Jul 1, 10:30 UTCJul 1, 12:45 UTC2h 15m
2026-07-01 IGO5931 - Jul 1, 07:40 UTCJul 1, 09:20 UTC1h 40m
2026-07-01 IGO792E - Jul 1, 03:35 UTCJul 1, 04:25 UTC50m
2026-06-30 IGO5283 - Jun 30, 16:50 UTCJun 30, 17:05 UTC15m
2026-06-30 IGO5160 - Jun 30, 14:20 UTCJun 30, 15:20 UTC1h 0m
2026-06-30 IGO23LA - Jun 30, 11:55 UTCJun 30, 12:30 UTC35m
2026-06-30 IGO925 - Jun 30, 10:20 UTCJun 30, 10:50 UTC30m
2026-06-29 IGO54YH - Jun 29, 15:39 UTCJun 29, 16:10 UTC30m
2026-06-29 IGO6713 - Jun 29, 10:50 UTCJun 29, 14:44 UTC3h 55m
2026-06-29 IGO6712 - Jun 29, 08:50 UTCJun 29, 09:34 UTC45m
2026-06-28 IGO1424 - Jun 28, 22:15 UTCJun 29, 00:39 UTC2h 25m
2026-06-28 IGO1423 - Jun 28, 18:10 UTCJun 28, 20:29 UTC2h 20m
2026-06-28 IGO544 - Jun 28, 14:04 UTCJun 28, 14:19 UTC15m
2026-06-28 IGO422C - Jun 28, 12:09 UTCJun 28, 12:25 UTC15m
2026-06-28 IGO6522 - Jun 28, 09:20 UTCJun 28, 09:30 UTC10m
2026-06-27 IGO78F - Jun 27, 21:59 UTCJun 27, 22:29 UTC30m
2026-06-27 IGO1435 CCJ → AUH Jun 27, 16:59 UTCJun 27, 20:14 UTC3h 15m
2026-06-27 IGO152 - Jun 27, 13:55 UTCJun 27, 14:14 UTC20m
2026-06-27 IGO942 AGR → BLR Jun 27, 12:19 UTCJun 27, 12:29 UTC10m
2026-06-27 IGO942 AGR → BLR Jun 27, 10:25 UTCJun 27, 10:45 UTC20m
2026-06-27 IGO941 - Jun 27, 07:30 UTCJun 27, 07:39 UTC10m
2026-06-26 IGO6137 MAA → RPR Jun 26, 18:39 UTCJun 26, 18:49 UTC10m
2026-06-26 IGO6137 MAA → RPR Jun 26, 17:40 UTCJun 26, 17:50 UTC10m
2026-06-26 IGO466W - Jun 26, 14:15 UTCJun 26, 15:15 UTC1h 0m
2026-06-26 IGO5159 BOM → HSR Jun 26, 12:29 UTCJun 26, 12:59 UTC30m
2026-06-26 IGO5155 RDP → BOM Jun 26, 11:00 UTCJun 26, 11:20 UTC20m
2026-06-26 IGO5155 RDP → BOM Jun 26, 09:00 UTCJun 26, 09:30 UTC30m
2026-06-26 IGO5125 AMD → BOM Jun 26, 05:50 UTCJun 26, 07:55 UTC2h 5m
2026-06-26 IGO5146 HYD → BOM Jun 26, 03:05 UTCJun 26, 03:54 UTC50m

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

Mode-S 800D00 frequently asked

What is Mode-S code 800D00?
800D00 is an ICAO 24-bit transponder address. Allocated to India. Assigned to VT-IVY.
Where is Mode-S 800D00 registered?
Mode-S code 800D00 is allocated to India (IN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 800D00 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 800D00, octal 40006400, decimal 8,391,936.
What flights does 800D00 operate?
Mode-S 800D00 has broadcast 20 distinct callsigns, including IGO5338, IGO737, IGO5316, IGO512W, IGO2219.