sensors Mode-S transponder

8003F1

ICAO 24-bit transponder address · allocated to India

Currently assigned to VT-AXR · BOEING 737-800

Hex
8003F1
Octal
40001761
Decimal
8,389,617
Country
IN
Tail
VT-AXR
Type
B738
No current signal · last broadcast 14d ago
Flights observed
55
Distinct callsigns
11
Country
IN
Last broadcast
14d ago

Last known position

Most recent position reported by Mode-S 8003F1.

Country allocation

The ICAO 24-bit address 8003F1 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-15 AXB6003 COK → HYD May 15, 10:10 UTCMay 15, 10:25 UTC15m
2026-05-15 AXB689 SIN → TRZ May 15, 04:45 UTCMay 15, 05:30 UTC45m
2026-05-15 AXB690 TRZ → SIN May 15, 01:10 UTCMay 15, 02:00 UTC50m
2026-05-14 AXB612 DXB → TRZ May 14, 07:45 UTCMay 14, 16:40 UTC8h 55m
2026-05-13 AXB689 SIN → TRZ May 13, 04:15 UTCMay 13, 04:45 UTC30m
2026-05-13 AXB690 TRZ → SIN May 13, 01:20 UTCMay 13, 02:00 UTC40m
2026-05-12 AXB611 TRZ → DXB May 12, 08:00 UTCMay 12, 16:40 UTC8h 40m
2026-05-11 AXB689 SIN → TRZ May 11, 04:15 UTCMay 11, 04:50 UTC35m
2026-05-11 AXB690 TRZ → SIN May 11, 01:25 UTCMay 11, 02:05 UTC40m
2026-05-10 AXB689 SIN → TRZ May 10, 04:09 UTCMay 10, 04:39 UTC30m
2026-05-10 AXB690 TRZ → SIN May 10, 01:20 UTCMay 10, 02:00 UTC40m
2026-05-09 AXB612 DXB → TRZ May 9, 16:00 UTCMay 9, 16:55 UTC55m
2026-05-09 AXB612 DXB → TRZ May 9, 13:05 UTCMay 9, 13:25 UTC20m
2026-05-09 AXB611 TRZ → DXB May 9, 07:50 UTCMay 9, 08:25 UTC35m
2026-05-08 AXB689 SIN → TRZ May 8, 04:09 UTCMay 8, 04:44 UTC35m
2026-05-08 AXB690 TRZ → SIN May 8, 01:35 UTCMay 8, 02:14 UTC40m
2026-05-07 AXB612 DXB → TRZ May 7, 08:05 UTCMay 7, 16:40 UTC8h 35m
2026-05-06 AXB689 SIN → TRZ May 6, 04:35 UTCMay 6, 05:10 UTC35m
2026-05-06 AXB690 TRZ → SIN May 6, 01:45 UTCMay 6, 02:20 UTC35m
2026-05-05 AXB611 TRZ → DXB May 5, 08:05 UTCMay 5, 16:50 UTC8h 45m
2026-05-04 AXB689 SIN → TRZ May 4, 03:54 UTCMay 4, 04:34 UTC40m
2026-05-04 AXB690 TRZ → SIN May 4, 01:35 UTCMay 4, 02:30 UTC55m
2026-05-03 AXB612 DXB → TRZ May 3, 13:15 UTCMay 3, 16:40 UTC3h 25m
2026-05-03 AXB611 TRZ → DXB May 3, 07:55 UTCMay 3, 11:45 UTC3h 50m
2026-05-02 AXB689 SIN → TRZ May 2, 03:55 UTCMay 2, 04:40 UTC45m
2026-05-02 AXB690 TRZ → SIN May 2, 01:20 UTCMay 2, 02:15 UTC55m
2026-05-01 AXB690 TRZ → SIN May 1, 04:20 UTCMay 2, 02:15 UTC21h 55m
2026-05-01 AXB690 TRZ → SIN May 1, 04:05 UTCMay 2, 02:15 UTC22h 10m
2026-05-01 AXB690 TRZ → SIN May 1, 01:35 UTCMay 1, 02:25 UTC50m
2026-04-30 AXB940 JED → HYD Apr 30, 00:25 UTCApr 30, 19:00 UTC18h 35m
2026-04-29 AXB940 JED → HYD Apr 29, 15:15 UTCApr 30, 11:00 UTC19h 44m
2026-04-29 AXB5309 CNN → TRV Apr 29, 02:30 UTCApr 29, 03:10 UTC40m
2026-04-28 AXB6802 SHJ → CNN Apr 28, 07:20 UTCApr 28, 07:45 UTC25m
2026-04-27 AXB6801 CNN → SHJ Apr 27, 19:05 UTCApr 28, 05:30 UTC10h 25m
2026-04-27 AXB6801 CNN → SHJ Apr 27, 07:20 UTCApr 28, 05:30 UTC22h 10m
2026-04-27 AXB6801 CNN → SHJ Apr 27, 04:45 UTCApr 27, 05:20 UTC35m
2026-04-26 AXB6802 SHJ → CNN Apr 26, 07:10 UTCApr 26, 07:35 UTC25m
2026-04-26 AXB6801 CNN → SHJ Apr 26, 04:50 UTCApr 26, 05:25 UTC35m
2026-04-25 AXB6802 SHJ → CNN Apr 25, 07:10 UTCApr 25, 07:30 UTC20m
2026-04-25 AXB6801 CNN → SHJ Apr 25, 04:50 UTCApr 25, 05:20 UTC30m
2026-04-24 AXB5310 TRV → CNN Apr 24, 08:20 UTCApr 24, 08:50 UTC30m
2026-04-24 AXB5309 CNN → TRV Apr 24, 00:15 UTCApr 24, 00:50 UTC35m
2026-04-23 AXB789 CNN → RUH Apr 23, 10:30 UTCApr 23, 14:05 UTC3h 35m
2026-04-22 AXB5310 TRV → CNN Apr 22, 11:00 UTCApr 22, 11:25 UTC25m
2026-04-22 AXB5309 CNN → TRV Apr 22, 02:25 UTCApr 22, 03:05 UTC40m
2026-04-20 AXB6802 SHJ → CNN Apr 20, 07:35 UTCApr 20, 08:00 UTC25m
2026-04-20 AXB6801 CNN → SHJ Apr 20, 05:40 UTCApr 20, 06:20 UTC40m
2026-04-19 AXB6801 CNN → SHJ Apr 19, 07:40 UTCApr 20, 06:15 UTC22h 35m
2026-04-19 AXB6801 CNN → SHJ Apr 19, 05:50 UTCApr 19, 06:25 UTC35m
2026-04-18 AXB6802 SHJ → CNN Apr 18, 07:45 UTCApr 19, 06:15 UTC22h 30m

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

Mode-S 8003F1 frequently asked

What is Mode-S code 8003F1?
8003F1 is an ICAO 24-bit transponder address. Allocated to India. Assigned to VT-AXR.
Where is Mode-S 8003F1 registered?
Mode-S code 8003F1 is allocated to India (IN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 8003F1 broadcasting right now?
No active broadcast right now. Last signal was 14d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 8003F1, octal 40001761, decimal 8,389,617.
What flights does 8003F1 operate?
Mode-S 8003F1 has broadcast 11 distinct callsigns, including AXB690, AXB6801, AXB689, AXB6802, AXB612.