sensors Mode-S transponder
0D0A26
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VRA · AIRBUS A-320
- Hex
- 0D0A26
- Octal
- 03205046
- Decimal
- 854,566
- Country
- MX
- Tail
- XA-VRA
- Type
- A320
- Flights observed
- 270
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- Jul 26, 14:05 UTC
Last known position
Country allocation
The ICAO 24-bit address 0D0A26 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 |
|---|---|---|---|
| VOI7730 | Volaris | 7 | 2026-04-18 |
| VOI901 | Volaris | 4 | 2026-04-28 |
| VOI3259 | - | 4 | 2026-07-03 |
| VOI1770 | Volaris | 4 | 2026-07-24 |
| VOI7945 | Volaris | 3 | 2026-05-25 |
| VOI7944 | Volaris | 3 | 2026-04-13 |
| VOI7885 | - | 3 | 2026-07-23 |
| VOI7884 | - | 3 | 2026-07-23 |
| VOI7821 | Volaris | 3 | 2026-05-24 |
| VOI7820 | Volaris | 3 | 2026-05-23 |
| VOI7761 | - | 3 | 2026-07-08 |
| VOI7731 | Volaris | 3 | 2026-04-18 |
| VOI370 | - | 3 | 2026-07-01 |
| VOI3503 | - | 3 | 2026-07-10 |
| VOI3291 | - | 3 | 2026-06-21 |
| VOI3269 | - | 3 | 2026-07-01 |
| VOI3232 | - | 3 | 2026-06-23 |
| VOI3122 | Volaris | 3 | 2026-05-26 |
| VOI1811 | Volaris | 3 | 2026-07-20 |
| VOI1810 | Volaris | 3 | 2026-07-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VOI1183 | HMO → GDL | Jul 26, 04:05 UTC | Jul 26, 14:05 UTC | 10h 1m |
| 2026-07-26 | VOI1182 | GDL → HMO | Jul 26, 02:55 UTC | Jul 26, 03:10 UTC | 15m |
| 2026-07-25 | VOI1751 | SAT → GDL | Jul 25, 16:30 UTC | Jul 25, 23:40 UTC | 7h 10m |
| 2026-07-25 | VOI1771 | OAK → GDL | Jul 25, 03:20 UTC | Jul 25, 15:00 UTC | 11h 40m |
| 2026-07-24 | VOI1770 | GDL → OAK | Jul 24, 23:10 UTC | Jul 25, 01:05 UTC | 1h 55m |
| 2026-07-24 | VOI1770 | GDL → OAK | Jul 24, 03:35 UTC | Jul 25, 01:05 UTC | 21h 30m |
| 2026-07-23 | VOI7885 | - | Jul 23, 19:00 UTC | Jul 24, 02:20 UTC | 7h 20m |
| 2026-07-23 | VOI7884 | - | Jul 23, 16:10 UTC | Jul 23, 17:05 UTC | 55m |
| 2026-07-22 | VOI1891 | RNO → GDL | Jul 22, 19:40 UTC | Jul 22, 21:25 UTC | 1h 45m |
| 2026-07-22 | VOI1890 | GDL → RNO | Jul 22, 03:25 UTC | Jul 22, 17:25 UTC | 14h 0m |
| 2026-07-21 | VOI1761 | DEN → GDL | Jul 21, 19:05 UTC | Jul 22, 02:05 UTC | 7h 0m |
| 2026-07-21 | VOI1760 | GDL → DEN | Jul 21, 08:30 UTC | Jul 21, 17:00 UTC | 8h 30m |
| 2026-07-21 | VOI1812 | GDL → SMF | Jul 21, 04:40 UTC | Jul 21, 06:40 UTC | 2h 0m |
| 2026-07-20 | VOI1812 | GDL → SMF | Jul 20, 07:35 UTC | Jul 21, 06:40 UTC | 23h 4m |
| 2026-07-20 | VOI1811 | SMF → GDL | Jul 20, 06:45 UTC | Jul 21, 05:30 UTC | 22h 44m |
| 2026-07-19 | VOI1810 | GDL → SMF | Jul 19, 18:55 UTC | Jul 20, 04:50 UTC | 9h 55m |
| 2026-07-18 | VOI7884 | - | Jul 18, 22:15 UTC | Jul 19, 17:20 UTC | 19h 5m |
| 2026-07-18 | VOI5791 | TIJ → MEX | Jul 18, 20:15 UTC | Jul 19, 17:20 UTC | 21h 5m |
| 2026-07-18 | VOI5703 | ORD → GDL | Jul 18, 08:05 UTC | Jul 18, 17:10 UTC | 9h 5m |
| 2026-07-17 | VOI5702 | GDL → ORD | Jul 17, 23:20 UTC | Jul 18, 05:35 UTC | 6h 16m |
| 2026-07-17 | VOI3532 | - | Jul 17, 20:25 UTC | Jul 17, 22:10 UTC | 1h 45m |
| 2026-07-17 | VOI3533 | - | Jul 17, 17:25 UTC | Jul 17, 19:15 UTC | 1h 50m |
| 2026-07-17 | VOI1291 | - | Jul 17, 12:45 UTC | Jul 17, 13:00 UTC | 15m |
| 2026-07-16 | VOI1083 | - | Jul 16, 19:05 UTC | Jul 16, 19:25 UTC | 20m |
| 2026-07-16 | VOI1081 | MTY → MTY | Jul 16, 14:20 UTC | Jul 16, 17:40 UTC | 3h 20m |
| 2026-07-16 | VOI1771 | OAK → MTY | Jul 16, 03:20 UTC | Jul 16, 13:10 UTC | 9h 50m |
| 2026-07-15 | VOI1770 | - | Jul 15, 23:15 UTC | Jul 16, 01:10 UTC | 1h 55m |
| 2026-07-15 | VOI1770 | - | Jul 15, 02:35 UTC | Jul 16, 01:10 UTC | 22h 35m |
| 2026-07-14 | VOI1752 | - | Jul 14, 23:15 UTC | Jul 15, 00:10 UTC | 55m |
| 2026-07-11 | VOI1231 | - | Jul 11, 18:45 UTC | Jul 12, 05:30 UTC | 10h 45m |
| 2026-07-11 | VOI3280 | - | Jul 11, 12:10 UTC | Jul 11, 16:05 UTC | 3h 55m |
| 2026-07-10 | VOI3502 | - | Jul 10, 20:05 UTC | Jul 11, 07:05 UTC | 11h 0m |
| 2026-07-10 | VOI3503 | MTY → CUN | Jul 10, 14:50 UTC | Jul 10, 18:50 UTC | 4h 0m |
| 2026-07-10 | VOI3046 | - | Jul 10, 02:55 UTC | Jul 10, 13:40 UTC | 10h 45m |
| 2026-07-09 | VOI3143 | - | Jul 9, 21:35 UTC | Jul 10, 01:05 UTC | 3h 30m |
| 2026-07-09 | VOI3140 | - | Jul 9, 17:00 UTC | Jul 9, 20:15 UTC | 3h 15m |
| 2026-07-09 | VOI7721 | - | Jul 9, 08:00 UTC | Jul 9, 15:45 UTC | 7h 45m |
| 2026-07-08 | VOI7761 | - | Jul 8, 20:10 UTC | Jul 9, 05:45 UTC | 9h 35m |
| 2026-07-08 | VOI7760 | - | Jul 8, 08:55 UTC | Jul 8, 18:05 UTC | 9h 10m |
| 2026-07-07 | VOI5645 | - | Jul 7, 22:45 UTC | Jul 8, 04:40 UTC | 5h 55m |
| 2026-07-07 | VOI3931 | GUA → CUN | Jul 7, 19:20 UTC | Jul 7, 20:35 UTC | 1h 15m |
| 2026-07-07 | VOI3930 | CUN → GUA | Jul 7, 16:30 UTC | Jul 7, 17:50 UTC | 1h 20m |
| 2026-07-07 | VOI3591 | - | Jul 7, 13:35 UTC | Jul 7, 15:15 UTC | 1h 40m |
| 2026-07-05 | VOI3576 | - | Jul 5, 22:20 UTC | Jul 6, 01:20 UTC | 3h 0m |
| 2026-07-05 | VOI1270 | - | Jul 5, 12:30 UTC | Jul 5, 21:25 UTC | 8h 55m |
| 2026-07-04 | VOI1005 | - | Jul 4, 21:05 UTC | Jul 4, 22:05 UTC | 1h 0m |
| 2026-07-04 | VOI3242 | - | Jul 4, 14:05 UTC | Jul 4, 20:00 UTC | 5h 55m |
| 2026-07-03 | VOI3377 | CUN → TIJ | Jul 3, 22:50 UTC | Jul 4, 04:40 UTC | 5h 50m |
| 2026-07-03 | VOI3931 | GUA → CUN | Jul 3, 19:35 UTC | Jul 3, 20:50 UTC | 1h 15m |
| 2026-07-03 | VOI3930 | CUN → GUA | Jul 3, 16:55 UTC | Jul 3, 18:05 UTC | 1h 10m |
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-VRA page for operator, model, and routing details .