sensors Mode-S transponder
0D0D7E
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-TIF · BOEING 737-400
- Hex
- 0D0D7E
- Octal
- 03206576
- Decimal
- 855,422
- Country
- MX
- Tail
- XA-TIF
- Type
- B734
- Flights observed
- 35
- Distinct callsigns
- 11
- Country
- MX
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0D7E 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 11 distinct
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VTM5001 | - | Jun 2, 18:30 UTC | Jun 2, 19:40 UTC | 1h 10m |
| 2026-06-02 | VTM5002 | - | Jun 2, 05:20 UTC | Jun 2, 17:00 UTC | 11h 40m |
| 2026-05-31 | VTM9902 | - | May 31, 10:20 UTC | May 31, 11:10 UTC | 50m |
| 2026-05-30 | VTM3907 | - | May 30, 02:40 UTC | May 30, 15:00 UTC | 12h 20m |
| 2026-05-29 | VTM3908 | - | May 29, 15:25 UTC | May 29, 15:50 UTC | 25m |
| 2026-05-22 | VTM1102 | - | May 22, 01:40 UTC | May 22, 02:00 UTC | 20m |
| 2026-05-21 | VTM1102 | - | May 21, 13:10 UTC | May 21, 13:25 UTC | 15m |
| 2026-05-21 | VTM1101 | - | May 21, 01:50 UTC | May 21, 02:05 UTC | 15m |
| 2026-05-20 | VTM1102 | - | May 20, 12:55 UTC | May 20, 13:10 UTC | 15m |
| 2026-05-20 | VTM9904 | - | May 20, 03:40 UTC | May 20, 04:45 UTC | 1h 6m |
| 2026-05-19 | VTM9905 | - | May 19, 11:10 UTC | May 19, 12:00 UTC | 50m |
| 2026-05-14 | VTM9905 | - | May 14, 10:05 UTC | May 15, 04:25 UTC | 18h 20m |
| 2026-05-14 | VTM9905 | - | May 14, 04:30 UTC | May 14, 10:50 UTC | 6h 20m |
| 2026-05-13 | VTM9905 | - | May 13, 10:20 UTC | May 14, 04:45 UTC | 18h 25m |
| 2026-05-13 | VTM9905 | - | May 13, 04:10 UTC | May 13, 11:05 UTC | 6h 55m |
| 2026-05-12 | VTM9905 | - | May 12, 10:15 UTC | May 13, 04:40 UTC | 18h 25m |
| 2026-05-08 | VTM9905 | - | May 8, 10:59 UTC | May 9, 04:45 UTC | 17h 45m |
| 2026-05-08 | VTM9905 | - | May 8, 02:59 UTC | May 8, 11:44 UTC | 8h 45m |
| 2026-05-07 | VTM1102 | - | May 7, 13:50 UTC | May 7, 14:30 UTC | 40m |
| 2026-05-07 | VTM1102 | - | May 7, 12:50 UTC | May 7, 13:10 UTC | 20m |
| 2026-04-29 | VTM1101 | - | Apr 29, 02:30 UTC | Apr 29, 02:45 UTC | 15m |
| 2026-04-28 | VTM1102 | - | Apr 28, 13:15 UTC | Apr 28, 13:30 UTC | 15m |
| 2026-04-24 | VTM1101 | - | Apr 24, 03:10 UTC | Apr 24, 04:15 UTC | 1h 5m |
| 2026-04-23 | VTM1102 | - | Apr 23, 14:25 UTC | Apr 23, 15:15 UTC | 50m |
| 2026-04-23 | VTM1102 | - | Apr 23, 13:00 UTC | Apr 23, 13:20 UTC | 20m |
| 2026-04-22 | VTM1101 | - | Apr 22, 03:10 UTC | Apr 22, 04:10 UTC | 1h 0m |
| 2026-04-21 | VTM1102 | - | Apr 21, 14:15 UTC | Apr 21, 15:05 UTC | 50m |
| 2026-04-21 | VTM1102 | - | Apr 21, 12:50 UTC | Apr 21, 13:10 UTC | 20m |
| 2026-04-21 | VTM8801 | - | Apr 21, 06:00 UTC | Apr 21, 06:20 UTC | 20m |
| 2026-04-21 | VTM151 | - | Apr 21, 03:05 UTC | Apr 21, 03:35 UTC | 30m |
| 2026-04-18 | VTM151 | - | Apr 18, 17:00 UTC | Apr 18, 18:20 UTC | 1h 20m |
| 2026-04-18 | VTM151 | - | Apr 18, 13:40 UTC | Apr 18, 14:10 UTC | 30m |
| 2026-04-18 | VTM151 | - | Apr 18, 10:00 UTC | Apr 18, 12:30 UTC | 2h 30m |
| 2026-04-18 | VTM151 | - | Apr 18, 01:25 UTC | Apr 18, 03:20 UTC | 1h 55m |
| 2026-04-17 | VTM151 | - | Apr 17, 23:50 UTC | Apr 18, 00:20 UTC | 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-TIF page for operator, model, and routing details .