sensors Mode-S transponder

0D0FF8

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VVB · AIRBUS A-320

Hex
0D0FF8
Octal
03207770
Decimal
856,056
Country
MX
Tail
XA-VVB
Type
A320
No current signal · last broadcast 16h ago
Flights observed
235
Distinct callsigns
20
Country
MX
Last broadcast
16h ago

Last known position

Most recent position reported by Mode-S 0D0FF8.

Country allocation

The ICAO 24-bit address 0D0FF8 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
VOI3263 Volaris 6 2026-05-31
VOI3533 Volaris 5 2026-06-08
VOI380 Volaris 4 2026-06-03
VOI7120 Volaris 3 2026-06-07
VOI7110 Volaris 3 2026-06-08
VOI5617 - 3 2026-07-14
VOI5616 - 3 2026-07-14
VOI5605 Volaris 3 2026-05-31
VOI5587 - 3 2026-07-14
VOI5586 - 3 2026-07-14
VOI490 Volaris 3 2026-06-04
VOI3960 Volaris 3 2026-06-07
VOI371 - 3 2026-07-13
VOI3532 Volaris 3 2026-06-08
VOI3482 Volaris 3 2026-05-30
VOI3388 - 3 2026-07-11
VOI3275 - 3 2026-07-09
VOI3268 - 3 2026-07-12
VOI3259 - 3 2026-06-29
VOI249 - 3 2026-07-15

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-15 VOI390 - Jul 15, 12:25 UTCJul 15, 12:40 UTC15m
2026-07-15 VOI249 - Jul 15, 04:15 UTCJul 15, 04:25 UTC10m
2026-07-15 VOI249 - Jul 15, 03:15 UTCJul 15, 03:40 UTC25m
2026-07-14 VOI5596 MTY → MTY Jul 14, 23:15 UTCJul 15, 01:55 UTC2h 40m
2026-07-14 VOI5587 CUN → MTY Jul 14, 20:10 UTCJul 14, 22:15 UTC2h 5m
2026-07-14 VOI5586 MTY → CUN Jul 14, 17:05 UTCJul 14, 19:05 UTC2h 0m
2026-07-14 VOI5617 - Jul 14, 14:35 UTCJul 14, 15:45 UTC1h 10m
2026-07-14 VOI5616 MTY → MEX Jul 14, 12:25 UTCJul 14, 13:30 UTC1h 5m
2026-07-14 VOI244 MEX → MTY Jul 14, 02:05 UTCJul 14, 03:15 UTC1h 10m
2026-07-13 VOI243 - Jul 13, 23:35 UTCJul 14, 00:50 UTC1h 15m
2026-07-13 VOI5587 CUN → MTY Jul 13, 19:55 UTCJul 13, 21:55 UTC2h 0m
2026-07-13 VOI5586 MTY → CUN Jul 13, 16:55 UTCJul 13, 18:55 UTC2h 0m
2026-07-13 VOI5617 - Jul 13, 14:35 UTCJul 13, 15:50 UTC1h 15m
2026-07-13 VOI5616 MTY → MEX Jul 13, 12:15 UTCJul 13, 13:35 UTC1h 20m
2026-07-13 VOI248 - Jul 13, 03:40 UTCJul 13, 04:45 UTC1h 5m
2026-07-13 VOI371 - Jul 13, 00:45 UTCJul 13, 01:20 UTC35m
2026-07-12 VOI3268 - Jul 12, 20:05 UTCJul 12, 23:05 UTC3h 0m
2026-07-12 VOI3252 - Jul 12, 13:25 UTCJul 12, 18:30 UTC5h 5m
2026-07-12 VOI5657 - Jul 12, 01:45 UTCJul 12, 08:20 UTC6h 35m
2026-07-11 VOI3389 - Jul 11, 23:30 UTCJul 12, 00:25 UTC55m
2026-07-11 VOI3388 - Jul 11, 20:50 UTCJul 11, 21:55 UTC1h 5m
2026-07-11 VOI3242 - Jul 11, 14:10 UTCJul 11, 19:35 UTC5h 25m
2026-07-10 VOI3240 - Jul 10, 23:50 UTCJul 11, 05:20 UTC5h 30m
2026-07-10 VOI3191 - Jul 10, 17:45 UTCJul 10, 22:35 UTC4h 50m
2026-07-10 VOI3359 - Jul 10, 07:05 UTCJul 10, 16:30 UTC9h 25m
2026-07-09 VOI3275 - Jul 9, 20:55 UTCJul 10, 03:15 UTC6h 20m
2026-07-09 VOI3242 - Jul 9, 14:10 UTCJul 9, 19:35 UTC5h 25m
2026-07-09 VOI5010 - Jul 9, 01:25 UTCJul 9, 05:45 UTC4h 20m
2026-07-08 VOI3661 - Jul 8, 15:25 UTCJul 9, 00:25 UTC9h 0m
2026-07-07 VOI3275 - Jul 7, 20:25 UTCJul 8, 02:55 UTC6h 30m
2026-07-07 VOI3262 - Jul 7, 13:05 UTCJul 7, 19:10 UTC6h 5m
2026-07-06 VOI3009 - Jul 6, 21:40 UTCJul 7, 02:15 UTC4h 35m
2026-07-06 VOI3230 - Jul 6, 16:30 UTCJul 6, 20:30 UTC4h 0m
2026-07-06 VOI5343 - Jul 6, 06:40 UTCJul 6, 15:35 UTC8h 55m
2026-07-05 VOI3125 - Jul 5, 21:40 UTCJul 6, 03:20 UTC5h 40m
2026-07-05 VOI3213 - Jul 5, 14:30 UTCJul 5, 20:15 UTC5h 45m
2026-07-01 VOI3045 BJX → TIJ Jul 1, 14:45 UTCJul 1, 15:50 UTC1h 5m
2026-06-30 VOI3046 - Jun 30, 00:45 UTCJun 30, 01:50 UTC1h 5m
2026-06-29 VOI3043 - Jun 29, 16:55 UTCJun 29, 23:29 UTC6h 35m
2026-06-29 VOI3045 BJX → TIJ Jun 29, 09:05 UTCJun 29, 15:49 UTC6h 45m
2026-06-29 VOI3259 - Jun 29, 00:49 UTCJun 29, 04:39 UTC3h 50m
2026-06-28 VOI3232 - Jun 28, 19:29 UTCJun 28, 23:25 UTC3h 55m
2026-06-28 VOI3252 - Jun 28, 13:14 UTCJun 28, 18:19 UTC5h 5m
2026-06-28 VOI3317 - Jun 28, 04:15 UTCJun 28, 05:15 UTC1h 0m
2026-06-28 VOI3316 - Jun 28, 01:55 UTCJun 28, 02:49 UTC55m
2026-06-27 VOI3388 - Jun 27, 20:55 UTCJun 28, 00:35 UTC3h 40m
2026-06-27 VOI1013 TIJ → GDL Jun 27, 13:15 UTCJun 27, 19:39 UTC6h 25m
2026-06-27 VOI5610 - Jun 27, 04:05 UTCJun 27, 06:30 UTC2h 25m
2026-06-27 VOI5589 - Jun 27, 00:50 UTCJun 27, 02:55 UTC2h 5m
2026-06-26 VOI5588 - Jun 26, 21:50 UTCJun 26, 23:49 UTC2h 0m

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-VVB page for operator, model, and routing details .

Mode-S 0D0FF8 frequently asked

What is Mode-S code 0D0FF8?
0D0FF8 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VVB.
Where is Mode-S 0D0FF8 registered?
Mode-S code 0D0FF8 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0FF8 broadcasting right now?
No active broadcast right now. Last signal was 16h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0FF8, octal 03207770, decimal 856,056.
What flights does 0D0FF8 operate?
Mode-S 0D0FF8 has broadcast 20 distinct callsigns, including VOI3263, VOI3533, VOI380, VOI7120, VOI7110.