Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0E83

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VFI · BOEING 737-300

Hex
0D0E83
Octal
03207203
Decimal
855,683
Country
MX
Tail
XA-VFI
Type
B733
No current signal · last broadcast Jul 26, 14:10 UTC
Flights observed
133
Distinct callsigns
10
Country
MX
Last broadcast
Jul 26, 14:10 UTC

Last known position

Most recent position reported by Mode-S 0D0E83.

Country allocation

The ICAO 24-bit address 0D0E83 falls within the block assigned to Mexico (MX) by ICAO Annex 10, Volume III. Every aircraft registered in Mexico 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 10 distinct

Callsign Airline Flights Last seen
VTM9902 - 55 2026-07-26
VTM9901 - 22 2026-07-26
VTM5002 - 15 2026-06-30
VTM1102 - 13 2026-07-25
VTM5001 - 11 2026-07-01
VTM1101 - 11 2026-07-11
VTM5004 - 2 2026-06-02
VTM4402 - 2 2026-06-04
VTM9904 - 1 2026-07-01
VTM4401 - 1 2026-06-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 VTM9901 - Jul 26, 13:50 UTCJul 26, 14:10 UTC20m
2026-07-26 VTM9902 - Jul 26, 12:35 UTCJul 26, 13:00 UTC25m
2026-07-26 VTM9902 - Jul 26, 01:25 UTCJul 26, 10:55 UTC9h 31m
2026-07-25 VTM1102 - Jul 25, 12:45 UTCJul 25, 13:00 UTC15m
2026-07-24 VTM9901 - Jul 24, 01:15 UTCJul 24, 02:30 UTC1h 15m
2026-07-23 VTM9901 - Jul 23, 01:30 UTCJul 23, 12:15 UTC10h 45m
2026-07-22 VTM9901 - Jul 22, 01:25 UTCJul 22, 12:25 UTC11h 0m
2026-07-21 VTM9902 - Jul 21, 10:45 UTCJul 21, 12:25 UTC1h 40m
2026-07-18 VTM9901 - Jul 18, 02:00 UTCJul 18, 03:35 UTC1h 36m
2026-07-17 VTM9902 - Jul 17, 01:45 UTCJul 17, 12:15 UTC10h 30m
2026-07-16 VTM9902 - Jul 16, 01:40 UTCJul 16, 12:20 UTC10h 40m
2026-07-15 VTM9902 - Jul 15, 01:40 UTCJul 15, 12:05 UTC10h 25m
2026-07-14 VTM9902 - Jul 14, 04:45 UTCJul 14, 12:20 UTC7h 35m
2026-07-12 VTM9901 - Jul 12, 13:55 UTCJul 12, 14:15 UTC20m
2026-07-12 VTM9902 - Jul 12, 12:35 UTCJul 12, 13:01 UTC25m
2026-07-12 VTM9902 - Jul 12, 01:55 UTCJul 12, 10:55 UTC9h 0m
2026-07-11 VTM1102 - Jul 11, 12:30 UTCJul 11, 12:50 UTC20m
2026-07-11 VTM1101 - Jul 11, 01:50 UTCJul 11, 02:05 UTC15m
2026-07-10 VTM1102 - Jul 10, 12:50 UTCJul 10, 13:05 UTC15m
2026-07-10 VTM1101 - Jul 10, 01:45 UTCJul 10, 02:05 UTC20m
2026-07-09 VTM1102 - Jul 9, 13:00 UTCJul 9, 13:15 UTC15m
2026-07-09 VTM9901 - Jul 9, 01:40 UTCJul 9, 03:05 UTC1h 25m
2026-07-08 VTM9902 CUN → CUN Jul 8, 01:35 UTCJul 8, 12:45 UTC11h 10m
2026-07-07 VTM9902 - Jul 7, 04:50 UTCJul 7, 12:30 UTC7h 40m
2026-07-06 VTM9902 - Jul 6, 14:10 UTCJul 6, 14:35 UTC25m
2026-07-06 VTM9902 - Jul 6, 13:00 UTCJul 6, 13:20 UTC20m
2026-07-06 VTM9902 - Jul 6, 11:00 UTCJul 6, 11:40 UTC40m
2026-07-05 VTM1101 - Jul 5, 02:10 UTCJul 5, 02:25 UTC15m
2026-07-04 VTM9901 CUN → HMO Jul 4, 01:40 UTCJul 4, 13:10 UTC11h 30m
2026-07-03 VTM9902 - Jul 3, 01:45 UTCJul 3, 12:10 UTC10h 25m
2026-07-02 VTM9902 - Jul 2, 04:20 UTCJul 2, 12:20 UTC8h 0m
2026-07-01 VTM9904 - Jul 1, 10:50 UTCJul 2, 10:45 UTC23h 55m
2026-07-01 VTM5001 - Jul 1, 10:20 UTCJul 2, 05:00 UTC18h 40m
2026-07-01 VTM5001 - Jul 1, 04:15 UTCJul 1, 11:10 UTC6h 55m
2026-07-01 VTM5001 - Jul 1, 02:45 UTCJul 1, 03:20 UTC35m
2026-06-30 VTM5002 - Jun 30, 13:40 UTCJun 30, 14:00 UTC20m
2026-06-30 VTM5002 - Jun 30, 04:55 UTCJun 30, 13:00 UTC8h 5m
2026-06-28 VTM9902 - Jun 28, 14:30 UTCJun 28, 14:50 UTC20m
2026-06-28 VTM9902 - Jun 28, 12:50 UTCJun 28, 13:19 UTC30m
2026-06-28 VTM9902 - Jun 28, 10:39 UTCJun 28, 11:29 UTC50m
2026-06-27 VTM1101 - Jun 27, 02:04 UTCJun 27, 02:25 UTC20m
2026-06-26 VTM1102 - Jun 26, 12:59 UTCJun 26, 13:19 UTC20m
2026-06-25 VTM9901 - Jun 25, 01:35 UTCJun 25, 03:15 UTC1h 40m
2026-06-24 VTM9902 CUN → CUN Jun 24, 01:34 UTCJun 24, 12:14 UTC10h 40m
2026-06-23 VTM9902 - Jun 23, 04:25 UTCJun 23, 13:24 UTC9h 0m
2026-06-21 VTM9901 - Jun 21, 14:19 UTCJun 21, 14:44 UTC25m
2026-06-21 VTM9902 - Jun 21, 12:35 UTCJun 21, 12:55 UTC20m
2026-06-21 VTM9902 - Jun 21, 02:30 UTCJun 21, 11:05 UTC8h 35m
2026-06-20 VTM1102 - Jun 20, 13:59 UTCJun 20, 14:50 UTC50m
2026-06-20 VTM1102 - Jun 20, 12:59 UTCJun 20, 13:14 UTC15m

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

Mode-S 0D0E83 frequently asked

What is Mode-S code 0D0E83?
0D0E83 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VFI.
Where is Mode-S 0D0E83 registered?
Mode-S code 0D0E83 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0E83 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 14:10 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0E83, octal 03207203, decimal 855,683.
What flights does 0D0E83 operate?
Mode-S 0D0E83 has broadcast 10 distinct callsigns, including VTM9902, VTM9901, VTM5002, VTM1102, VTM5001.