sensors Mode-S transponder

0D112A

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VXU · AIRBUS A-321neo

Hex
0D112A
Octal
03210452
Decimal
856,362
Country
MX
Tail
XA-VXU
Type
A21N
Broadcasting now · callsign VIV4284 · 30,725 ft
Flights observed
469
Distinct callsigns
20
Country
MX
Last broadcast
2h ago

Current position

0D112A is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 0D112A 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
VIV7061 VivaAerobus 14 2026-06-09
VIV7060 VivaAerobus 11 2026-06-08
VIV1380 VivaAerobus 11 2026-06-11
VIV1379 VivaAerobus 11 2026-06-11
VIV2198 VivaAerobus 9 2026-06-10
VIV1373 VivaAerobus 9 2026-06-11
VIV1249 - 9 2026-06-29
VIV7443 VivaAerobus 8 2026-05-06
VIV2199 VivaAerobus 8 2026-06-10
VIV2197 VivaAerobus 8 2026-06-08
VIV2196 VivaAerobus 8 2026-06-08
VIV1248 - 8 2026-06-30
VIV113 - 8 2026-06-16
VIV1374 - 7 2026-06-16
VIV1127 - 7 2026-06-30
VIV7442 VivaAerobus 6 2026-05-05
VIV1105 - 6 2026-06-12
VIV7379 - 5 2026-07-12
VIV7067 - 5 2026-05-25
VIV7066 VivaAerobus 5 2026-05-24

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 VIV4204 - Jul 14, 15:45 UTCJul 14, 18:30 UTC2h 45m
2026-07-14 VIV1118 - Jul 14, 13:30 UTCJul 14, 14:40 UTC1h 10m
2026-07-14 VIV1117 MTY → MEX Jul 14, 11:10 UTCJul 14, 12:15 UTC1h 5m
2026-07-13 VIV4319 - Jul 13, 23:20 UTCJul 14, 05:55 UTC6h 35m
2026-07-13 VIV9395 - Jul 13, 21:05 UTCJul 13, 21:20 UTC15m
2026-07-13 VIV9394 - Jul 13, 19:05 UTCJul 13, 19:50 UTC45m
2026-07-13 VIV2278 - Jul 13, 15:45 UTCJul 13, 17:25 UTC1h 40m
2026-07-13 VIV2281 - Jul 13, 12:40 UTCJul 13, 14:30 UTC1h 50m
2026-07-13 VIV9500 - Jul 13, 02:40 UTCJul 13, 03:01 UTC20m
2026-07-12 VIV9234 - Jul 12, 22:00 UTCJul 12, 22:15 UTC15m
2026-07-12 VIV7379 - Jul 12, 19:20 UTCJul 12, 20:20 UTC1h 0m
2026-07-12 VIV7378 MTY → MTY Jul 12, 14:20 UTCJul 12, 18:15 UTC3h 55m
2026-07-12 VIV7378 - Jul 12, 12:05 UTCJul 12, 13:15 UTC1h 10m
2026-07-12 VIV5070 - Jul 12, 03:30 UTCJul 12, 04:40 UTC1h 10m
2026-07-11 VIV7371 - Jul 11, 21:55 UTCJul 12, 02:05 UTC4h 10m
2026-07-11 VIV7370 - Jul 11, 16:15 UTCJul 11, 17:25 UTC1h 10m
2026-07-11 VIV5069 - Jul 11, 12:30 UTCJul 11, 15:15 UTC2h 45m
2026-07-11 VIV5070 - Jul 11, 03:30 UTCJul 11, 04:35 UTC1h 5m
2026-07-10 VIV7371 - Jul 10, 22:10 UTCJul 11, 02:20 UTC4h 10m
2026-07-10 VIV7370 - Jul 10, 16:55 UTCJul 10, 18:00 UTC1h 5m
2026-07-10 VIV5069 - Jul 10, 14:35 UTCJul 10, 15:50 UTC1h 15m
2026-07-10 VIV5069 - Jul 10, 12:55 UTCJul 10, 13:10 UTC15m
2026-07-10 VIV5070 - Jul 10, 03:40 UTCJul 10, 04:55 UTC1h 15m
2026-07-09 VIV7371 - Jul 9, 22:15 UTCJul 10, 02:25 UTC4h 10m
2026-07-09 VIV7370 - Jul 9, 16:35 UTCJul 9, 17:40 UTC1h 5m
2026-07-09 VIV5069 - Jul 9, 14:10 UTCJul 9, 15:15 UTC1h 5m
2026-07-09 VIV5069 - Jul 9, 12:25 UTCJul 9, 12:35 UTC10m
2026-07-09 VIV5068 - Jul 9, 08:05 UTCJul 9, 09:15 UTC1h 10m
2026-07-09 VIV5067 - Jul 9, 05:55 UTCJul 9, 07:00 UTC1h 5m
2026-07-09 VIV5067 - Jul 9, 04:05 UTCJul 9, 04:20 UTC15m
2026-07-08 VIV3195 - Jul 8, 23:25 UTCJul 9, 02:40 UTC3h 15m
2026-07-08 VIV3206 MTY → MTY Jul 8, 15:45 UTCJul 8, 19:10 UTC3h 25m
2026-07-08 VIV4311 MTY → MTY Jul 8, 04:25 UTCJul 8, 13:30 UTC9h 5m
2026-07-08 VIV4289 - Jul 8, 02:20 UTCJul 8, 03:15 UTC55m
2026-07-07 VIV755 - Jul 7, 21:55 UTCJul 7, 23:25 UTC1h 30m
2026-07-07 VIV754 - Jul 7, 18:30 UTCJul 7, 19:45 UTC1h 15m
2026-07-07 VIV9245 - Jul 7, 15:05 UTCJul 7, 15:55 UTC50m
2026-07-07 VIV9266 - Jul 7, 02:25 UTCJul 7, 13:55 UTC11h 30m
2026-07-06 VIV9021 - Jul 6, 20:05 UTCJul 6, 20:35 UTC30m
2026-07-06 VIV4282 MTY → VER Jul 6, 15:00 UTCJul 6, 18:55 UTC3h 55m
2026-07-06 VIV4290 MTY → MTY Jul 6, 05:25 UTCJul 6, 13:50 UTC8h 25m
2026-07-05 VIV6017 - Jul 5, 19:50 UTCJul 6, 04:20 UTC8h 30m
2026-07-05 VIV9313 - Jul 5, 16:55 UTCJul 5, 17:25 UTC30m
2026-07-05 VIV9312 - Jul 5, 15:15 UTCJul 5, 15:35 UTC20m
2026-07-05 VIV6016 - Jul 5, 04:55 UTCJul 5, 13:35 UTC8h 40m
2026-07-04 VIV9234 - Jul 4, 21:50 UTCJul 4, 22:10 UTC20m
2026-07-04 VIV7379 - Jul 4, 19:35 UTCJul 4, 20:35 UTC1h 0m
2026-07-04 VIV7379 MTY → MTY Jul 4, 14:40 UTCJul 4, 18:30 UTC3h 50m
2026-07-04 VIV7378 - Jul 4, 12:40 UTCJul 4, 13:45 UTC1h 5m
2026-07-04 VIV9500 - Jul 4, 02:30 UTCJul 4, 02:45 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-VXU page for operator, model, and routing details .

Mode-S 0D112A frequently asked

What is Mode-S code 0D112A?
0D112A is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VXU.
Where is Mode-S 0D112A registered?
Mode-S code 0D112A is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D112A broadcasting right now?
Yes. Mode-S 0D112A is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D112A, octal 03210452, decimal 856,362.
What flights does 0D112A operate?
Mode-S 0D112A has broadcast 20 distinct callsigns, including VIV7061, VIV7060, VIV1380, VIV1379, VIV2198.