Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0FFB

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VHB · BOEING 737-400

Hex
0D0FFB
Octal
03207773
Decimal
856,059
Country
MX
Tail
XA-VHB
Type
B734
No current signal · last broadcast 13h ago
Flights observed
140
Distinct callsigns
11
Country
MX
Last broadcast
13h ago

Last known position

Most recent position reported by Mode-S 0D0FFB.

Country allocation

The ICAO 24-bit address 0D0FFB 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 11 distinct

Callsign Airline Flights Last seen
VTM2208 - 36 2026-07-17
VTM2207 - 29 2026-07-17
VTM2203 - 23 2026-05-29
VTM2202 - 14 2026-05-29
VTM7701 - 8 2026-04-17
VTM7702 - 7 2026-04-16
VTM8802 - 3 2026-04-23
2207 - 3 2026-07-15
VYM2208 - 1 2026-06-17
VTM3202 - 1 2026-06-03
VT2207 - 1 2026-06-19

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 VTM2208 - Jul 17, 14:55 UTCJul 17, 15:05 UTC10m
2026-07-17 VTM2208 - Jul 17, 14:04 UTCJul 17, 14:20 UTC15m
2026-07-17 VTM2208 - Jul 17, 04:29 UTCJul 17, 04:49 UTC20m
2026-07-17 VTM2207 - Jul 17, 03:34 UTCJul 17, 03:50 UTC15m
2026-07-16 VTM2208 - Jul 16, 14:45 UTCJul 16, 15:00 UTC15m
2026-07-16 VTM2208 - Jul 16, 14:10 UTCJul 16, 14:15 UTC5m
2026-07-16 VTM2208 - Jul 16, 04:25 UTCJul 16, 04:40 UTC15m
2026-07-16 VTM2207 - Jul 16, 03:40 UTCJul 16, 03:50 UTC10m
2026-07-15 VTM2208 - Jul 15, 14:35 UTCJul 15, 14:45 UTC10m
2026-07-15 VTM2208 - Jul 15, 13:45 UTCJul 15, 14:00 UTC15m
2026-07-15 2207 - Jul 15, 04:35 UTCJul 15, 04:55 UTC20m
2026-07-15 VTM2207 - Jul 15, 03:50 UTCJul 15, 04:05 UTC15m
2026-07-14 VTM2208 - Jul 14, 15:40 UTCJul 14, 15:55 UTC15m
2026-07-14 VTM2208 - Jul 14, 14:25 UTCJul 14, 14:30 UTC5m
2026-07-14 VTM2207 - Jul 14, 05:05 UTCJul 14, 05:15 UTC10m
2026-07-10 VTM2208 - Jul 10, 14:45 UTCJul 10, 14:55 UTC10m
2026-07-10 VTM2208 - Jul 10, 13:50 UTCJul 10, 14:05 UTC15m
2026-07-10 VTM2207 - Jul 10, 05:20 UTCJul 10, 05:35 UTC15m
2026-07-10 VTM2207 - Jul 10, 04:25 UTCJul 10, 04:40 UTC15m
2026-07-09 VTM2208 - Jul 9, 13:45 UTCJul 9, 14:00 UTC15m
2026-07-09 VTM2207 - Jul 9, 04:50 UTCJul 9, 05:10 UTC20m
2026-07-08 VTM2208 - Jul 8, 14:55 UTCJul 8, 15:05 UTC10m
2026-07-08 VTM2208 - Jul 8, 14:05 UTCJul 8, 14:20 UTC15m
2026-07-08 VTM2207 - Jul 8, 04:35 UTCJul 8, 05:00 UTC25m
2026-07-08 VTM2207 - Jul 8, 03:50 UTCJul 8, 04:00 UTC10m
2026-07-07 VTM2208 - Jul 7, 15:20 UTCJul 7, 15:30 UTC10m
2026-07-07 VTM2208 - Jul 7, 14:35 UTCJul 7, 14:40 UTC5m
2026-07-07 VTM2207 - Jul 7, 04:45 UTCJul 7, 04:55 UTC10m
2026-07-07 VTM2207 - Jul 7, 03:45 UTCJul 7, 03:50 UTC5m
2026-07-03 - - Jul 3, 14:55 UTCJul 3, 15:10 UTC15m
2026-07-03 - - Jul 3, 14:05 UTCJul 3, 14:15 UTC10m
2026-07-02 - - Jul 2, 05:00 UTCJul 2, 05:15 UTC15m
2026-07-01 - - Jul 1, 15:10 UTCJul 1, 15:20 UTC10m
2026-07-01 - - Jul 1, 13:55 UTCJul 1, 14:05 UTC10m
2026-07-01 - - Jul 1, 05:05 UTCJul 1, 05:25 UTC20m
2026-06-30 - - Jun 30, 15:35 UTCJun 30, 15:45 UTC10m
2026-06-30 - - Jun 30, 14:35 UTCJun 30, 14:45 UTC10m
2026-06-30 - - Jun 30, 04:40 UTCJun 30, 04:55 UTC15m
2026-06-30 - - Jun 30, 03:45 UTCJun 30, 03:50 UTC5m
2026-06-26 VTM2208 - Jun 26, 14:44 UTCJun 26, 14:55 UTC10m
2026-06-26 VTM2208 - Jun 26, 13:59 UTCJun 26, 14:09 UTC10m
2026-06-26 VTM2207 - Jun 26, 04:45 UTCJun 26, 04:55 UTC10m
2026-06-26 VTM2207 - Jun 26, 03:54 UTCJun 26, 04:04 UTC10m
2026-06-25 VTM2208 - Jun 25, 14:39 UTCJun 25, 14:50 UTC10m
2026-06-25 VTM2208 - Jun 25, 13:55 UTCJun 25, 14:04 UTC10m
2026-06-25 VTM2207 - Jun 25, 04:40 UTCJun 25, 04:54 UTC15m
2026-06-25 VTM2207 - Jun 25, 03:15 UTCJun 25, 03:50 UTC35m
2026-06-24 VTM2208 - Jun 24, 14:45 UTCJun 24, 14:55 UTC10m
2026-06-24 VTM2208 - Jun 24, 13:54 UTCJun 24, 14:00 UTC5m
2026-06-24 VTM2207 - Jun 24, 04:50 UTCJun 24, 04:59 UTC10m

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

Mode-S 0D0FFB frequently asked

What is Mode-S code 0D0FFB?
0D0FFB is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VHB.
Where is Mode-S 0D0FFB registered?
Mode-S code 0D0FFB is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0FFB broadcasting right now?
No active broadcast right now. Last signal was 13h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0FFB, octal 03207773, decimal 856,059.
What flights does 0D0FFB operate?
Mode-S 0D0FFB has broadcast 11 distinct callsigns, including VTM2208, VTM2207, VTM2203, VTM2202, VTM7701.