Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D08D7

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-UVG · MCDONNELL-DOUGLAS MD-83

Hex
0D08D7
Octal
03204327
Decimal
854,231
Country
MX
Tail
XA-UVG
Type
MD83
No current signal · last broadcast 2d ago
Flights observed
95
Distinct callsigns
2
Country
MX
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 0D08D7.

Country allocation

The ICAO 24-bit address 0D08D7 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 2 distinct

Callsign Airline Flights Last seen
VTM663 - 88 2026-07-15
00000000 - 7 2026-05-15

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-15 VTM663 - Jul 15, 14:20 UTCJul 15, 15:50 UTC1h 30m
2026-07-15 VTM663 - Jul 15, 11:05 UTCJul 15, 12:35 UTC1h 30m
2026-07-15 VTM663 LRD → RFD Jul 15, 04:20 UTCJul 15, 06:45 UTC2h 25m
2026-07-15 VTM663 - Jul 15, 02:15 UTCJul 15, 02:45 UTC30m
2026-07-07 VTM663 - Jul 7, 15:20 UTCJul 7, 20:45 UTC5h 25m
2026-07-07 VTM663 - Jul 7, 03:15 UTCJul 7, 04:55 UTC1h 40m
2026-07-06 VTM663 - Jul 6, 20:55 UTCJul 6, 23:25 UTC2h 30m
2026-07-06 VTM663 - Jul 6, 19:00 UTCJul 6, 19:35 UTC35m
2026-06-27 VTM663 - Jun 27, 21:40 UTCJun 27, 23:00 UTC1h 20m
2026-06-27 VTM663 - Jun 27, 07:24 UTCJun 27, 08:55 UTC1h 30m
2026-06-27 VTM663 - Jun 27, 02:59 UTCJun 27, 05:29 UTC2h 30m
2026-06-27 VTM663 - Jun 27, 01:00 UTCJun 27, 01:35 UTC35m
2026-06-26 VTM663 - Jun 26, 21:50 UTCJun 27, 00:29 UTC2h 40m
2026-06-25 VTM663 - Jun 25, 14:24 UTCJun 25, 16:45 UTC2h 20m
2026-06-24 VTM663 - Jun 24, 12:30 UTCJun 24, 23:14 UTC10h 45m
2026-06-23 VTM663 LRD → YIP Jun 23, 22:10 UTCJun 24, 01:04 UTC2h 55m
2026-06-23 VTM663 - Jun 23, 19:59 UTCJun 23, 20:29 UTC30m
2026-06-20 VTM663 - Jun 20, 22:39 UTCJun 21, 00:04 UTC1h 25m
2026-06-20 VTM663 - Jun 20, 18:24 UTCJun 20, 20:05 UTC1h 40m
2026-06-20 VTM663 - Jun 20, 00:04 UTCJun 20, 02:29 UTC2h 25m
2026-06-19 VTM663 - Jun 19, 18:34 UTCJun 19, 22:34 UTC4h 0m
2026-06-17 VTM663 - Jun 17, 17:00 UTCJun 17, 19:50 UTC2h 50m
2026-06-16 VTM663 - Jun 16, 09:10 UTCJun 16, 11:25 UTC2h 15m
2026-06-16 VTM663 - Jun 16, 04:39 UTCJun 16, 08:20 UTC3h 40m
2026-06-13 VTM663 - Jun 13, 19:00 UTCJun 14, 05:25 UTC10h 25m
2026-06-13 VTM663 - Jun 13, 15:35 UTCJun 13, 16:10 UTC35m
2026-06-10 VTM663 - Jun 10, 16:40 UTCJun 10, 18:05 UTC1h 25m
2026-06-10 VTM663 - Jun 10, 13:50 UTCJun 10, 15:40 UTC1h 50m
2026-06-09 VTM663 LRD → YIP Jun 9, 06:40 UTCJun 9, 09:25 UTC2h 45m
2026-06-09 VTM663 - Jun 9, 02:45 UTCJun 9, 05:15 UTC2h 30m
2026-06-05 VTM663 - Jun 5, 21:05 UTCJun 6, 00:05 UTC3h 0m
2026-06-05 VTM663 LRD → SDF Jun 5, 03:10 UTCJun 5, 05:35 UTC2h 25m
2026-06-05 VTM663 - Jun 5, 00:25 UTCJun 5, 01:15 UTC50m
2026-06-04 VTM663 - Jun 4, 20:30 UTCJun 4, 23:10 UTC2h 40m
2026-06-04 VTM663 - Jun 4, 16:20 UTCJun 4, 18:55 UTC2h 35m
2026-06-03 VTM663 LRD → SDF Jun 3, 07:15 UTCJun 3, 09:40 UTC2h 25m
2026-06-03 VTM663 MTY → LRD Jun 3, 05:00 UTCJun 3, 05:35 UTC35m
2026-06-03 VTM663 - Jun 3, 01:15 UTCJun 3, 03:45 UTC2h 30m
2026-06-02 VTM663 - Jun 2, 18:40 UTCJun 2, 20:05 UTC1h 25m
2026-06-02 VTM663 - Jun 2, 07:00 UTCJun 2, 08:20 UTC1h 20m
2026-06-02 VTM663 LRD → SDF Jun 2, 03:15 UTCJun 2, 05:35 UTC2h 20m
2026-06-01 VTM663 - Jun 1, 22:50 UTCJun 2, 01:55 UTC3h 5m
2026-05-29 VTM663 - May 29, 17:15 UTCMay 29, 20:00 UTC2h 45m
2026-05-28 VTM663 - May 28, 03:20 UTCMay 28, 05:45 UTC2h 25m
2026-05-27 VTM663 - May 27, 23:10 UTCMay 28, 02:10 UTC3h 0m
2026-05-24 VTM663 - May 24, 00:00 UTCMay 24, 01:30 UTC1h 30m
2026-05-23 VTM663 - May 23, 20:30 UTCMay 23, 22:05 UTC1h 35m
2026-05-23 VTM663 - May 23, 03:40 UTCMay 23, 05:55 UTC2h 15m
2026-05-23 VTM663 - May 23, 01:45 UTCMay 23, 02:15 UTC30m
2026-05-22 VTM663 - May 22, 22:45 UTCMay 23, 01:00 UTC2h 15m

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

Mode-S 0D08D7 frequently asked

What is Mode-S code 0D08D7?
0D08D7 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-UVG.
Where is Mode-S 0D08D7 registered?
Mode-S code 0D08D7 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D08D7 broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D08D7, octal 03204327, decimal 854,231.
What flights does 0D08D7 operate?
Mode-S 0D08D7 has broadcast 2 distinct callsigns, including VTM663, 00000000.