sensors Mode-S transponder

801684

ICAO 24-bit transponder address · allocated to India

Currently assigned to VT-FIC · ATR-72-600

Hex
801684
Octal
40013204
Decimal
8,394,372
Country
IN
Tail
VT-FIC
Type
AT76
No current signal · last broadcast 4h ago
Flights observed
50
Distinct callsigns
11
Country
IN
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S 801684.

Country allocation

The ICAO 24-bit address 801684 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 11 distinct

Callsign Airline Flights Last seen
GOA5301 - 11 2026-05-18
GOA3412 Alberta Government 11 2026-06-04
GOA3411 Alberta Government 11 2026-06-04
GOA5206 Alberta Government 5 2026-06-06
GOA5302 - 4 2026-05-05
GOA3102 Alberta Government 2 2026-05-14
GOA3101 - 2 2026-05-14
GOA5205 Alberta Government 1 2026-06-06
GOA5202 Alberta Government 1 2026-06-01
GOA3104 - 1 2026-05-14
GOA3103 - 1 2026-05-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-06 GOA5206 - Jun 6, 11:30 UTCJun 6, 11:45 UTC15m
2026-06-06 GOA5205 - Jun 6, 10:00 UTCJun 6, 10:09 UTC10m
2026-06-04 GOA3412 BLR → HBX Jun 4, 13:40 UTCJun 4, 14:05 UTC25m
2026-06-04 GOA3411 HBX → BLR Jun 4, 11:55 UTCJun 4, 12:35 UTC40m
2026-06-03 GOA3412 BLR → HBX Jun 3, 13:45 UTCJun 3, 13:55 UTC10m
2026-06-03 GOA3411 HBX → BLR Jun 3, 12:05 UTCJun 3, 12:40 UTC35m
2026-06-01 GOA5202 - Jun 1, 11:55 UTCJun 1, 12:20 UTC25m
2026-05-30 GOA3412 BLR → HBX May 30, 14:50 UTCMay 30, 15:30 UTC40m
2026-05-30 GOA3411 HBX → BLR May 30, 13:00 UTCMay 30, 13:45 UTC45m
2026-05-29 GOA3412 BLR → HBX May 29, 13:20 UTCMay 29, 13:55 UTC35m
2026-05-29 GOA3411 HBX → BLR May 29, 12:00 UTCMay 29, 12:20 UTC20m
2026-05-28 GOA3412 BLR → HBX May 28, 13:40 UTCMay 28, 14:05 UTC25m
2026-05-28 GOA3411 HBX → BLR May 28, 11:55 UTCMay 28, 12:30 UTC35m
2026-05-26 GOA5206 - May 26, 10:34 UTCMay 26, 10:50 UTC15m
2026-05-25 GOA5206 - May 25, 10:45 UTCMay 25, 11:15 UTC30m
2026-05-24 GOA5206 - May 24, 10:50 UTCMay 24, 11:05 UTC15m
2026-05-22 GOA3412 BLR → HBX May 22, 13:45 UTCMay 22, 13:55 UTC10m
2026-05-22 GOA3411 HBX → BLR May 22, 12:00 UTCMay 22, 12:30 UTC30m
2026-05-19 GOA5206 - May 19, 12:55 UTCMay 19, 13:10 UTC15m
2026-05-18 GOA5301 - May 18, 04:45 UTCMay 18, 05:20 UTC35m
2026-05-16 GOA5301 - May 16, 04:55 UTCMay 16, 05:30 UTC35m
2026-05-14 GOA3104 - May 14, 09:20 UTCMay 14, 09:30 UTC10m
2026-05-14 GOA3103 - May 14, 08:15 UTCMay 14, 08:25 UTC10m
2026-05-14 GOA3102 COK → AGX May 14, 05:35 UTCMay 14, 05:50 UTC15m
2026-05-14 GOA3101 - May 14, 04:40 UTCMay 14, 04:51 UTC10m
2026-05-09 GOA3412 BLR → HBX May 9, 13:40 UTCMay 9, 14:20 UTC40m
2026-05-09 GOA3411 HBX → BLR May 9, 12:00 UTCMay 9, 12:35 UTC35m
2026-05-08 GOA5301 - May 8, 06:35 UTCMay 8, 06:54 UTC20m
2026-05-08 GOA5301 - May 8, 04:54 UTCMay 8, 05:24 UTC30m
2026-05-05 GOA5302 - May 5, 07:40 UTCMay 5, 08:10 UTC30m
2026-05-05 GOA5301 - May 5, 06:10 UTCMay 5, 06:40 UTC30m
2026-05-04 GOA5302 - May 4, 06:45 UTCMay 4, 06:55 UTC10m
2026-05-04 GOA5301 - May 4, 05:10 UTCMay 4, 05:45 UTC35m
2026-05-03 GOA5302 - May 3, 06:20 UTCMay 3, 06:55 UTC35m
2026-05-03 GOA5301 - May 3, 04:55 UTCMay 3, 05:25 UTC30m
2026-05-02 GOA5301 - May 2, 05:10 UTCMay 2, 05:50 UTC40m
2026-05-01 GOA3102 - May 1, 06:40 UTCMay 1, 06:55 UTC15m
2026-05-01 GOA3101 - May 1, 05:20 UTCMay 1, 05:40 UTC20m
2026-04-30 GOA5301 - Apr 30, 05:00 UTCApr 30, 05:35 UTC35m
2026-04-29 GOA5301 - Apr 29, 04:44 UTCApr 29, 05:20 UTC35m
2026-04-24 GOA3412 BLR → HBX Apr 24, 13:25 UTCApr 24, 13:40 UTC15m
2026-04-24 GOA3411 HBX → BLR Apr 24, 12:00 UTCApr 24, 12:25 UTC25m
2026-04-23 GOA5302 - Apr 23, 06:35 UTCApr 23, 07:10 UTC35m
2026-04-23 GOA5301 - Apr 23, 05:00 UTCApr 23, 05:30 UTC30m
2026-04-22 GOA3412 BLR → HBX Apr 22, 13:30 UTCApr 22, 14:05 UTC35m
2026-04-22 GOA3411 HBX → BLR Apr 22, 11:55 UTCApr 22, 12:20 UTC25m
2026-04-21 GOA3412 BLR → HBX Apr 21, 13:25 UTCApr 21, 14:10 UTC45m
2026-04-21 GOA3411 HBX → BLR Apr 21, 12:01 UTCApr 21, 12:25 UTC25m
2026-04-20 GOA3412 BLR → HBX Apr 20, 13:30 UTCApr 20, 13:50 UTC20m
2026-04-20 GOA3411 HBX → BLR Apr 20, 12:20 UTCApr 20, 12:45 UTC25m

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

Mode-S 801684 frequently asked

What is Mode-S code 801684?
801684 is an ICAO 24-bit transponder address. Allocated to India. Assigned to VT-FIC.
Where is Mode-S 801684 registered?
Mode-S code 801684 is allocated to India (IN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 801684 broadcasting right now?
No active broadcast right now. Last signal was 4h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 801684, octal 40013204, decimal 8,394,372.
What flights does 801684 operate?
Mode-S 801684 has broadcast 11 distinct callsigns, including GOA5301, GOA3412, GOA3411, GOA5206, GOA5302.