Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D103F

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VDB · AIRBUS A-320

Hex
0D103F
Octal
03210077
Decimal
856,127
Country
MX
Tail
XA-VDB
Type
A320
No current signal · last broadcast 13h ago
Flights observed
373
Distinct callsigns
20
Country
MX
Last broadcast
13h ago

Last known position

Most recent position reported by Mode-S 0D103F.

Country allocation

The ICAO 24-bit address 0D103F 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 20 distinct

Callsign Airline Flights Last seen
VIV7435 - 34 2026-07-12
VIV7434 - 31 2026-07-12
VIV8005 - 13 2026-07-11
VIV8004 - 13 2026-07-11
VIV4044 VivaAerobus 12 2026-05-26
VIV8013 - 11 2026-07-12
VIV4043 VivaAerobus 11 2026-05-27
VIV8012 - 10 2026-07-12
VIV7333 VivaAerobus 10 2026-04-29
VIV4042 VivaAerobus 10 2026-05-27
VIV4041 VivaAerobus 10 2026-05-27
VIV7332 VivaAerobus 9 2026-04-29
VIV8014 - 8 2026-07-08
VIV8011 - 8 2026-07-13
VIV7033 VivaAerobus 8 2026-05-26
VIV2022 VivaAerobus 8 2026-05-27
VIV2015 VivaAerobus 8 2026-05-26
VIV8015 - 7 2026-07-13
VIV7032 VivaAerobus 7 2026-05-26
VIV7005 - 7 2026-07-01

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 VIV8011 - Jul 13, 15:15 UTCJul 13, 15:50 UTC35m
2026-07-13 VIV8015 MTY → MTY Jul 13, 03:45 UTCJul 13, 13:40 UTC9h 55m
2026-07-12 VIV8013 MTY → MTY Jul 12, 23:15 UTCJul 13, 02:40 UTC3h 25m
2026-07-12 VIV8012 - Jul 12, 03:55 UTCJul 12, 22:20 UTC18h 25m
2026-07-12 VIV7435 - Jul 12, 03:10 UTCJul 12, 03:20 UTC10m
2026-07-12 VIV7435 - Jul 12, 01:35 UTCJul 12, 02:15 UTC40m
2026-07-12 VIV7434 - Jul 12, 00:10 UTCJul 12, 00:45 UTC35m
2026-07-11 VIV8005 - Jul 11, 16:45 UTCJul 11, 22:30 UTC5h 45m
2026-07-11 VIV8004 - Jul 11, 04:01 UTCJul 11, 15:15 UTC11h 15m
2026-07-11 VIV7435 - Jul 11, 01:20 UTCJul 11, 01:50 UTC30m
2026-07-10 VIV7434 - Jul 10, 23:55 UTCJul 11, 00:30 UTC35m
2026-07-10 VIV8005 - Jul 10, 16:35 UTCJul 10, 22:00 UTC5h 26m
2026-07-10 VIV8004 - Jul 10, 13:00 UTCJul 10, 15:20 UTC2h 20m
2026-07-09 VIV8011 - Jul 9, 15:10 UTCJul 10, 13:45 UTC22h 35m
2026-07-09 VIV8010 - Jul 9, 04:00 UTCJul 9, 13:50 UTC9h 50m
2026-07-08 VIV8014 MTY → MTY Jul 8, 23:25 UTCJul 9, 02:55 UTC3h 30m
2026-07-08 VIV8012 - Jul 8, 21:40 UTCJul 8, 22:20 UTC40m
2026-07-07 VIV8011 - Jul 7, 15:05 UTCJul 7, 15:45 UTC40m
2026-07-07 VIV4201 - Jul 7, 01:35 UTCJul 7, 13:30 UTC11h 55m
2026-07-06 VIV2062 - Jul 6, 19:05 UTCJul 7, 00:10 UTC5h 5m
2026-07-06 VIV2061 - Jul 6, 16:55 UTCJul 6, 17:20 UTC25m
2026-07-06 VIV4202 - Jul 6, 13:35 UTCJul 6, 16:15 UTC2h 40m
2026-07-06 VIV2172 CUN → MTY Jul 6, 03:20 UTCJul 6, 05:25 UTC2h 5m
2026-07-05 VIV2124 CUN → CUN Jul 5, 23:05 UTCJul 6, 02:05 UTC3h 0m
2026-07-05 VIV2171 MTY → CUN Jul 5, 19:40 UTCJul 5, 21:35 UTC1h 55m
2026-07-05 VIV4037 - Jul 5, 15:15 UTCJul 5, 16:25 UTC1h 10m
2026-07-05 VIV4036 - Jul 5, 13:05 UTCJul 5, 13:30 UTC25m
2026-07-05 VIV705 MTY → MTY Jul 5, 04:25 UTCJul 5, 11:45 UTC7h 20m
2026-07-04 VIV701 MCO → MTY Jul 4, 21:40 UTCJul 5, 00:20 UTC2h 40m
2026-07-04 VIV700 MTY → MCO Jul 4, 15:15 UTCJul 4, 17:55 UTC2h 40m
2026-07-04 VIV8010 CJS → MTY Jul 4, 13:05 UTCJul 4, 13:45 UTC40m
2026-07-03 VIV8011 MTY → MTY Jul 3, 15:00 UTCJul 4, 13:45 UTC22h 45m
2026-07-03 VIV8010 CJS → MTY Jul 3, 13:10 UTCJul 3, 13:50 UTC40m
2026-07-03 VIV8015 - Jul 3, 04:05 UTCJul 3, 05:25 UTC1h 20m
2026-07-03 VIV8014 - Jul 3, 01:40 UTCJul 3, 03:15 UTC1h 35m
2026-07-02 VIV8013 - Jul 2, 23:40 UTCJul 3, 00:55 UTC1h 15m
2026-07-02 VIV8012 - Jul 2, 21:10 UTCJul 2, 22:35 UTC1h 25m
2026-07-02 VIV8016 - Jul 2, 12:10 UTCJul 2, 19:55 UTC7h 45m
2026-07-02 VIV8015 - Jul 2, 03:55 UTCJul 2, 05:20 UTC1h 25m
2026-07-02 VIV8014 - Jul 2, 01:40 UTCJul 2, 03:00 UTC1h 20m
2026-07-01 VIV8013 - Jul 1, 23:30 UTCJul 2, 00:50 UTC1h 20m
2026-07-01 VIV8012 CJS → MTY Jul 1, 21:05 UTCJul 1, 22:30 UTC1h 25m
2026-07-01 VIV7005 - Jul 1, 12:10 UTCJul 1, 20:00 UTC7h 50m
2026-07-01 VIV8025 - Jul 1, 02:35 UTCJul 1, 04:40 UTC2h 5m
2026-06-30 VIV8024 - Jun 30, 21:10 UTCJun 30, 22:15 UTC1h 5m
2026-06-30 VIV8005 - Jun 30, 16:35 UTCJun 30, 19:40 UTC3h 5m
2026-06-30 VIV8004 CJS → CUN Jun 30, 12:15 UTCJun 30, 15:15 UTC3h 0m
2026-06-30 VIV7435 - Jun 30, 04:20 UTCJun 30, 05:30 UTC1h 10m
2026-06-30 VIV7435 - Jun 30, 03:30 UTCJun 30, 03:40 UTC10m
2026-06-30 VIV7435 - Jun 30, 01:50 UTCJun 30, 02:35 UTC45m

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

Mode-S 0D103F frequently asked

What is Mode-S code 0D103F?
0D103F is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VDB.
Where is Mode-S 0D103F registered?
Mode-S code 0D103F is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D103F broadcasting right now?
No active broadcast right now. Last signal was 13h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D103F, octal 03210077, decimal 856,127.
What flights does 0D103F operate?
Mode-S 0D103F has broadcast 20 distinct callsigns, including VIV7435, VIV7434, VIV8005, VIV8004, VIV4044.