sensors Mode-S transponder
0D0FC0
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VGY
- Hex
- 0D0FC0
- Octal
- 03207700
- Decimal
- 856,000
- Country
- MX
- Tail
- XA-VGY
- Type
- B734
- Flights observed
- 65
- Distinct callsigns
- 14
- Country
- MX
- Last broadcast
- 41m ago
Current position
Country allocation
The ICAO 24-bit address 0D0FC0 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VTM5001 | - | 14 | 2026-07-17 |
| VTM5002 | - | 9 | 2026-07-15 |
| VTM9902 | - | 7 | 2026-07-09 |
| VTM4401 | - | 7 | 2026-06-20 |
| VTM9901 | - | 5 | 2026-07-10 |
| VTM4402 | - | 5 | 2026-06-19 |
| VTM1102 | - | 4 | 2026-06-17 |
| VTM8802 | - | 3 | 2026-06-05 |
| VTM8801 | - | 3 | 2026-06-09 |
| VTM848 | - | 2 | 2026-06-09 |
| VTM6602 | - | 2 | 2026-06-27 |
| VTM1101 | - | 2 | 2026-06-18 |
| VTM2203 | - | 1 | 2026-06-02 |
| VTM2022 | - | 1 | 2026-06-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | VTM5001 | - | Jul 17, 04:25 UTC | Jul 18, 03:50 UTC | 23h 26m |
| 2026-07-16 | VTM5001 | - | Jul 16, 11:45 UTC | Jul 17, 03:30 UTC | 15h 45m |
| 2026-07-16 | VTM5001 | MTY → MTY | Jul 16, 04:30 UTC | Jul 17, 03:30 UTC | 23h 0m |
| 2026-07-15 | VTM5001 | - | Jul 15, 11:50 UTC | Jul 16, 03:40 UTC | 15h 50m |
| 2026-07-15 | VTM5002 | MTY → MTY | Jul 15, 04:30 UTC | Jul 16, 03:40 UTC | 23h 10m |
| 2026-07-14 | VTM5002 | - | Jul 14, 12:00 UTC | Jul 15, 03:50 UTC | 15h 49m |
| 2026-07-12 | VTM5002 | - | Jul 12, 04:10 UTC | Jul 12, 04:30 UTC | 20m |
| 2026-07-11 | VTM5002 | - | Jul 11, 11:55 UTC | Jul 12, 03:35 UTC | 15h 40m |
| 2026-07-11 | VTM5002 | - | Jul 11, 04:55 UTC | Jul 12, 03:35 UTC | 22h 40m |
| 2026-07-10 | VTM5001 | - | Jul 10, 11:55 UTC | Jul 11, 04:05 UTC | 16h 10m |
| 2026-07-10 | VTM9901 | - | Jul 10, 01:40 UTC | Jul 10, 02:00 UTC | 20m |
| 2026-07-09 | VTM9902 | - | Jul 9, 13:35 UTC | Jul 9, 14:05 UTC | 30m |
| 2026-07-09 | VTM9902 | - | Jul 9, 04:30 UTC | Jul 9, 12:10 UTC | 7h 40m |
| 2026-07-08 | VTM5001 | - | Jul 8, 12:15 UTC | Jul 9, 03:45 UTC | 15h 30m |
| 2026-07-08 | VTM5001 | MTY → MTY | Jul 8, 04:40 UTC | Jul 9, 03:45 UTC | 23h 5m |
| 2026-07-07 | VTM5001 | - | Jul 7, 12:50 UTC | Jul 8, 03:45 UTC | 14h 55m |
| 2026-07-01 | VTM9901 | - | Jul 1, 04:20 UTC | Jul 1, 04:50 UTC | 30m |
| 2026-07-01 | VTM9901 | - | Jul 1, 01:35 UTC | Jul 1, 02:00 UTC | 25m |
| 2026-06-30 | VTM9902 | - | Jun 30, 13:10 UTC | Jun 30, 13:35 UTC | 25m |
| 2026-06-30 | VTM9902 | - | Jun 30, 10:55 UTC | Jun 30, 11:40 UTC | 45m |
| 2026-06-27 | VTM6602 | - | Jun 27, 13:24 UTC | Jun 27, 13:44 UTC | 20m |
| 2026-06-27 | VTM5001 | MTY → HMO | Jun 27, 04:59 UTC | Jun 27, 12:50 UTC | 7h 50m |
| 2026-06-27 | VTM5001 | - | Jun 27, 03:34 UTC | Jun 27, 04:09 UTC | 35m |
| 2026-06-26 | VTM5002 | - | Jun 26, 13:49 UTC | Jun 26, 14:09 UTC | 20m |
| 2026-06-26 | VTM9901 | - | Jun 26, 04:10 UTC | Jun 26, 13:04 UTC | 8h 55m |
| 2026-06-26 | VTM9901 | - | Jun 26, 01:39 UTC | Jun 26, 02:00 UTC | 20m |
| 2026-06-25 | VTM9902 | - | Jun 25, 12:15 UTC | Jun 25, 12:40 UTC | 25m |
| 2026-06-25 | VTM9902 | - | Jun 25, 10:09 UTC | Jun 25, 10:45 UTC | 35m |
| 2026-06-24 | VTM9902 | - | Jun 24, 13:24 UTC | Jun 25, 10:45 UTC | 21h 20m |
| 2026-06-24 | VTM6602 | - | Jun 24, 12:09 UTC | Jun 24, 12:25 UTC | 15m |
| 2026-06-24 | VTM5001 | - | Jun 24, 04:39 UTC | Jun 24, 04:59 UTC | 20m |
| 2026-06-24 | VTM5001 | - | Jun 24, 02:49 UTC | Jun 24, 03:29 UTC | 40m |
| 2026-06-23 | VTM5002 | - | Jun 23, 13:55 UTC | Jun 23, 14:15 UTC | 20m |
| 2026-06-23 | VTM5002 | - | Jun 23, 12:09 UTC | Jun 23, 13:15 UTC | 1h 5m |
| 2026-06-21 | VTM5001 | - | Jun 21, 04:44 UTC | Jun 21, 05:10 UTC | 25m |
| 2026-06-21 | VTM5001 | - | Jun 21, 02:50 UTC | Jun 21, 03:25 UTC | 35m |
| 2026-06-20 | VTM5002 | - | Jun 20, 13:55 UTC | Jun 20, 14:14 UTC | 20m |
| 2026-06-20 | VTM4401 | - | Jun 20, 00:59 UTC | Jun 20, 13:14 UTC | 12h 15m |
| 2026-06-19 | VTM4402 | - | Jun 19, 12:54 UTC | Jun 19, 14:09 UTC | 1h 15m |
| 2026-06-18 | VTM1101 | - | Jun 18, 02:35 UTC | Jun 18, 03:45 UTC | 1h 10m |
| 2026-06-17 | VTM1102 | - | Jun 17, 14:15 UTC | Jun 17, 15:00 UTC | 45m |
| 2026-06-17 | VTM1102 | - | Jun 17, 13:10 UTC | Jun 17, 13:25 UTC | 15m |
| 2026-06-17 | VTM1101 | - | Jun 17, 02:30 UTC | Jun 17, 03:40 UTC | 1h 10m |
| 2026-06-16 | VTM1102 | - | Jun 16, 14:15 UTC | Jun 16, 15:00 UTC | 45m |
| 2026-06-16 | VTM1102 | - | Jun 16, 13:04 UTC | Jun 16, 13:19 UTC | 15m |
| 2026-06-16 | VTM4401 | - | Jun 16, 00:55 UTC | Jun 16, 02:00 UTC | 1h 5m |
| 2026-06-15 | VTM4401 | - | Jun 15, 01:00 UTC | Jun 15, 15:15 UTC | 14h 15m |
| 2026-06-14 | VTM4401 | - | Jun 14, 00:55 UTC | Jun 14, 15:10 UTC | 14h 15m |
| 2026-06-13 | VTM4402 | - | Jun 13, 13:50 UTC | Jun 13, 14:50 UTC | 1h 0m |
| 2026-06-12 | VTM4402 | - | Jun 12, 14:05 UTC | Jun 13, 14:00 UTC | 23h 54m |
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-VGY page for operator, model, and routing details .