sensors Mode-S transponder
0D0DA8
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VSF · AIRBUS A-320neo
- Hex
- 0D0DA8
- Octal
- 03206650
- Decimal
- 855,464
- Country
- MX
- Tail
- XA-VSF
- Type
- A20N
- Flights observed
- 131
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0DA8 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 |
|---|---|---|---|
| VOI3930 | - | 5 | 2026-04-17 |
| VOI1903 | Volaris | 5 | 2026-05-19 |
| VOI1902 | Volaris | 5 | 2026-05-18 |
| VOI7842 | Volaris | 4 | 2026-04-28 |
| VOI3931 | - | 4 | 2026-04-17 |
| VOI3591 | Volaris | 4 | 2026-05-25 |
| VOI3588 | Volaris | 4 | 2026-04-17 |
| VOI3223 | Volaris | 4 | 2026-04-16 |
| VOI7843 | Volaris | 3 | 2026-04-28 |
| VOI7831 | Volaris | 3 | 2026-05-28 |
| VOI3555 | - | 3 | 2026-04-15 |
| VOI1270 | Volaris | 3 | 2026-05-16 |
| VOI7830 | Volaris | 2 | 2026-05-28 |
| VOI3554 | Volaris | 2 | 2026-04-15 |
| VOI3519 | Volaris | 2 | 2026-05-29 |
| VOI3377 | Volaris | 2 | 2026-04-18 |
| VOI3376 | Volaris | 2 | 2026-04-16 |
| VOI3204 | Volaris | 2 | 2026-04-14 |
| VOI3045 | Volaris | 2 | 2026-04-26 |
| VOI1841 | Volaris | 2 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | VOI3518 | CUN → QRO | May 29, 23:30 UTC | May 30, 01:05 UTC | 1h 35m |
| 2026-05-29 | VOI3519 | QRO → CUN | May 29, 16:30 UTC | May 29, 22:20 UTC | 5h 50m |
| 2026-05-28 | VOI7831 | MDW → ZCL | May 28, 20:05 UTC | May 29, 15:20 UTC | 19h 15m |
| 2026-05-28 | VOI7831 | MDW → ZCL | May 28, 19:30 UTC | May 29, 15:20 UTC | 19h 50m |
| 2026-05-28 | VOI7830 | ZCL → MDW | May 28, 08:40 UTC | May 28, 17:50 UTC | 9h 10m |
| 2026-05-28 | VOI7840 | ZCL → LAX | May 28, 04:40 UTC | May 28, 05:55 UTC | 1h 15m |
| 2026-05-26 | VOI7831 | MDW → ZCL | May 26, 19:30 UTC | May 26, 22:44 UTC | 3h 15m |
| 2026-05-26 | VOI7830 | ZCL → MDW | May 26, 09:25 UTC | May 26, 17:35 UTC | 8h 10m |
| 2026-05-26 | VOI3323 | TLC → TIJ | May 26, 01:24 UTC | May 26, 02:19 UTC | 55m |
| 2026-05-25 | VOI3480 | CUN → TLC | May 25, 16:10 UTC | May 25, 18:00 UTC | 1h 50m |
| 2026-05-25 | VOI3591 | SLP → CUN | May 25, 09:05 UTC | May 25, 15:10 UTC | 6h 5m |
| 2026-05-24 | VOI5265 | CLQ → TIJ | May 24, 23:20 UTC | May 25, 05:30 UTC | 6h 10m |
| 2026-05-24 | VOI182 | MEX → TIJ | May 24, 18:50 UTC | May 24, 21:45 UTC | 2h 55m |
| 2026-05-24 | VOI3919 | LIM → MEX | May 24, 11:35 UTC | May 24, 17:05 UTC | 5h 30m |
| 2026-05-24 | VOI3918 | MEX → LIM | May 24, 04:30 UTC | May 24, 09:35 UTC | 5h 5m |
| 2026-05-23 | VOI751 | MXL → MEX | May 23, 02:40 UTC | May 23, 04:25 UTC | 1h 45m |
| 2026-05-22 | VOI1752 | GDL → SAT | May 22, 21:15 UTC | May 23, 01:05 UTC | 3h 50m |
| 2026-05-22 | VOI1233 | MID → GDL | May 22, 02:55 UTC | May 22, 20:10 UTC | 17h 15m |
| 2026-05-21 | VOI1716 | GDL → LAX | May 21, 15:15 UTC | May 22, 01:00 UTC | 9h 45m |
| 2026-05-21 | VOI1161 | CJS → GDL | May 21, 04:35 UTC | May 21, 14:10 UTC | 9h 35m |
| 2026-05-21 | VOI1160 | GDL → CJS | May 21, 03:05 UTC | May 21, 03:35 UTC | 30m |
| 2026-05-19 | VOI1903 | EWR → GDL | May 19, 10:45 UTC | May 19, 14:55 UTC | 4h 10m |
| 2026-05-18 | VOI1902 | GDL → EWR | May 18, 21:00 UTC | May 19, 08:30 UTC | 11h 30m |
| 2026-05-18 | VOI1841 | MDW → GDL | May 18, 01:35 UTC | May 18, 20:00 UTC | 18h 24m |
| 2026-05-17 | VOI1903 | EWR → GDL | May 17, 10:35 UTC | May 18, 00:05 UTC | 13h 30m |
| 2026-05-16 | VOI1902 | GDL → EWR | May 16, 21:20 UTC | May 17, 08:40 UTC | 11h 20m |
| 2026-05-16 | VOI1270 | GDL → TGZ | May 16, 02:05 UTC | May 16, 20:20 UTC | 18h 16m |
| 2026-05-16 | VOI1823 | SJC → GDL | May 16, 00:25 UTC | May 16, 20:20 UTC | 19h 56m |
| 2026-05-15 | VOI1903 | EWR → GDL | May 15, 10:40 UTC | May 15, 22:15 UTC | 11h 34m |
| 2026-05-14 | VOI1902 | GDL → EWR | May 14, 19:05 UTC | May 15, 09:10 UTC | 14h 5m |
| 2026-05-14 | VOI1760 | GDL → DEN | May 14, 15:25 UTC | May 14, 17:10 UTC | 1h 45m |
| 2026-05-13 | VOI1903 | EWR → GDL | May 13, 10:35 UTC | May 13, 14:51 UTC | 4h 15m |
| 2026-05-12 | VOI1902 | GDL → EWR | May 12, 14:30 UTC | May 13, 08:45 UTC | 18h 15m |
| 2026-05-12 | VOI1080 | GDL → MTY | May 12, 12:50 UTC | May 12, 13:35 UTC | 45m |
| 2026-05-11 | VOI1270 | GDL → TGZ | May 11, 16:50 UTC | May 12, 13:35 UTC | 20h 46m |
| 2026-05-11 | VOI1270 | GDL → TGZ | May 11, 12:40 UTC | May 11, 17:45 UTC | 5h 5m |
| 2026-05-10 | VOI1883 | PHX → GDL | May 10, 16:50 UTC | May 10, 17:25 UTC | 35m |
| 2026-05-10 | VOI5803 | EWR → GDL | May 10, 02:24 UTC | May 10, 14:45 UTC | 12h 20m |
| 2026-05-09 | VOI1903 | EWR → GDL | May 9, 10:45 UTC | May 10, 00:09 UTC | 13h 25m |
| 2026-05-08 | VOI1902 | GDL → EWR | May 8, 19:05 UTC | May 9, 08:25 UTC | 13h 20m |
| 2026-05-08 | VOI1704 | GDL → ORD | May 8, 04:34 UTC | May 8, 16:55 UTC | 12h 20m |
| 2026-05-07 | VOI1816 | GDL → SMF | May 7, 17:00 UTC | May 8, 02:44 UTC | 9h 44m |
| 2026-05-07 | VOI1841 | MDW → GDL | May 7, 01:35 UTC | May 7, 14:35 UTC | 13h 0m |
| 2026-05-06 | VOI1840 | GDL → MDW | May 6, 20:45 UTC | May 6, 23:30 UTC | 2h 45m |
| 2026-05-06 | VOI1840 | GDL → MDW | May 6, 02:55 UTC | May 6, 23:30 UTC | 20h 34m |
| 2026-05-05 | VOI3967 | BOG → GDL | May 5, 21:40 UTC | May 6, 01:35 UTC | 3h 55m |
| 2026-05-05 | VOI3966 | GDL → BOG | May 5, 02:05 UTC | May 5, 21:05 UTC | 19h 0m |
| 2026-05-05 | VOI1823 | SJC → GDL | May 5, 00:20 UTC | May 5, 21:05 UTC | 20h 45m |
| 2026-05-04 | VOI5811 | ORD → GDL | May 4, 07:50 UTC | May 4, 21:55 UTC | 14h 6m |
| 2026-05-03 | VOI5810 | TIJ → MEX | May 3, 21:35 UTC | May 4, 05:55 UTC | 8h 20m |
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-VSF page for operator, model, and routing details .