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
- Flights observed
- 66
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 5h ago
Last known position
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 | - | 66 | 2026-06-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | VTM356 | - | Jun 3, 18:30 UTC | Jun 3, 21:20 UTC | 2h 50m |
| 2026-06-03 | VTM356 | LRD → SDF | Jun 3, 00:10 UTC | Jun 3, 02:35 UTC | 2h 25m |
| 2026-06-02 | VTM356 | - | Jun 2, 22:15 UTC | Jun 2, 22:55 UTC | 40m |
| 2026-06-02 | VTM356 | - | Jun 2, 18:40 UTC | Jun 2, 18:50 UTC | 10m |
| 2026-05-31 | VTM356 | - | May 31, 17:05 UTC | May 31, 17:30 UTC | 25m |
| 2026-05-29 | VTM356 | - | May 29, 23:10 UTC | May 29, 23:50 UTC | 40m |
| 2026-05-29 | VTM356 | - | May 29, 20:25 UTC | May 29, 20:35 UTC | 10m |
| 2026-05-27 | VTM356 | - | May 27, 23:25 UTC | May 27, 23:40 UTC | 15m |
| 2026-05-23 | VTM356 | - | May 23, 23:50 UTC | May 24, 00:20 UTC | 30m |
| 2026-05-23 | VTM356 | - | May 23, 19:00 UTC | May 23, 22:35 UTC | 3h 35m |
| 2026-05-21 | VTM356 | LRD → IAG | May 21, 13:30 UTC | May 21, 16:40 UTC | 3h 10m |
| 2026-05-21 | VTM356 | - | May 21, 11:55 UTC | May 21, 12:25 UTC | 30m |
| 2026-05-19 | VTM356 | - | May 19, 18:00 UTC | May 19, 21:45 UTC | 3h 45m |
| 2026-05-19 | VTM356 | - | May 19, 16:25 UTC | May 19, 17:15 UTC | 50m |
| 2026-05-18 | VTM356 | - | May 18, 21:40 UTC | May 19, 00:55 UTC | 3h 15m |
| 2026-05-18 | VTM356 | - | May 18, 16:00 UTC | May 18, 20:50 UTC | 4h 49m |
| 2026-05-17 | VTM356 | - | May 17, 12:01 UTC | May 17, 13:05 UTC | 1h 5m |
| 2026-05-17 | VTM356 | - | May 17, 09:15 UTC | May 17, 11:20 UTC | 2h 5m |
| 2026-05-17 | VTM356 | - | May 17, 07:25 UTC | May 17, 08:10 UTC | 45m |
| 2026-05-16 | VTM356 | - | May 16, 19:10 UTC | May 16, 21:10 UTC | 2h 0m |
| 2026-05-16 | VTM356 | - | May 16, 14:16 UTC | May 16, 16:50 UTC | 2h 35m |
| 2026-05-15 | VTM356 | - | May 15, 06:10 UTC | May 15, 09:30 UTC | 3h 20m |
| 2026-05-15 | VTM356 | LRD → LRD | May 15, 01:20 UTC | May 15, 04:55 UTC | 3h 35m |
| 2026-05-14 | VTM356 | - | May 14, 03:30 UTC | May 14, 05:55 UTC | 2h 25m |
| 2026-05-14 | VTM356 | - | May 14, 00:10 UTC | May 14, 02:40 UTC | 2h 30m |
| 2026-05-13 | VTM356 | - | May 13, 22:15 UTC | May 13, 23:00 UTC | 45m |
| 2026-05-12 | VTM356 | - | May 12, 21:25 UTC | May 12, 23:30 UTC | 2h 5m |
| 2026-05-12 | VTM356 | - | May 12, 18:10 UTC | May 12, 20:35 UTC | 2h 25m |
| 2026-05-12 | VTM356 | - | May 12, 02:45 UTC | May 12, 03:00 UTC | 15m |
| 2026-05-11 | VTM356 | - | May 11, 17:20 UTC | May 11, 22:35 UTC | 5h 14m |
| 2026-05-11 | VTM356 | - | May 11, 00:05 UTC | May 11, 02:25 UTC | 2h 20m |
| 2026-05-10 | VTM356 | LRD → CHA | May 10, 20:30 UTC | May 10, 22:30 UTC | 2h 0m |
| 2026-05-10 | VTM356 | - | May 10, 19:00 UTC | May 10, 19:35 UTC | 35m |
| 2026-05-09 | VTM356 | - | May 9, 20:05 UTC | May 10, 19:35 UTC | 23h 30m |
| 2026-05-09 | VTM356 | - | May 9, 18:25 UTC | May 9, 20:05 UTC | 1h 40m |
| 2026-05-09 | VTM356 | - | May 9, 16:20 UTC | May 9, 17:40 UTC | 1h 20m |
| 2026-05-08 | VTM356 | - | May 8, 06:25 UTC | May 8, 08:14 UTC | 1h 50m |
| 2026-05-08 | VTM356 | - | May 8, 04:34 UTC | May 8, 05:09 UTC | 35m |
| 2026-05-07 | VTM356 | - | May 7, 18:45 UTC | May 7, 23:05 UTC | 4h 20m |
| 2026-05-07 | VTM356 | IAG → YIP | May 7, 16:30 UTC | May 7, 17:25 UTC | 55m |
| 2026-05-06 | VTM356 | - | May 6, 22:45 UTC | May 7, 01:35 UTC | 2h 50m |
| 2026-05-06 | VTM356 | - | May 6, 20:50 UTC | May 6, 21:25 UTC | 35m |
| 2026-05-05 | VTM356 | - | May 5, 17:10 UTC | May 5, 19:40 UTC | 2h 30m |
| 2026-05-04 | VTM356 | LRD → MQY | May 4, 22:35 UTC | May 5, 00:40 UTC | 2h 5m |
| 2026-05-04 | VTM356 | - | May 4, 21:10 UTC | May 4, 21:45 UTC | 35m |
| 2026-05-02 | VTM356 | - | May 2, 20:55 UTC | May 2, 21:30 UTC | 35m |
| 2026-05-02 | VTM356 | - | May 2, 16:40 UTC | May 2, 19:45 UTC | 3h 5m |
| 2026-05-01 | VTM356 | LRD → YQG | May 1, 00:00 UTC | May 1, 02:40 UTC | 2h 40m |
| 2026-04-30 | VTM356 | - | Apr 30, 10:45 UTC | Apr 30, 13:25 UTC | 2h 40m |
| 2026-04-30 | VTM356 | LRD → SDF | Apr 30, 07:30 UTC | Apr 30, 09:45 UTC | 2h 15m |
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 .