sensors Mode-S transponder

0D0D2B

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VBI · AIRBUS A-321

Hex
0D0D2B
Octal
03206453
Decimal
855,339
Country
MX
Tail
XA-VBI
Type
A321
Broadcasting now · callsign VIV1229 · 36,000 ft
Flights observed
293
Distinct callsigns
20
Country
MX
Last broadcast
4h ago

Current position

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

Country allocation

The ICAO 24-bit address 0D0D2B 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
VIV7416 VivaAerobus 7 2026-05-28
VIV1029 - 7 2026-07-13
VIV1213 - 5 2026-06-15
VIV1189 - 5 2026-06-16
VIV1183 - 5 2026-07-06
VIV1105 - 5 2026-07-13
VIV7443 - 4 2026-06-14
VIV7350 VivaAerobus 4 2026-05-03
VIV4387 VivaAerobus 4 2026-05-05
VIV4036 - 4 2026-06-27
VIV3677 - 4 2026-05-31
VIV1399 - 4 2026-06-15
VIV1355 VivaAerobus 4 2026-05-19
VIV1268 VivaAerobus 4 2026-06-13
VIV1050 - 4 2026-07-14
VIV9244 VivaAerobus 3 2026-04-18
VIV9221 VivaAerobus 3 2026-05-30
VIV7432 VivaAerobus 3 2026-07-02
VIV7383 VivaAerobus 3 2026-06-01
VIV7190 VivaAerobus 3 2026-04-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 VIV165 - Jul 14, 23:35 UTCJul 15, 01:15 UTC1h 40m
2026-07-14 VIV153 - Jul 14, 16:45 UTCJul 14, 18:30 UTC1h 45m
2026-07-14 VIV1051 AZP → MEX Jul 14, 06:15 UTCJul 14, 06:25 UTC10m
2026-07-14 VIV1050 - Jul 14, 01:20 UTCJul 14, 05:25 UTC4h 5m
2026-07-13 VIV1105 - Jul 13, 20:00 UTCJul 13, 23:30 UTC3h 30m
2026-07-13 VIV1029 CUN → MEX Jul 13, 15:40 UTCJul 13, 17:25 UTC1h 45m
2026-07-13 VIV1028 - Jul 13, 12:25 UTCJul 13, 14:15 UTC1h 50m
2026-07-12 VIV2184 - Jul 12, 19:05 UTCJul 13, 05:05 UTC10h 0m
2026-07-12 VIV4310 MTY → CUN Jul 12, 12:25 UTCJul 12, 17:35 UTC5h 10m
2026-07-12 VIV2180 CUN → MTY Jul 12, 04:15 UTCJul 12, 06:15 UTC2h 0m
2026-07-11 VIV4190 MTY → CUN Jul 11, 19:05 UTCJul 12, 03:10 UTC8h 5m
2026-07-11 VIV4213 - Jul 11, 15:50 UTCJul 11, 17:50 UTC2h 0m
2026-07-11 VIV4212 MTY → TQO Jul 11, 12:40 UTCJul 11, 14:40 UTC2h 0m
2026-07-10 VIV511 - Jul 10, 19:10 UTCJul 10, 20:30 UTC1h 20m
2026-07-10 VIV519 - Jul 10, 08:00 UTCJul 10, 09:25 UTC1h 25m
2026-07-09 VIV533 - Jul 9, 21:15 UTCJul 9, 22:40 UTC1h 25m
2026-07-09 VIV532 - Jul 9, 14:25 UTCJul 9, 19:25 UTC5h 0m
2026-07-09 VIV1057 - Jul 9, 06:00 UTCJul 9, 13:10 UTC7h 10m
2026-07-09 VIV1069 - Jul 9, 04:25 UTCJul 9, 04:40 UTC15m
2026-07-09 VIV1066 - Jul 9, 01:45 UTCJul 9, 01:55 UTC10m
2026-07-09 VIV1065 - Jul 9, 00:00 UTCJul 9, 00:05 UTC5m
2026-07-08 VIV3207 - Jul 8, 20:15 UTCJul 8, 20:40 UTC25m
2026-07-08 VIV4325 MTY → MTY Jul 8, 00:45 UTCJul 8, 17:10 UTC16h 25m
2026-07-07 VIV0683 DFW → MTY Jul 7, 22:10 UTCJul 7, 23:30 UTC1h 20m
2026-07-07 VIV4162 MTY → VER Jul 7, 12:25 UTCJul 7, 13:40 UTC1h 15m
2026-07-07 VIV4074 - Jul 7, 01:00 UTCJul 7, 02:15 UTC1h 15m
2026-07-06 VIV1183 - Jul 6, 20:25 UTCJul 6, 21:00 UTC35m
2026-07-06 VIV1182 - Jul 6, 18:25 UTCJul 6, 18:55 UTC30m
2026-07-06 VIV1100 - Jul 6, 13:10 UTCJul 6, 17:05 UTC3h 55m
2026-07-06 VIV1021 CUN → MEX Jul 6, 05:20 UTCJul 6, 07:10 UTC1h 50m
2026-07-05 VIV1183 - Jul 5, 23:35 UTCJul 6, 00:25 UTC50m
2026-07-05 VIV1183 - Jul 5, 20:25 UTCJul 5, 22:00 UTC1h 35m
2026-07-05 VIV1101 - Jul 5, 16:00 UTCJul 5, 16:50 UTC50m
2026-07-05 VIV1051 - Jul 5, 05:45 UTCJul 5, 05:55 UTC10m
2026-07-04 VIV2184 - Jul 4, 18:40 UTCJul 5, 05:00 UTC10h 20m
2026-07-04 VB4310 MTY → CUN Jul 4, 12:20 UTCJul 4, 17:15 UTC4h 55m
2026-07-03 VIV2194 CUN → MTY Jul 3, 22:05 UTCJul 4, 00:15 UTC2h 10m
2026-07-03 VIV2193 MTY → CUN Jul 3, 18:20 UTCJul 3, 20:25 UTC2h 5m
2026-07-03 VIV4087 - Jul 3, 04:30 UTCJul 3, 06:50 UTC2h 20m
2026-07-02 VIV7432 TIJ → GDL Jul 2, 13:00 UTCJul 2, 18:20 UTC5h 20m
2026-07-02 VIV7371 - Jul 2, 04:25 UTCJul 2, 05:20 UTC55m
2026-07-01 VIV992 - Jul 1, 08:50 UTCJul 2, 05:20 UTC20h 30m
2026-07-01 VIV0991 - Jul 1, 04:35 UTCJul 1, 06:20 UTC1h 45m
2026-06-30 VIV7379 - Jun 30, 19:40 UTCJun 30, 20:40 UTC1h 0m
2026-06-30 VIV7378 - Jun 30, 14:55 UTCJun 30, 15:20 UTC25m
2026-06-30 VIV5068 - Jun 30, 08:25 UTCJun 30, 09:35 UTC1h 10m
2026-06-29 VIV7026 - Jun 29, 16:00 UTCJun 29, 22:44 UTC6h 45m
2026-06-29 VIV5009 - Jun 29, 05:15 UTCJun 29, 06:19 UTC1h 5m
2026-06-28 VIV1253 - Jun 28, 19:34 UTCJun 28, 19:49 UTC15m
2026-06-28 VIV1253 - Jun 28, 16:49 UTCJun 28, 17:55 UTC1h 5m

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

Mode-S 0D0D2B frequently asked

What is Mode-S code 0D0D2B?
0D0D2B is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VBI.
Where is Mode-S 0D0D2B registered?
Mode-S code 0D0D2B is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0D2B broadcasting right now?
Yes. Mode-S 0D0D2B is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0D2B, octal 03206453, decimal 855,339.
What flights does 0D0D2B operate?
Mode-S 0D0D2B has broadcast 20 distinct callsigns, including VIV7416, VIV1029, VIV1213, VIV1189, VIV1183.