sensors Mode-S transponder

0D1068

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VDE · AIRBUS A-320

Hex
0D1068
Octal
03210150
Decimal
856,168
Country
MX
Tail
XA-VDE
Type
A320
Transponder active on ground
Flights observed
394
Distinct callsigns
20
Country
MX
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 0D1068.

Country allocation

The ICAO 24-bit address 0D1068 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
VIV7033 - 14 2026-07-12
VIV7032 - 14 2026-07-11
VIV4042 - 14 2026-07-13
VIV2015 - 14 2026-07-11
VIV4043 VivaAerobus 12 2026-06-12
VIV4044 VivaAerobus 11 2026-06-09
VIV4041 - 11 2026-07-13
VIV8012 - 9 2026-06-29
VIV2022 - 9 2026-07-12
VIV8011 - 8 2026-06-28
VIV7435 VivaAerobus 8 2026-05-20
VIV8010 VivaAerobus 7 2026-06-28
VIV7434 VivaAerobus 7 2026-05-18
VIV8013 - 6 2026-06-26
VIV7812 - 6 2026-07-03
VIV8014 - 5 2026-06-27
VIV1355 VivaAerobus 5 2026-05-21
VIV9145 VivaAerobus 4 2026-06-12
VIV8027 - 4 2026-06-23
VIV8019 - 4 2026-06-28

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 VIV4081 - Jul 14, 16:45 UTCJul 14, 19:10 UTC2h 25m
2026-07-14 VIV4080 - Jul 14, 12:45 UTCJul 14, 15:05 UTC2h 20m
2026-07-14 VIV4047 - Jul 14, 03:35 UTCJul 14, 04:40 UTC1h 5m
2026-07-13 VIV9348 - Jul 13, 21:10 UTCJul 13, 21:20 UTC10m
2026-07-13 VIV4042 - Jul 13, 14:35 UTCJul 13, 15:00 UTC25m
2026-07-13 VIV4041 - Jul 13, 12:10 UTCJul 13, 13:25 UTC1h 15m
2026-07-13 VIV4048 - Jul 13, 04:10 UTCJul 13, 04:55 UTC45m
2026-07-13 VIV4047 - Jul 13, 02:01 UTCJul 13, 03:15 UTC1h 15m
2026-07-12 VIV9348 - Jul 12, 21:10 UTCJul 12, 21:20 UTC10m
2026-07-12 VIV4042 - Jul 12, 15:01 UTCJul 12, 15:25 UTC25m
2026-07-12 VIV4041 - Jul 12, 12:05 UTCJul 12, 13:15 UTC1h 10m
2026-07-12 VIV2022 - Jul 12, 03:15 UTCJul 12, 05:01 UTC1h 46m
2026-07-12 VIV7033 - Jul 12, 00:01 UTCJul 12, 01:50 UTC1h 50m
2026-07-11 VIV7032 - Jul 11, 15:55 UTCJul 11, 17:40 UTC1h 45m
2026-07-11 VIV2015 - Jul 11, 12:15 UTCJul 11, 14:05 UTC1h 50m
2026-07-11 VIV2022 - Jul 11, 03:45 UTCJul 11, 05:31 UTC1h 45m
2026-07-10 VIV7033 - Jul 10, 23:50 UTCJul 11, 01:40 UTC1h 50m
2026-07-10 VIV7032 - Jul 10, 15:35 UTCJul 10, 17:20 UTC1h 45m
2026-07-10 VIV2015 - Jul 10, 12:20 UTCJul 10, 14:00 UTC1h 40m
2026-07-10 VIV2022 - Jul 10, 03:30 UTCJul 10, 05:15 UTC1h 45m
2026-07-10 VIV7033 - Jul 10, 00:10 UTCJul 10, 02:00 UTC1h 50m
2026-07-09 VIV7032 - Jul 9, 15:35 UTCJul 9, 17:20 UTC1h 45m
2026-07-09 VIV2015 - Jul 9, 12:10 UTCJul 9, 14:05 UTC1h 55m
2026-07-09 VIV2022 - Jul 9, 03:50 UTCJul 9, 05:40 UTC1h 50m
2026-07-09 VIV7033 - Jul 9, 00:05 UTCJul 9, 01:55 UTC1h 50m
2026-07-08 VIV7032 - Jul 8, 15:40 UTCJul 8, 17:25 UTC1h 45m
2026-07-08 VIV2015 - Jul 8, 12:15 UTCJul 8, 14:05 UTC1h 50m
2026-07-08 VIV2022 - Jul 8, 03:25 UTCJul 8, 05:20 UTC1h 55m
2026-07-08 VIV7033 TLC → CUN Jul 8, 00:00 UTCJul 8, 01:55 UTC1h 55m
2026-07-07 VIV7032 - Jul 7, 18:35 UTCJul 7, 18:45 UTC10m
2026-07-07 VIV7032 - Jul 7, 15:35 UTCJul 7, 17:20 UTC1h 45m
2026-07-07 VIV2015 - Jul 7, 12:10 UTCJul 7, 13:55 UTC1h 45m
2026-07-07 VIV2022 - Jul 7, 03:15 UTCJul 7, 05:05 UTC1h 50m
2026-07-07 VIV7033 TLC → CUN Jul 7, 00:05 UTCJul 7, 01:55 UTC1h 50m
2026-07-06 VIV7032 - Jul 6, 15:35 UTCJul 6, 17:20 UTC1h 45m
2026-07-06 VIV2015 - Jul 6, 12:15 UTCJul 6, 14:00 UTC1h 45m
2026-07-06 VIV2022 - Jul 6, 03:30 UTCJul 6, 05:15 UTC1h 45m
2026-07-06 VIV7033 TLC → CUN Jul 6, 00:05 UTCJul 6, 01:45 UTC1h 40m
2026-07-05 VIV7032 - Jul 5, 19:05 UTCJul 5, 19:15 UTC10m
2026-07-05 VIV7032 - Jul 5, 15:45 UTCJul 5, 18:00 UTC2h 15m
2026-07-05 VIV2015 - Jul 5, 12:15 UTCJul 5, 14:00 UTC1h 45m
2026-07-05 VIV4048 MTY → TLC Jul 5, 03:55 UTCJul 5, 04:15 UTC20m
2026-07-05 VIV4047 - Jul 5, 01:50 UTCJul 5, 03:00 UTC1h 10m
2026-07-04 VIV9348 - Jul 4, 21:05 UTCJul 4, 21:20 UTC15m
2026-07-04 VIV9144 - Jul 4, 16:50 UTCJul 4, 17:00 UTC10m
2026-07-04 VIV4042 - Jul 4, 14:40 UTCJul 4, 15:05 UTC25m
2026-07-04 VIV7017 - Jul 4, 04:05 UTCJul 4, 05:00 UTC55m
2026-07-04 VIV7017 - Jul 4, 02:15 UTCJul 4, 02:50 UTC35m
2026-07-04 VIV7016 - Jul 4, 00:40 UTCJul 4, 01:05 UTC25m
2026-07-03 VIV7016 - Jul 3, 22:30 UTCJul 3, 23:30 UTC1h 0m

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

Mode-S 0D1068 frequently asked

What is Mode-S code 0D1068?
0D1068 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VDE.
Where is Mode-S 0D1068 registered?
Mode-S code 0D1068 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D1068 broadcasting right now?
Mode-S 0D1068 is currently broadcasting from the ground.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D1068, octal 03210150, decimal 856,168.
What flights does 0D1068 operate?
Mode-S 0D1068 has broadcast 20 distinct callsigns, including VIV7033, VIV7032, VIV4042, VIV2015, VIV4043.