sensors Mode-S transponder
0D0932
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VLL · AIRBUS A-320
- Hex
- 0D0932
- Octal
- 03204462
- Decimal
- 854,322
- Country
- MX
- Tail
- XA-VLL
- Type
- A320
- Flights observed
- 112
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0932 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 |
|---|---|---|---|
| VOI713 | - | 6 | 2026-06-16 |
| VOI3519 | - | 5 | 2026-06-24 |
| VOI1102 | Volaris | 4 | 2026-05-25 |
| VOI712 | Volaris | 3 | 2026-06-15 |
| VOI7912 | Volaris | 2 | 2026-06-05 |
| VOI7908 | Volaris | 2 | 2026-06-05 |
| VOI7891 | - | 2 | 2026-06-21 |
| VOI7890 | - | 2 | 2026-06-20 |
| VOI7446 | Volaris | 2 | 2026-05-17 |
| VOI7417 | Volaris | 2 | 2026-05-25 |
| VOI7400 | Volaris | 2 | 2026-05-26 |
| VOI5043 | Volaris | 2 | 2026-06-08 |
| VOI3352 | - | 2 | 2026-06-23 |
| VOI325 | Volaris | 2 | 2026-06-12 |
| VOI3211 | - | 2 | 2026-06-20 |
| VOI1884 | - | 2 | 2026-05-21 |
| VOI1883 | Volaris | 2 | 2026-05-13 |
| VOI1882 | Volaris | 2 | 2026-05-13 |
| VOI185 | Volaris | 2 | 2026-06-10 |
| VOI143 | Volaris | 2 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-24 | VOI3518 | - | Jun 24, 23:14 UTC | Jun 25, 00:29 UTC | 1h 15m |
| 2026-06-24 | VOI3519 | - | Jun 24, 20:40 UTC | Jun 24, 22:19 UTC | 1h 40m |
| 2026-06-23 | VOI3519 | - | Jun 23, 23:14 UTC | Jun 24, 22:19 UTC | 23h 5m |
| 2026-06-23 | VOI3519 | - | Jun 23, 16:29 UTC | Jun 23, 22:15 UTC | 5h 45m |
| 2026-06-23 | VOI3352 | - | Jun 23, 01:20 UTC | Jun 23, 15:09 UTC | 13h 50m |
| 2026-06-22 | VOI3519 | - | Jun 22, 18:24 UTC | Jun 23, 00:09 UTC | 5h 45m |
| 2026-06-22 | VOI3352 | - | Jun 22, 16:10 UTC | Jun 22, 17:15 UTC | 1h 5m |
| 2026-06-21 | VOI7891 | - | Jun 21, 12:35 UTC | Jun 21, 15:40 UTC | 3h 5m |
| 2026-06-20 | VOI7890 | CUN → ORD | Jun 20, 23:19 UTC | Jun 21, 10:40 UTC | 11h 20m |
| 2026-06-20 | VOI3519 | - | Jun 20, 16:34 UTC | Jun 20, 22:25 UTC | 5h 50m |
| 2026-06-20 | VOI3211 | - | Jun 20, 09:24 UTC | Jun 20, 15:14 UTC | 5h 50m |
| 2026-06-19 | VOI3204 | - | Jun 19, 14:04 UTC | Jun 20, 02:40 UTC | 12h 35m |
| 2026-06-18 | VOI3265 | - | Jun 18, 23:20 UTC | Jun 19, 05:34 UTC | 6h 14m |
| 2026-06-18 | VOI3365 | - | Jun 18, 15:10 UTC | Jun 18, 22:00 UTC | 6h 50m |
| 2026-06-18 | VOI5610 | - | Jun 18, 03:40 UTC | Jun 18, 06:10 UTC | 2h 30m |
| 2026-06-18 | VOI5611 | - | Jun 18, 00:05 UTC | Jun 18, 02:25 UTC | 2h 20m |
| 2026-06-17 | VOI3221 | - | Jun 17, 19:50 UTC | Jun 17, 23:05 UTC | 3h 15m |
| 2026-06-17 | VOI3552 | CUN → PBC | Jun 17, 17:00 UTC | Jun 17, 18:40 UTC | 1h 40m |
| 2026-06-17 | VOI3553 | PBC → CUN | Jun 17, 14:00 UTC | Jun 17, 15:40 UTC | 1h 40m |
| 2026-06-17 | VOI3220 | - | Jun 17, 10:00 UTC | Jun 17, 13:10 UTC | 3h 10m |
| 2026-06-17 | VOI184 | - | Jun 17, 01:55 UTC | Jun 17, 05:05 UTC | 3h 10m |
| 2026-06-16 | VOI227 | - | Jun 16, 20:00 UTC | Jun 17, 00:40 UTC | 4h 40m |
| 2026-06-16 | VOI491 | AGU → TIJ | Jun 16, 16:45 UTC | Jun 16, 16:50 UTC | 5m |
| 2026-06-16 | VOI490 | TIJ → AGU | Jun 16, 12:14 UTC | Jun 16, 12:35 UTC | 20m |
| 2026-06-16 | VOI713 | AZP → MEX | Jun 16, 05:40 UTC | Jun 16, 05:50 UTC | 10m |
| 2026-06-16 | VOI713 | - | Jun 16, 02:34 UTC | Jun 16, 04:00 UTC | 1h 25m |
| 2026-06-15 | VOI7965 | LAX → TPQ | Jun 15, 18:10 UTC | Jun 16, 00:15 UTC | 6h 5m |
| 2026-06-15 | VOI712 | MEX → LAX | Jun 15, 12:30 UTC | Jun 15, 15:50 UTC | 3h 20m |
| 2026-06-15 | VOI713 | - | Jun 15, 05:45 UTC | Jun 15, 05:55 UTC | 10m |
| 2026-06-15 | VOI713 | - | Jun 15, 02:30 UTC | Jun 15, 04:00 UTC | 1h 30m |
| 2026-06-14 | VOI7854 | - | Jun 14, 17:40 UTC | Jun 15, 00:35 UTC | 6h 55m |
| 2026-06-14 | VOI712 | MEX → LAX | Jun 14, 12:20 UTC | Jun 14, 15:40 UTC | 3h 20m |
| 2026-06-14 | VOI713 | - | Jun 14, 06:00 UTC | Jun 14, 06:10 UTC | 10m |
| 2026-06-14 | VOI713 | - | Jun 14, 02:50 UTC | Jun 14, 04:20 UTC | 1h 30m |
| 2026-06-13 | VOI7855 | LAX → AGU | Jun 13, 18:00 UTC | Jun 14, 00:50 UTC | 6h 50m |
| 2026-06-13 | VOI712 | MEX → LAX | Jun 13, 12:25 UTC | Jun 13, 15:45 UTC | 3h 20m |
| 2026-06-13 | VOI431 | GDL → TIJ | Jun 13, 02:40 UTC | Jun 13, 06:15 UTC | 3h 34m |
| 2026-06-12 | VOI143 | GDL → MEX | Jun 12, 18:50 UTC | Jun 12, 21:40 UTC | 2h 50m |
| 2026-06-12 | VOI325 | MXL → MEX | Jun 12, 10:45 UTC | Jun 12, 10:50 UTC | 5m |
| 2026-06-12 | VOI325 | MXL → MEX | Jun 12, 08:10 UTC | Jun 12, 09:05 UTC | 55m |
| 2026-06-12 | VOI324 | MEX → MXL | Jun 12, 04:00 UTC | Jun 12, 06:35 UTC | 2h 35m |
| 2026-06-11 | VOI731 | IAH → MEX | Jun 11, 02:05 UTC | Jun 11, 03:50 UTC | 1h 45m |
| 2026-06-10 | VOI730 | MEX → IAH | Jun 10, 22:20 UTC | Jun 11, 00:10 UTC | 1h 50m |
| 2026-06-10 | VOI281 | PVR → MEX | Jun 10, 17:15 UTC | Jun 10, 20:35 UTC | 3h 20m |
| 2026-06-10 | VOI481 | CTM → MEX | Jun 10, 11:30 UTC | Jun 10, 15:55 UTC | 4h 25m |
| 2026-06-10 | VOI185 | TIJ → MEX | Jun 10, 09:40 UTC | Jun 10, 09:45 UTC | 5m |
| 2026-06-10 | VOI185 | TIJ → MEX | Jun 10, 06:50 UTC | Jun 10, 07:55 UTC | 1h 5m |
| 2026-06-10 | VOI3295 | CUU → TIJ | Jun 10, 01:20 UTC | Jun 10, 05:30 UTC | 4h 10m |
| 2026-06-09 | VOI3232 | TIJ → LAP | Jun 9, 19:20 UTC | Jun 9, 23:30 UTC | 4h 10m |
| 2026-06-09 | VOI3281 | CJS → TIJ | Jun 9, 14:35 UTC | Jun 9, 15:50 UTC | 1h 15m |
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-VLL page for operator, model, and routing details .