Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0B20

ICAO 24-bit transponder address · allocated to Mexico

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

Hex
0D0B20
Octal
03205440
Decimal
854,816
Country
MX
Tail
XA-VBF
Type
CRJ2
No current signal · last broadcast 2d ago
Flights observed
126
Distinct callsigns
1
Country
MX
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 0D0B20.

Country allocation

The ICAO 24-bit address 0D0B20 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
VTM356 - 126 2026-07-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 VTM356 - Jul 17, 20:04 UTCJul 17, 23:25 UTC3h 20m
2026-07-17 VTM356 - Jul 17, 16:24 UTCJul 17, 17:20 UTC55m
2026-07-15 VTM356 - Jul 15, 22:25 UTCJul 16, 01:50 UTC3h 25m
2026-07-15 VTM356 - Jul 15, 13:05 UTCJul 15, 21:30 UTC8h 25m
2026-07-15 VTM356 - Jul 15, 11:05 UTCJul 15, 11:50 UTC45m
2026-07-14 VTM356 - Jul 14, 04:40 UTCJul 14, 08:05 UTC3h 25m
2026-07-14 VTM356 - Jul 14, 02:45 UTCJul 14, 03:25 UTC40m
2026-07-12 VTM356 - Jul 12, 23:05 UTCJul 12, 23:15 UTC10m
2026-07-11 VTM356 - Jul 11, 17:45 UTCJul 11, 21:05 UTC3h 20m
2026-07-11 VTM356 - Jul 11, 03:15 UTCJul 11, 04:01 UTC45m
2026-07-10 VTM356 - Jul 10, 22:50 UTCJul 11, 02:10 UTC3h 20m
2026-07-10 VTM356 - Jul 10, 20:30 UTCJul 10, 21:15 UTC45m
2026-07-10 VTM356 - Jul 10, 00:05 UTCJul 10, 21:15 UTC21h 10m
2026-07-09 VTM356 - Jul 9, 22:05 UTCJul 10, 21:15 UTC23h 10m
2026-07-09 VTM356 - Jul 9, 21:05 UTCJul 10, 00:25 UTC3h 20m
2026-07-09 VTM356 IAG → TOL Jul 9, 16:40 UTCJul 9, 17:30 UTC50m
2026-07-08 VTM356 - Jul 8, 21:05 UTCJul 9, 00:30 UTC3h 25m
2026-07-08 VTM356 - Jul 8, 16:35 UTCJul 8, 19:50 UTC3h 15m
2026-07-03 VTM356 - Jul 3, 16:40 UTCJul 3, 19:25 UTC2h 45m
2026-07-02 VTM356 - Jul 2, 19:50 UTCJul 2, 22:15 UTC2h 25m
2026-07-02 VTM356 - Jul 2, 17:10 UTCJul 2, 18:35 UTC1h 25m
2026-07-02 VTM356 - Jul 2, 14:10 UTCJul 2, 15:10 UTC1h 0m
2026-06-30 VTM356 - Jun 30, 20:55 UTCJul 1, 00:35 UTC3h 40m
2026-06-30 VTM356 - Jun 30, 15:25 UTCJun 30, 18:45 UTC3h 20m
2026-06-29 VTM356 - Jun 29, 20:04 UTCJun 30, 14:10 UTC18h 6m
2026-06-29 VTM356 - Jun 29, 19:49 UTCJun 30, 14:10 UTC18h 21m
2026-06-27 VTM356 - Jun 27, 18:09 UTCJun 27, 21:19 UTC3h 10m
2026-06-27 VTM356 - Jun 27, 16:30 UTCJun 27, 17:20 UTC50m
2026-06-26 VTM356 LRD → BUF Jun 26, 04:30 UTCJun 26, 07:55 UTC3h 25m
2026-06-25 VTM356 - Jun 25, 19:24 UTCJun 26, 03:34 UTC8h 10m
2026-06-25 VTM356 - Jun 25, 17:09 UTCJun 25, 18:00 UTC50m
2026-06-24 VTM356 LRD → IAG Jun 24, 05:34 UTCJun 24, 08:55 UTC3h 20m
2026-06-23 VTM356 - Jun 23, 22:40 UTCJun 24, 04:20 UTC5h 40m
2026-06-23 VTM356 LRD → BMI Jun 23, 03:45 UTCJun 23, 07:05 UTC3h 20m
2026-06-23 VTM356 - Jun 23, 02:15 UTCJun 23, 02:40 UTC25m
2026-06-23 VTM356 - Jun 23, 00:35 UTCJun 23, 01:00 UTC25m
2026-06-20 VTM356 - Jun 20, 19:40 UTCJun 20, 21:44 UTC2h 5m
2026-06-20 VTM356 - Jun 20, 16:55 UTCJun 20, 17:59 UTC1h 5m
2026-06-19 VTM356 - Jun 19, 06:29 UTCJun 19, 08:54 UTC2h 25m
2026-06-19 VTM356 - Jun 19, 03:39 UTCJun 19, 04:14 UTC35m
2026-06-17 VTM356 - Jun 17, 14:00 UTCJun 17, 14:35 UTC35m
2026-06-16 VTM356 - Jun 16, 21:25 UTCJun 17, 00:00 UTC2h 35m
2026-06-16 VTM356 - Jun 16, 05:20 UTCJun 16, 07:34 UTC2h 15m
2026-06-16 VTM356 - Jun 16, 02:40 UTCJun 16, 03:55 UTC1h 15m
2026-06-15 VTM356 - Jun 15, 20:54 UTCJun 15, 21:09 UTC15m
2026-06-14 VTM356 - Jun 14, 00:05 UTCJun 14, 01:10 UTC1h 5m
2026-06-13 VTM356 - Jun 13, 19:35 UTCJun 13, 21:45 UTC2h 10m
2026-06-13 VTM356 LRD → OAK Jun 13, 06:25 UTCJun 13, 09:45 UTC3h 20m
2026-06-13 VTM356 - Jun 13, 04:15 UTCJun 13, 04:55 UTC40m
2026-06-11 VTM356 - Jun 11, 18:25 UTCJun 11, 19:55 UTC1h 30m

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

Mode-S 0D0B20 frequently asked

What is Mode-S code 0D0B20?
0D0B20 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VBF.
Where is Mode-S 0D0B20 registered?
Mode-S code 0D0B20 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0B20 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 0D0B20, octal 03205440, decimal 854,816.
What flights does 0D0B20 operate?
Mode-S 0D0B20 has broadcast 1 distinct callsign, including VTM356.