Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0468

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-SPO · BOMBARDIER Regional Jet CRJ-100

Hex
0D0468
Octal
03202150
Decimal
853,096
Country
MX
Tail
XA-SPO
Type
CRJ1
No current signal · last broadcast 2d ago
Flights observed
66
Distinct callsigns
5
Country
MX
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 0D0468.

Country allocation

The ICAO 24-bit address 0D0468 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 5 distinct

Callsign Airline Flights Last seen
VTM2687 - 35 2026-06-27
VTM9987 - 27 2026-06-25
VTM2807 - 2 2026-06-05
VTM085 - 1 2026-05-13
VTM0085 - 1 2026-05-06

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-27 VTM2687 PHX → HMO Jun 27, 02:59 UTCJun 27, 03:44 UTC45m
2026-06-26 VTM2687 HMO → PHX Jun 26, 23:49 UTCJun 27, 00:34 UTC45m
2026-06-26 VTM2687 PHX → HMO Jun 26, 02:00 UTCJun 26, 02:44 UTC45m
2026-06-25 VTM2687 - Jun 25, 23:39 UTCJun 26, 00:30 UTC50m
2026-06-25 VTM9987 PHX → HMO Jun 25, 05:25 UTCJun 25, 06:09 UTC45m
2026-06-24 VTM9987 - Jun 24, 23:54 UTCJun 25, 00:44 UTC50m
2026-06-24 VTM9987 - Jun 24, 04:00 UTCJun 24, 04:44 UTC45m
2026-06-24 VTM9987 - Jun 24, 00:05 UTCJun 24, 00:55 UTC50m
2026-06-23 VTM2687 - Jun 23, 01:54 UTCJun 23, 02:45 UTC50m
2026-06-23 VTM2687 HMO → PHX Jun 23, 00:04 UTCJun 23, 00:54 UTC50m
2026-06-20 VTM2687 PHX → HMO Jun 20, 03:24 UTCJun 20, 04:09 UTC45m
2026-06-20 VTM2687 - Jun 20, 00:14 UTCJun 20, 01:09 UTC55m
2026-06-19 VTM9987 - Jun 19, 04:19 UTCJun 19, 05:09 UTC50m
2026-06-18 VTM9987 - Jun 18, 23:55 UTCJun 19, 00:49 UTC54m
2026-06-18 VTM2687 PHX → HMO Jun 18, 02:50 UTCJun 18, 03:35 UTC45m
2026-06-17 VTM2687 - Jun 17, 23:55 UTCJun 18, 01:25 UTC1h 30m
2026-06-17 VTM2687 PHX → HMO Jun 17, 03:05 UTCJun 17, 03:55 UTC50m
2026-06-17 VTM2687 - Jun 17, 00:20 UTCJun 17, 01:15 UTC55m
2026-06-16 VTM2687 PHX → HMO Jun 16, 04:45 UTCJun 16, 05:30 UTC45m
2026-06-16 VTM2687 - Jun 16, 00:15 UTCJun 16, 01:04 UTC50m
2026-06-13 VTM2687 PHX → HMO Jun 13, 05:55 UTCJun 13, 06:45 UTC50m
2026-06-13 VTM2687 - Jun 13, 00:35 UTCJun 13, 01:25 UTC50m
2026-06-12 VTM9987 PHX → HMO Jun 12, 02:40 UTCJun 12, 03:30 UTC50m
2026-06-12 VTM9987 - Jun 12, 00:45 UTCJun 12, 01:40 UTC55m
2026-06-11 VTM2687 PHX → HMO Jun 11, 03:20 UTCJun 11, 04:05 UTC45m
2026-06-11 VTM2687 - Jun 11, 00:00 UTCJun 11, 00:50 UTC50m
2026-06-10 VTM9987 PHX → HMO Jun 10, 03:35 UTCJun 10, 04:20 UTC45m
2026-06-09 VTM9987 - Jun 9, 23:55 UTCJun 10, 00:45 UTC50m
2026-06-09 VTM2687 - Jun 9, 03:20 UTCJun 9, 03:55 UTC35m
2026-06-09 VTM2687 - Jun 9, 00:45 UTCJun 9, 01:15 UTC30m
2026-06-06 VTM2687 - Jun 6, 03:35 UTCJun 6, 04:25 UTC50m
2026-06-06 VTM2687 - Jun 6, 00:20 UTCJun 6, 01:15 UTC55m
2026-06-05 VTM2807 - Jun 5, 22:50 UTCJun 5, 23:35 UTC45m
2026-06-05 VTM2807 - Jun 5, 20:45 UTCJun 5, 21:35 UTC50m
2026-06-04 VTM9987 PHX → HMO Jun 4, 04:35 UTCJun 4, 05:20 UTC45m
2026-06-04 VTM9987 - Jun 4, 00:05 UTCJun 4, 00:55 UTC50m
2026-06-03 VTM9987 - Jun 3, 05:20 UTCJun 3, 06:05 UTC45m
2026-06-03 VTM2687 HMO → PHX Jun 3, 00:40 UTCJun 3, 01:30 UTC50m
2026-06-02 VTM2687 PHX → HMO Jun 2, 02:45 UTCJun 2, 03:35 UTC50m
2026-06-02 VTM2687 - Jun 2, 00:00 UTCJun 2, 00:50 UTC50m
2026-05-30 VTM2687 - May 30, 03:20 UTCMay 30, 03:50 UTC30m
2026-05-30 VTM2687 - May 30, 01:05 UTCMay 30, 01:35 UTC30m
2026-05-29 VTM9987 - May 29, 04:35 UTCMay 29, 05:10 UTC35m
2026-05-29 VTM9987 - May 29, 00:15 UTCMay 29, 00:45 UTC30m
2026-05-28 VTM2687 - May 28, 04:25 UTCMay 28, 04:55 UTC30m
2026-05-28 VTM9987 - May 28, 00:40 UTCMay 28, 01:10 UTC30m
2026-05-27 VTM9987 - May 27, 22:50 UTCMay 27, 23:20 UTC30m
2026-05-27 VTM9987 - May 27, 19:40 UTCMay 27, 20:05 UTC25m
2026-05-23 VTM2687 - May 23, 03:10 UTCMay 23, 03:40 UTC30m
2026-05-23 VTM2687 - May 23, 00:40 UTCMay 23, 01:05 UTC25m

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

Mode-S 0D0468 frequently asked

What is Mode-S code 0D0468?
0D0468 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-SPO.
Where is Mode-S 0D0468 registered?
Mode-S code 0D0468 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0468 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 0D0468, octal 03202150, decimal 853,096.
What flights does 0D0468 operate?
Mode-S 0D0468 has broadcast 5 distinct callsigns, including VTM2687, VTM9987, VTM2807, VTM085, VTM0085.