sensors Mode-S transponder
0D1046
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VHF · BOEING 737-300
- Hex
- 0D1046
- Octal
- 03210106
- Decimal
- 856,134
- Country
- MX
- Tail
- XA-VHF
- Type
- B733
- Flights observed
- 39
- Distinct callsigns
- 14
- Country
- MX
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 0D1046 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 |
|---|---|---|---|
| VTM9905 | - | 6 | 2026-06-19 |
| VTM7521 | - | 6 | 2026-05-07 |
| VTM9902 | - | 4 | 2026-06-14 |
| VTM5002 | - | 4 | 2026-06-12 |
| VTM4402 | - | 4 | 2026-06-16 |
| VTM990 | - | 3 | 2026-05-26 |
| VTM9901 | - | 2 | 2026-06-07 |
| VTM7520 | - | 2 | 2026-05-06 |
| VTM4401 | - | 2 | 2026-06-18 |
| VTM1102 | - | 2 | 2026-06-13 |
| VTM9904 | - | 1 | 2026-06-09 |
| VTM2208 | - | 1 | 2026-06-02 |
| VTM2207 | - | 1 | 2026-06-03 |
| VTM1101 | - | 1 | 2026-06-10 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | VTM9905 | - | Jun 19, 11:24 UTC | Jun 20, 06:14 UTC | 18h 50m |
| 2026-06-19 | VTM9905 | - | Jun 19, 02:59 UTC | Jun 19, 12:19 UTC | 9h 20m |
| 2026-06-18 | VTM4401 | - | Jun 18, 00:45 UTC | Jun 18, 13:35 UTC | 12h 50m |
| 2026-06-17 | VTM4401 | - | Jun 17, 00:40 UTC | Jun 17, 14:10 UTC | 13h 30m |
| 2026-06-16 | VTM4402 | - | Jun 16, 04:39 UTC | Jun 16, 14:00 UTC | 9h 20m |
| 2026-06-14 | VTM9902 | - | Jun 14, 02:00 UTC | Jun 14, 11:25 UTC | 9h 25m |
| 2026-06-13 | VTM1102 | - | Jun 13, 12:55 UTC | Jun 13, 13:15 UTC | 20m |
| 2026-06-12 | VTM5002 | - | Jun 12, 04:25 UTC | Jun 12, 04:45 UTC | 20m |
| 2026-06-12 | VTM5002 | - | Jun 12, 03:00 UTC | Jun 12, 03:40 UTC | 40m |
| 2026-06-11 | VTM5002 | - | Jun 11, 13:45 UTC | Jun 11, 14:05 UTC | 20m |
| 2026-06-11 | VTM5002 | - | Jun 11, 12:30 UTC | Jun 11, 13:00 UTC | 30m |
| 2026-06-10 | VTM1101 | - | Jun 10, 02:15 UTC | Jun 10, 02:35 UTC | 20m |
| 2026-06-09 | VTM9904 | - | Jun 9, 05:05 UTC | Jun 9, 05:50 UTC | 45m |
| 2026-06-07 | VTM9901 | - | Jun 7, 14:20 UTC | Jun 7, 14:40 UTC | 20m |
| 2026-06-07 | VTM9902 | - | Jun 7, 12:25 UTC | Jun 7, 12:50 UTC | 25m |
| 2026-06-07 | VTM9902 | - | Jun 7, 02:14 UTC | Jun 7, 10:50 UTC | 8h 35m |
| 2026-06-06 | VTM1102 | - | Jun 6, 13:15 UTC | Jun 6, 13:34 UTC | 20m |
| 2026-06-06 | VTM9901 | - | Jun 6, 01:20 UTC | Jun 6, 02:40 UTC | 1h 20m |
| 2026-06-05 | VTM9902 | - | Jun 5, 04:15 UTC | Jun 5, 12:20 UTC | 8h 5m |
| 2026-06-04 | VTM9905 | - | Jun 4, 10:30 UTC | Jun 5, 05:00 UTC | 18h 30m |
| 2026-06-04 | VTM9905 | - | Jun 4, 05:35 UTC | Jun 5, 05:00 UTC | 23h 25m |
| 2026-06-04 | VTM9905 | - | Jun 4, 05:20 UTC | Jun 4, 11:20 UTC | 6h 0m |
| 2026-06-03 | VTM2207 | - | Jun 3, 05:05 UTC | Jun 3, 05:20 UTC | 15m |
| 2026-06-02 | VTM2208 | - | Jun 2, 14:15 UTC | Jun 2, 14:20 UTC | 5m |
| 2026-05-30 | VTM9905 | - | May 30, 00:55 UTC | May 30, 10:55 UTC | 10h 0m |
| 2026-05-29 | VTM4402 | - | May 29, 01:15 UTC | May 29, 12:05 UTC | 10h 50m |
| 2026-05-28 | VTM4402 | - | May 28, 01:20 UTC | May 28, 12:25 UTC | 11h 5m |
| 2026-05-27 | VTM4402 | - | May 27, 01:14 UTC | May 27, 12:00 UTC | 10h 45m |
| 2026-05-26 | VTM990 | - | May 26, 01:20 UTC | May 26, 14:09 UTC | 12h 50m |
| 2026-05-25 | VTM990 | - | May 25, 12:00 UTC | May 25, 12:25 UTC | 25m |
| 2026-05-25 | VTM990 | - | May 25, 09:50 UTC | May 25, 10:45 UTC | 55m |
| 2026-05-07 | VTM7521 | - | May 7, 04:10 UTC | May 7, 04:25 UTC | 15m |
| 2026-05-06 | VTM7521 | - | May 6, 13:00 UTC | May 7, 01:20 UTC | 12h 19m |
| 2026-05-06 | VTM7520 | - | May 6, 11:05 UTC | May 6, 12:10 UTC | 1h 5m |
| 2026-05-06 | VTM7521 | - | May 6, 04:45 UTC | May 6, 05:05 UTC | 20m |
| 2026-05-05 | VTM7521 | MTY → MTY | May 5, 13:10 UTC | May 5, 23:55 UTC | 10h 45m |
| 2026-05-05 | VTM7520 | - | May 5, 11:20 UTC | May 5, 12:25 UTC | 1h 5m |
| 2026-05-05 | VTM7521 | - | May 5, 05:05 UTC | May 5, 05:30 UTC | 25m |
| 2026-05-04 | VTM7521 | - | May 4, 19:30 UTC | May 5, 01:15 UTC | 5h 45m |
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-VHF page for operator, model, and routing details .