sensors Mode-S transponder
0D0E68
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VYD · AIRBUS A-320
- Hex
- 0D0E68
- Octal
- 03207150
- Decimal
- 855,656
- Country
- MX
- Tail
- XA-VYD
- Type
- A320
- Flights observed
- 134
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- 52m ago
Last known position
Country allocation
The ICAO 24-bit address 0D0E68 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 |
|---|---|---|---|
| VIV7432 | VivaAerobus | 8 | 2026-05-25 |
| VIV9532 | VivaAerobus | 7 | 2026-04-22 |
| VIV9533 | VivaAerobus | 6 | 2026-04-22 |
| VIV5025 | VivaAerobus | 5 | 2026-05-29 |
| VIV7370 | VivaAerobus | 4 | 2026-04-21 |
| VIV7344 | VivaAerobus | 4 | 2026-05-28 |
| VIV5069 | VivaAerobus | 4 | 2026-04-21 |
| VIV5026 | VivaAerobus | 4 | 2026-05-29 |
| VIV9067 | VivaAerobus | 3 | 2026-05-29 |
| VIV7345 | VivaAerobus | 3 | 2026-04-26 |
| VIV4180 | VivaAerobus | 3 | 2026-04-27 |
| VIV2141 | VivaAerobus | 3 | 2026-05-10 |
| VIV9500 | VivaAerobus | 2 | 2026-04-21 |
| VIV9387 | VivaAerobus | 2 | 2026-04-21 |
| VIV9386 | VivaAerobus | 2 | 2026-04-21 |
| VIV7371 | VivaAerobus | 2 | 2026-04-16 |
| VIV5067 | - | 2 | 2026-04-13 |
| VIV5003 | VivaAerobus | 2 | 2026-05-23 |
| VIV3677 | - | 2 | 2026-04-29 |
| VIV3676 | - | 2 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | VIV9067 | CJS → BJX | May 29, 23:30 UTC | May 30, 00:00 UTC | 30m |
| 2026-05-29 | VIV5026 | TIJ → BJX | May 29, 16:55 UTC | May 29, 22:30 UTC | 5h 35m |
| 2026-05-29 | VIV5025 | BJX → TIJ | May 29, 14:55 UTC | May 29, 15:45 UTC | 50m |
| 2026-05-28 | VIV5025 | BJX → TIJ | May 28, 19:45 UTC | May 29, 15:45 UTC | 20h 0m |
| 2026-05-28 | VIV7344 | BJX → NLU | May 28, 13:00 UTC | May 28, 13:10 UTC | 10m |
| 2026-05-27 | VIV9067 | CJS → BJX | May 27, 23:35 UTC | May 28, 00:40 UTC | 1h 5m |
| 2026-05-27 | VIV5026 | TIJ → BJX | May 27, 17:05 UTC | May 27, 22:40 UTC | 5h 35m |
| 2026-05-25 | VIV7432 | TIJ → GDL | May 25, 13:05 UTC | May 26, 02:04 UTC | 12h 59m |
| 2026-05-24 | VIV7432 | TIJ → GDL | May 24, 13:15 UTC | May 24, 21:30 UTC | 8h 15m |
| 2026-05-23 | VIV5003 | CUL → TIJ | May 23, 13:20 UTC | May 23, 17:50 UTC | 4h 30m |
| 2026-05-23 | VIV5117 | PBC → TIJ | May 23, 03:15 UTC | May 23, 06:40 UTC | 3h 25m |
| 2026-05-22 | VIV5116 | TIJ → PBC | May 22, 23:10 UTC | May 23, 02:05 UTC | 2h 55m |
| 2026-05-22 | VIV7079 | - | May 22, 13:20 UTC | May 22, 20:25 UTC | 7h 5m |
| 2026-05-21 | VIV7432 | TIJ → GDL | May 21, 13:01 UTC | May 22, 02:25 UTC | 13h 25m |
| 2026-05-20 | VIV5084 | TIJ → PVR | May 20, 17:55 UTC | May 20, 23:50 UTC | 5h 55m |
| 2026-05-18 | VIV7432 | TIJ → GDL | May 18, 13:05 UTC | May 19, 02:00 UTC | 12h 54m |
| 2026-05-17 | VIV7432 | TIJ → GDL | May 17, 13:05 UTC | May 18, 02:25 UTC | 13h 20m |
| 2026-05-16 | VIV7432 | TIJ → GDL | May 16, 13:11 UTC | May 17, 02:05 UTC | 12h 55m |
| 2026-05-15 | VIV7432 | TIJ → GDL | May 15, 13:10 UTC | May 16, 01:55 UTC | 12h 44m |
| 2026-05-14 | VIV7432 | TIJ → GDL | May 14, 13:01 UTC | May 15, 01:50 UTC | 12h 50m |
| 2026-05-13 | VIV5003 | CUL → TIJ | May 13, 13:20 UTC | May 13, 17:55 UTC | 4h 35m |
| 2026-05-12 | VIV3114 | GDL → TIJ | May 12, 13:30 UTC | May 12, 14:40 UTC | 1h 10m |
| 2026-05-11 | VIV3110 | GDL → TIJ | May 11, 14:15 UTC | May 11, 21:30 UTC | 7h 16m |
| 2026-05-11 | VIV3278 | GDL → NLU | May 11, 12:35 UTC | May 11, 13:05 UTC | 30m |
| 2026-05-11 | VIV7305 | NLU → GDL | May 11, 03:00 UTC | May 11, 03:15 UTC | 15m |
| 2026-05-11 | 7305 | - | May 11, 01:40 UTC | May 11, 02:00 UTC | 20m |
| 2026-05-10 | VIV7304 | NLU → TAM | May 10, 23:44 UTC | May 11, 00:05 UTC | 20m |
| 2026-05-10 | VIV2141 | GDL → CUN | May 10, 01:04 UTC | May 10, 13:44 UTC | 12h 40m |
| 2026-05-09 | VIV547 | ORD → GDL | May 9, 17:40 UTC | May 9, 20:49 UTC | 3h 10m |
| 2026-05-09 | VIV186 | MEX → ORD | May 9, 12:00 UTC | May 9, 15:35 UTC | 3h 35m |
| 2026-05-08 | VIV1017 | CUN → MEX | May 8, 23:10 UTC | May 9, 05:35 UTC | 6h 25m |
| 2026-05-08 | VIV7040 | CUN → NLU | May 8, 13:25 UTC | May 8, 18:20 UTC | 4h 55m |
| 2026-05-08 | VIV1051 | CUU → MEX | May 8, 05:39 UTC | May 8, 05:54 UTC | 15m |
| 2026-05-08 | VIV1050 | MEX → CUU | May 8, 01:04 UTC | May 8, 01:19 UTC | 15m |
| 2026-05-07 | VIV1151 | MZT → MEX | May 7, 20:40 UTC | May 7, 20:45 UTC | 5m |
| 2026-05-07 | VIV1150 | MEX → MZT | May 7, 16:55 UTC | May 7, 17:10 UTC | 15m |
| 2026-05-07 | VIV1269 | TRC → MEX | May 7, 15:30 UTC | May 7, 15:45 UTC | 15m |
| 2026-05-07 | VIV1268 | MEX → TRC | May 7, 12:25 UTC | May 7, 12:40 UTC | 15m |
| 2026-05-06 | VIV1373 | CUN → MEX | May 6, 23:20 UTC | May 7, 04:05 UTC | 4h 45m |
| 2026-05-06 | VIV2133 | GDL → CUN | May 6, 14:45 UTC | May 6, 22:20 UTC | 7h 34m |
| 2026-05-06 | VIV3044 | GDL → VER | May 6, 04:35 UTC | May 6, 13:35 UTC | 9h 0m |
| 2026-05-05 | VIV3104 | GDL → TIJ | May 5, 17:40 UTC | May 6, 03:25 UTC | 9h 45m |
| 2026-05-05 | VIV2141 | GDL → CUN | May 5, 14:50 UTC | May 5, 15:05 UTC | 15m |
| 2026-05-05 | VIV2141 | GDL → CUN | May 5, 03:50 UTC | May 5, 14:00 UTC | 10h 10m |
| 2026-05-04 | VIV3244 | GDL → PBC | May 4, 14:10 UTC | May 5, 03:00 UTC | 12h 51m |
| 2026-05-04 | VIV1070 | MEX → GDL | May 4, 05:35 UTC | May 4, 13:00 UTC | 7h 25m |
| 2026-05-04 | VIV1069 | GDL → MEX | May 4, 01:05 UTC | May 4, 04:15 UTC | 3h 10m |
| 2026-05-03 | VIV1065 | GDL → MEX | May 3, 20:05 UTC | May 4, 00:00 UTC | 3h 55m |
| 2026-05-03 | VIV3206 | GDL → MTY | May 3, 14:30 UTC | May 3, 18:14 UTC | 3h 45m |
| 2026-05-02 | VIV4179 | BJX → MTY | May 2, 20:00 UTC | May 3, 13:20 UTC | 17h 19m |
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-VYD page for operator, model, and routing details .