Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0DF4

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XB-JMV

Hex
0D0DF4
Octal
03206764
Decimal
855,540
Country
MX
Tail
XB-JMV
Type
C172
No current signal · last broadcast 20d ago
Flights observed
163
Distinct callsigns
1
Country
MX
Last broadcast
20d ago

Last known position

Most recent position reported by Mode-S 0D0DF4.

Country allocation

The ICAO 24-bit address 0D0DF4 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 1 distinct

Callsign Airline Flights Last seen
XBJMV - 163 2026-06-27

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-27 XBJMV - Jun 27, 16:24 UTCJun 27, 17:49 UTC1h 25m
2026-06-27 XBJMV CVJ → CVJ Jun 27, 14:00 UTCJun 27, 15:34 UTC1h 35m
2026-06-25 XBJMV - Jun 25, 20:59 UTCJun 25, 21:59 UTC1h 0m
2026-06-25 XBJMV CVJ → CVJ Jun 25, 19:24 UTCJun 25, 20:25 UTC1h 0m
2026-06-25 XBJMV - Jun 25, 16:24 UTCJun 25, 18:00 UTC1h 35m
2026-06-25 XBJMV CVJ → CVJ Jun 25, 14:24 UTCJun 25, 15:50 UTC1h 25m
2026-06-24 XBJMV - Jun 24, 19:55 UTCJun 24, 22:04 UTC2h 10m
2026-06-24 XBJMV - Jun 24, 18:15 UTCJun 24, 19:39 UTC1h 25m
2026-06-24 XBJMV - Jun 24, 15:59 UTCJun 24, 17:55 UTC1h 55m
2026-06-24 XBJMV CVJ → CVJ Jun 24, 13:54 UTCJun 24, 15:35 UTC1h 40m
2026-06-21 XBJMV - Jun 21, 21:05 UTCJun 21, 23:24 UTC2h 20m
2026-06-21 XBJMV - Jun 21, 19:05 UTCJun 21, 20:34 UTC1h 30m
2026-06-20 XBJMV - Jun 20, 21:10 UTCJun 20, 22:54 UTC1h 45m
2026-06-20 XBJMV CVJ → CVJ Jun 20, 19:34 UTCJun 20, 20:49 UTC1h 15m
2026-06-20 XBJMV - Jun 20, 16:09 UTCJun 20, 18:49 UTC2h 40m
2026-06-20 XBJMV CVJ → CVJ Jun 20, 14:29 UTCJun 20, 15:34 UTC1h 5m
2026-06-19 XBJMV CVJ → CVJ Jun 19, 21:44 UTCJun 19, 22:30 UTC45m
2026-06-19 XBJMV - Jun 19, 19:45 UTCJun 19, 21:19 UTC1h 35m
2026-06-19 XBJMV CVJ → CVJ Jun 19, 17:19 UTCJun 19, 19:34 UTC2h 15m
2026-06-19 XBJMV CVJ → CVJ Jun 19, 15:39 UTCJun 19, 16:49 UTC1h 10m
2026-06-19 XBJMV CVJ → CVJ Jun 19, 14:04 UTCJun 19, 15:09 UTC1h 5m
2026-06-18 XBJMV CVJ → CVJ Jun 18, 22:30 UTCJun 18, 23:40 UTC1h 10m
2026-06-14 XBJMV CVJ → CVJ Jun 14, 14:10 UTCJun 14, 15:05 UTC55m
2026-06-13 XBJMV - Jun 13, 22:05 UTCJun 13, 23:40 UTC1h 35m
2026-06-13 XBJMV CVJ → CVJ Jun 13, 21:10 UTCJun 13, 21:45 UTC35m
2026-06-13 XBJMV - Jun 13, 17:00 UTCJun 13, 18:05 UTC1h 5m
2026-06-13 XBJMV CVJ → CVJ Jun 13, 15:15 UTCJun 13, 16:30 UTC1h 15m
2026-06-12 XBJMV - Jun 12, 13:55 UTCJun 12, 15:00 UTC1h 5m
2026-06-11 XBJMV CVJ → CVJ Jun 11, 22:00 UTCJun 11, 23:10 UTC1h 10m
2026-06-11 XBJMV CVJ → CVJ Jun 11, 20:35 UTCJun 11, 21:35 UTC1h 0m
2026-06-11 XBJMV CVJ → CVJ Jun 11, 15:40 UTCJun 11, 16:45 UTC1h 5m
2026-05-31 XBJMV CVJ → CVJ May 31, 19:25 UTCMay 31, 21:45 UTC2h 20m
2026-05-31 XBJMV - May 31, 17:10 UTCMay 31, 18:40 UTC1h 30m
2026-05-31 XBJMV - May 31, 15:20 UTCMay 31, 16:35 UTC1h 15m
2026-05-31 XBJMV CVJ → CVJ May 31, 13:55 UTCMay 31, 15:00 UTC1h 5m
2026-05-30 XBJMV CVJ → CVJ May 30, 20:25 UTCMay 30, 21:40 UTC1h 15m
2026-05-30 XBJMV - May 30, 18:25 UTCMay 30, 20:00 UTC1h 35m
2026-05-30 XBJMV - May 30, 15:50 UTCMay 30, 18:05 UTC2h 15m
2026-05-30 XBJMV CVJ → CVJ May 30, 13:45 UTCMay 30, 15:25 UTC1h 40m
2026-05-29 XBJMV CVJ → CVJ May 29, 21:30 UTCMay 29, 22:45 UTC1h 15m
2026-05-29 XBJMV CVJ → CVJ May 29, 20:45 UTCMay 29, 21:15 UTC30m
2026-05-29 XBJMV CVJ → CVJ May 29, 19:05 UTCMay 29, 19:50 UTC45m
2026-05-29 XBJMV - May 29, 16:55 UTCMay 29, 18:05 UTC1h 10m
2026-05-29 XBJMV CVJ → CVJ May 29, 14:55 UTCMay 29, 16:25 UTC1h 30m
2026-05-28 XBJMV - May 28, 22:00 UTCMay 28, 23:30 UTC1h 30m
2026-05-28 XBJMV - May 28, 20:35 UTCMay 28, 21:45 UTC1h 10m
2026-05-28 XBJMV CVJ → CVJ May 28, 18:50 UTCMay 28, 20:05 UTC1h 15m
2026-05-27 XBJMV - May 27, 22:15 UTCMay 27, 22:50 UTC35m
2026-05-27 XBJMV CVJ → CVJ May 27, 20:40 UTCMay 27, 21:45 UTC1h 5m
2026-05-27 XBJMV CVJ → CVJ May 27, 19:05 UTCMay 27, 20:05 UTC1h 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 XB-JMV page for operator, model, and routing details .

Mode-S 0D0DF4 frequently asked

What is Mode-S code 0D0DF4?
0D0DF4 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XB-JMV.
Where is Mode-S 0D0DF4 registered?
Mode-S code 0D0DF4 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0DF4 broadcasting right now?
No active broadcast right now. Last signal was 20d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0DF4, octal 03206764, decimal 855,540.
What flights does 0D0DF4 operate?
Mode-S 0D0DF4 has broadcast 1 distinct callsign, including XBJMV.