sensors Mode-S transponder
0D0CB1
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VRQ · AIRBUS A-320neo
- Hex
- 0D0CB1
- Octal
- 03206261
- Decimal
- 855,217
- Country
- MX
- Tail
- XA-VRQ
- Type
- A20N
- Flights observed
- 308
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- Jul 26, 02:25 UTC
Current position
Country allocation
The ICAO 24-bit address 0D0CB1 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 |
|---|---|---|---|
| VOI3918 | Volaris | 11 | 2026-07-20 |
| VOI3919 | Volaris | 9 | 2026-07-20 |
| VOI183 | - | 7 | 2026-07-02 |
| VOI3483 | Volaris | 6 | 2026-04-26 |
| VOI3482 | Volaris | 6 | 2026-04-26 |
| VOI1704 | - | 5 | 2026-06-27 |
| VOI5616 | - | 4 | 2026-07-16 |
| VOI3291 | Volaris | 4 | 2026-06-10 |
| VOI182 | - | 4 | 2026-07-02 |
| VOI1791 | Volaris | 4 | 2026-05-24 |
| VOI5607 | Volaris | 3 | 2026-04-25 |
| VOI5606 | Volaris | 3 | 2026-04-25 |
| VOI5605 | Volaris | 3 | 2026-04-26 |
| VOI3515 | - | 3 | 2026-04-13 |
| VOI3123 | Volaris | 3 | 2026-05-04 |
| VOI1965 | Volaris | 3 | 2026-07-25 |
| VOI1964 | Volaris | 3 | 2026-07-25 |
| VOI1850 | - | 3 | 2026-07-21 |
| VOI1820 | - | 3 | 2026-06-23 |
| VOI1810 | - | 3 | 2026-06-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | VOI1965 | DTW → GDL | Jul 25, 12:05 UTC | Jul 26, 02:25 UTC | 14h 20m |
| 2026-07-25 | VOI1964 | GDL → DTW | Jul 25, 02:35 UTC | Jul 25, 09:55 UTC | 7h 20m |
| 2026-07-24 | VOI1752 | GDL → SAT | Jul 24, 18:45 UTC | Jul 25, 00:15 UTC | 5h 30m |
| 2026-07-24 | VOI1411 | REX → GDL | Jul 24, 14:35 UTC | Jul 24, 17:35 UTC | 3h 0m |
| 2026-07-24 | VOI5823 | SJC → GDL | Jul 24, 00:30 UTC | Jul 24, 13:40 UTC | 13h 10m |
| 2026-07-23 | VOI1965 | DTW → GDL | Jul 23, 12:45 UTC | Jul 23, 22:10 UTC | 9h 25m |
| 2026-07-23 | VOI1964 | GDL → DTW | Jul 23, 02:50 UTC | Jul 23, 10:25 UTC | 7h 35m |
| 2026-07-22 | VOI7849 | LAX → OAX | Jul 22, 21:45 UTC | Jul 23, 01:25 UTC | 3h 40m |
| 2026-07-22 | VOI7848 | - | Jul 22, 16:15 UTC | Jul 22, 19:45 UTC | 3h 30m |
| 2026-07-22 | VOI1240 | - | Jul 22, 10:20 UTC | Jul 22, 14:15 UTC | 3h 55m |
| 2026-07-21 | VOI1850 | - | Jul 21, 17:15 UTC | Jul 22, 02:20 UTC | 9h 5m |
| 2026-07-20 | VOI5722 | GDL → LAX | Jul 20, 18:20 UTC | Jul 21, 14:40 UTC | 20h 19m |
| 2026-07-20 | VOI3919 | LIM → MEX | Jul 20, 11:30 UTC | Jul 20, 16:55 UTC | 5h 25m |
| 2026-07-20 | VOI3918 | MEX → LIM | Jul 20, 08:40 UTC | Jul 20, 09:15 UTC | 35m |
| 2026-07-20 | VOI3918 | MEX → LIM | Jul 20, 04:15 UTC | Jul 20, 06:35 UTC | 2h 20m |
| 2026-07-20 | VOI441 | - | Jul 20, 02:00 UTC | Jul 20, 02:35 UTC | 35m |
| 2026-07-19 | VOI1083 | - | Jul 19, 18:30 UTC | Jul 19, 23:50 UTC | 5h 20m |
| 2026-07-19 | VOI1082 | - | Jul 19, 14:15 UTC | Jul 19, 17:35 UTC | 3h 20m |
| 2026-07-19 | VOI5045 | LAS → GDL | Jul 19, 03:15 UTC | Jul 19, 13:10 UTC | 9h 55m |
| 2026-07-18 | VOI5044 | GDL → LAS | Jul 18, 20:20 UTC | Jul 19, 01:35 UTC | 5h 15m |
| 2026-07-18 | VOI5763 | DEN → GDL | Jul 18, 02:50 UTC | Jul 18, 18:25 UTC | 15h 35m |
| 2026-07-17 | VOI5762 | GDL → DEN | Jul 17, 23:35 UTC | Jul 18, 01:00 UTC | 1h 25m |
| 2026-07-17 | VOI5762 | GDL → DEN | Jul 17, 00:20 UTC | Jul 18, 00:15 UTC | 23h 55m |
| 2026-07-16 | VOI1271 | - | Jul 16, 21:45 UTC | Jul 17, 00:55 UTC | 3h 10m |
| 2026-07-16 | VOI1270 | - | Jul 16, 14:29 UTC | Jul 16, 20:29 UTC | 6h 0m |
| 2026-07-16 | VOI5616 | - | Jul 16, 13:05 UTC | Jul 16, 13:15 UTC | 10m |
| 2026-07-16 | VOI5616 | - | Jul 16, 12:09 UTC | Jul 16, 12:34 UTC | 25m |
| 2026-07-16 | VOI5593 | CUN → MTY | Jul 16, 03:25 UTC | Jul 16, 05:30 UTC | 2h 5m |
| 2026-07-16 | VOI5592 | - | Jul 16, 00:35 UTC | Jul 16, 02:35 UTC | 2h 0m |
| 2026-07-15 | VOI5615 | - | Jul 15, 20:25 UTC | Jul 15, 23:45 UTC | 3h 20m |
| 2026-07-15 | VOI5613 | - | Jul 15, 15:50 UTC | Jul 15, 19:10 UTC | 3h 20m |
| 2026-07-15 | VOI244 | - | Jul 15, 02:05 UTC | Jul 15, 03:15 UTC | 1h 10m |
| 2026-07-14 | VOI243 | MTY → MEX | Jul 14, 23:40 UTC | Jul 15, 00:45 UTC | 1h 5m |
| 2026-07-14 | VOI5590 | MTY → MTY | Jul 14, 16:25 UTC | Jul 14, 20:50 UTC | 4h 25m |
| 2026-07-14 | VOI5548 | - | Jul 14, 12:20 UTC | Jul 14, 15:25 UTC | 3h 5m |
| 2026-07-14 | VOI248 | - | Jul 14, 03:15 UTC | Jul 14, 04:30 UTC | 1h 15m |
| 2026-07-13 | VOI371 | - | Jul 13, 20:05 UTC | Jul 14, 01:30 UTC | 5h 25m |
| 2026-07-13 | VOI3269 | - | Jul 13, 17:40 UTC | Jul 13, 18:55 UTC | 1h 15m |
| 2026-07-13 | VOI370 | - | Jul 13, 14:10 UTC | Jul 13, 14:35 UTC | 25m |
| 2026-07-13 | VOI111 | CUN → MEX | Jul 13, 10:40 UTC | Jul 13, 12:30 UTC | 1h 50m |
| 2026-07-13 | VOI110 | - | Jul 13, 04:15 UTC | Jul 13, 06:05 UTC | 1h 50m |
| 2026-07-13 | VOI145 | - | Jul 13, 02:45 UTC | Jul 13, 02:55 UTC | 10m |
| 2026-07-12 | VOI1089 | - | Jul 12, 20:40 UTC | Jul 12, 21:00 UTC | 20m |
| 2026-07-12 | VOI1851 | SEA → MTY | Jul 12, 06:15 UTC | Jul 12, 19:45 UTC | 13h 30m |
| 2026-07-11 | VOI1850 | - | Jul 11, 19:45 UTC | Jul 12, 02:40 UTC | 6h 55m |
| 2026-07-11 | VOI1350 | - | Jul 11, 17:50 UTC | Jul 11, 18:20 UTC | 30m |
| 2026-07-10 | VOI1350 | - | Jul 10, 22:20 UTC | Jul 11, 18:20 UTC | 20h 0m |
| 2026-07-10 | VOI1401 | - | Jul 10, 21:00 UTC | Jul 11, 18:20 UTC | 21h 20m |
| 2026-07-10 | VOI1773 | - | Jul 10, 06:20 UTC | Jul 10, 20:05 UTC | 13h 45m |
| 2026-07-09 | VOI1772 | MCO → OAK | Jul 9, 19:25 UTC | Jul 10, 04:05 UTC | 8h 40m |
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-VRQ page for operator, model, and routing details .