Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0EFB

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VGC · BOMBARDIER Regional Jet CRJ-200

Hex
0D0EFB
Octal
03207373
Decimal
855,803
Country
MX
Tail
XA-VGC
Type
CRJ2
No current signal · last broadcast 3d ago
Flights observed
109
Distinct callsigns
2
Country
MX
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S 0D0EFB.

Country allocation

The ICAO 24-bit address 0D0EFB 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
VTM599 - 108 2026-07-25
VTM399 - 1 2026-05-28

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-25 VTM599 - Jul 25, 05:50 UTCJul 25, 06:25 UTC35m
2026-07-25 VTM599 - Jul 25, 01:40 UTCJul 25, 04:45 UTC3h 5m
2026-07-24 VTM599 - Jul 24, 22:45 UTCJul 25, 00:15 UTC1h 30m
2026-07-23 VTM599 LRD → CVG Jul 23, 06:30 UTCJul 23, 09:05 UTC2h 35m
2026-07-23 VTM599 - Jul 23, 04:25 UTCJul 23, 05:15 UTC50m
2026-07-22 VTM599 - Jul 22, 23:00 UTCJul 22, 23:15 UTC15m
2026-07-21 VTM599 - Jul 21, 11:15 UTCJul 21, 11:25 UTC10m
2026-07-21 VTM599 - Jul 21, 08:15 UTCJul 21, 08:50 UTC35m
2026-07-21 VTM599 - Jul 21, 04:00 UTCJul 21, 07:10 UTC3h 10m
2026-07-20 VTM599 - Jul 20, 23:05 UTCJul 21, 02:20 UTC3h 14m
2026-07-20 VTM599 - Jul 20, 20:40 UTCJul 20, 21:10 UTC30m
2026-07-17 VTM599 - Jul 17, 18:29 UTCJul 17, 18:44 UTC15m
2026-07-17 VTM599 - Jul 17, 17:20 UTCJul 17, 17:25 UTC5m
2026-07-17 VTM599 - Jul 17, 01:49 UTCJul 17, 02:54 UTC1h 5m
2026-07-16 VTM599 - Jul 16, 23:35 UTCJul 17, 00:35 UTC1h 0m
2026-07-15 VTM599 - Jul 15, 04:25 UTCJul 15, 05:00 UTC35m
2026-07-15 VTM599 - Jul 15, 00:20 UTCJul 15, 03:30 UTC3h 10m
2026-07-14 VTM599 - Jul 14, 22:35 UTCJul 14, 22:50 UTC14m
2026-07-13 VTM599 - Jul 13, 22:20 UTCJul 14, 01:30 UTC3h 10m
2026-07-12 VTM599 - Jul 12, 16:05 UTCJul 12, 16:35 UTC30m
2026-07-03 VTM599 - Jul 3, 16:15 UTCJul 3, 19:00 UTC2h 45m
2026-07-01 VTM599 - Jul 1, 22:00 UTCJul 2, 00:30 UTC2h 30m
2026-07-01 VTM599 - Jul 1, 19:15 UTCJul 1, 20:30 UTC1h 15m
2026-07-01 VTM599 - Jul 1, 14:00 UTCJul 1, 14:40 UTC40m
2026-07-01 VTM599 - Jul 1, 04:20 UTCJul 1, 07:35 UTC3h 15m
2026-06-30 VTM599 - Jun 30, 08:40 UTCJun 30, 12:05 UTC3h 25m
2026-06-30 VTM599 - Jun 30, 03:50 UTCJun 30, 04:25 UTC35m
2026-06-30 VTM599 - Jun 30, 02:45 UTCJun 30, 02:55 UTC10m
2026-06-29 VTM599 - Jun 29, 22:44 UTCJun 29, 22:49 UTC5m
2026-06-29 VTM599 - Jun 29, 21:19 UTCJun 29, 21:44 UTC25m
2026-06-26 VTM599 - Jun 26, 16:09 UTCJun 26, 19:39 UTC3h 30m
2026-06-25 VTM599 LRD → YQG Jun 25, 22:20 UTCJun 26, 01:24 UTC3h 5m
2026-06-25 VTM599 LRD → LRD Jun 25, 15:29 UTCJun 25, 21:10 UTC5h 40m
2026-06-24 VTM599 - Jun 24, 23:20 UTCJun 25, 02:25 UTC3h 5m
2026-06-24 VTM599 - Jun 24, 19:24 UTCJun 24, 22:25 UTC3h 0m
2026-06-24 VTM599 - Jun 24, 17:50 UTCJun 24, 18:20 UTC30m
2026-06-23 VTM599 - Jun 23, 21:59 UTCJun 24, 00:40 UTC2h 40m
2026-06-23 VTM599 LRD → CLU Jun 23, 06:09 UTCJun 23, 08:45 UTC2h 35m
2026-06-23 VTM599 - Jun 23, 03:49 UTCJun 23, 05:00 UTC1h 10m
2026-06-20 VTM599 - Jun 20, 14:05 UTCJun 20, 17:29 UTC3h 25m
2026-06-19 VTM599 - Jun 19, 04:00 UTCJun 19, 04:10 UTC10m
2026-06-18 VTM599 LRD → YQG Jun 18, 23:00 UTCJun 19, 02:04 UTC3h 4m
2026-06-18 VTM599 - Jun 18, 13:25 UTCJun 18, 21:05 UTC7h 40m
2026-06-17 VTM599 - Jun 17, 08:55 UTCJun 17, 11:15 UTC2h 20m
2026-06-17 VTM599 MTY → LRD Jun 17, 07:35 UTCJun 17, 08:00 UTC25m
2026-06-17 VTM599 - Jun 17, 04:15 UTCJun 17, 05:40 UTC1h 25m
2026-06-15 VTM599 - Jun 15, 19:35 UTCJun 15, 21:09 UTC1h 35m
2026-06-15 VTM599 - Jun 15, 16:30 UTCJun 15, 17:25 UTC55m
2026-06-14 VTM599 - Jun 14, 17:00 UTCJun 14, 18:00 UTC1h 0m
2026-06-13 VTM599 - Jun 13, 19:20 UTCJun 13, 21:45 UTC2h 25m

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

Mode-S 0D0EFB frequently asked

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