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
- 84
- Distinct callsigns
- 13
- Country
- MX
- Last broadcast
- Jul 26, 05:05 UTC
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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VTM9905 | - | 28 | 2026-07-23 |
| VTM1102 | - | 12 | 2026-06-19 |
| VTM5001 | - | 9 | 2026-07-26 |
| VTM9902 | - | 7 | 2026-07-24 |
| VTM151 | - | 6 | 2026-04-21 |
| VTM5002 | - | 5 | 2026-06-27 |
| VTM1101 | - | 5 | 2026-06-20 |
| VTM9904 | - | 4 | 2026-07-15 |
| VTM9901 | - | 3 | 2026-07-25 |
| VTMY9905 | - | 2 | 2026-06-05 |
| VTM8801 | - | 1 | 2026-04-21 |
| VTM3908 | - | 1 | 2026-05-29 |
| VTM3907 | - | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VTM5001 | - | Jul 26, 04:45 UTC | Jul 26, 05:05 UTC | 20m |
| 2026-07-25 | VTM5001 | - | Jul 25, 11:55 UTC | Jul 26, 03:40 UTC | 15h 45m |
| 2026-07-25 | VTM5001 | - | Jul 25, 05:35 UTC | Jul 26, 03:40 UTC | 22h 5m |
| 2026-07-25 | VTM9901 | - | Jul 25, 05:10 UTC | Jul 26, 03:30 UTC | 22h 20m |
| 2026-07-25 | VTM9901 | - | Jul 25, 01:40 UTC | Jul 25, 02:00 UTC | 20m |
| 2026-07-24 | VTM9902 | - | Jul 24, 12:55 UTC | Jul 24, 13:20 UTC | 25m |
| 2026-07-24 | VTM9902 | - | Jul 24, 04:25 UTC | Jul 24, 11:30 UTC | 7h 5m |
| 2026-07-23 | VTM9905 | - | Jul 23, 10:00 UTC | Jul 24, 05:00 UTC | 19h 0m |
| 2026-07-23 | VTM9905 | - | Jul 23, 04:10 UTC | Jul 23, 10:40 UTC | 6h 30m |
| 2026-07-21 | VTM9905 | - | Jul 21, 10:05 UTC | Jul 22, 04:55 UTC | 18h 50m |
| 2026-07-21 | VTM9901 | - | Jul 21, 01:50 UTC | Jul 21, 10:50 UTC | 9h 0m |
| 2026-07-20 | VTM9902 | - | Jul 20, 12:40 UTC | Jul 20, 13:05 UTC | 25m |
| 2026-07-20 | VTM5001 | - | Jul 20, 03:55 UTC | Jul 20, 11:00 UTC | 7h 5m |
| 2026-07-19 | VTM5001 | - | Jul 19, 11:45 UTC | Jul 20, 03:20 UTC | 15h 35m |
| 2026-07-17 | VTM9905 | - | Jul 17, 10:20 UTC | Jul 18, 05:10 UTC | 18h 51m |
| 2026-07-17 | VTM9905 | - | Jul 17, 04:14 UTC | Jul 17, 11:10 UTC | 6h 55m |
| 2026-07-16 | VTM9905 | - | Jul 16, 10:10 UTC | Jul 17, 04:54 UTC | 18h 45m |
| 2026-07-16 | VTM9905 | - | Jul 16, 04:25 UTC | Jul 16, 11:05 UTC | 6h 40m |
| 2026-07-15 | VTM9904 | - | Jul 15, 10:10 UTC | Jul 16, 05:00 UTC | 18h 50m |
| 2026-07-15 | VTM9904 | - | Jul 15, 05:35 UTC | Jul 16, 05:00 UTC | 23h 25m |
| 2026-07-15 | VTM9904 | - | Jul 15, 04:55 UTC | Jul 15, 11:10 UTC | 6h 15m |
| 2026-07-14 | VTM9905 | - | Jul 14, 10:20 UTC | Jul 15, 05:35 UTC | 19h 14m |
| 2026-07-08 | VTM9905 | - | Jul 8, 10:35 UTC | Jul 9, 05:05 UTC | 18h 30m |
| 2026-07-08 | VTM9905 | - | Jul 8, 04:10 UTC | Jul 8, 11:25 UTC | 7h 15m |
| 2026-07-07 | VTM9905 | - | Jul 7, 10:30 UTC | Jul 8, 04:15 UTC | 17h 45m |
| 2026-07-03 | VTM9905 | - | Jul 3, 04:20 UTC | Jul 3, 11:05 UTC | 6h 45m |
| 2026-07-02 | VTM9905 | - | Jul 2, 10:20 UTC | Jul 3, 05:00 UTC | 18h 40m |
| 2026-07-02 | VTM9905 | - | Jul 2, 01:50 UTC | Jul 2, 11:05 UTC | 9h 15m |
| 2026-07-01 | VTM9902 | - | Jul 1, 10:45 UTC | Jul 1, 12:20 UTC | 1h 35m |
| 2026-06-28 | VTM5001 | - | Jun 28, 04:29 UTC | Jun 28, 04:44 UTC | 15m |
| 2026-06-28 | VTM5001 | - | Jun 28, 03:09 UTC | Jun 28, 03:45 UTC | 35m |
| 2026-06-27 | VTM5002 | - | Jun 27, 13:44 UTC | Jun 27, 14:05 UTC | 20m |
| 2026-06-27 | VTM5002 | - | Jun 27, 11:50 UTC | Jun 27, 13:04 UTC | 1h 15m |
| 2026-06-26 | VTM5001 | - | Jun 26, 04:34 UTC | Jun 26, 04:55 UTC | 20m |
| 2026-06-26 | VTM5001 | - | Jun 26, 02:50 UTC | Jun 26, 03:29 UTC | 40m |
| 2026-06-25 | VTM5002 | - | Jun 25, 13:50 UTC | Jun 25, 14:09 UTC | 20m |
| 2026-06-25 | VTM5002 | - | Jun 25, 11:54 UTC | Jun 25, 13:05 UTC | 1h 10m |
| 2026-06-23 | VTM9905 | - | Jun 23, 10:35 UTC | Jun 24, 04:50 UTC | 18h 15m |
| 2026-06-20 | VTM1101 | - | Jun 20, 02:24 UTC | Jun 20, 03:29 UTC | 1h 5m |
| 2026-06-19 | VTM1102 | - | Jun 19, 13:50 UTC | Jun 19, 14:39 UTC | 50m |
| 2026-06-19 | VTM1102 | - | Jun 19, 13:04 UTC | Jun 19, 13:14 UTC | 10m |
| 2026-06-18 | VTM9905 | - | Jun 18, 10:20 UTC | Jun 19, 04:14 UTC | 17h 54m |
| 2026-06-17 | VTM9905 | - | Jun 17, 04:50 UTC | Jun 17, 11:20 UTC | 6h 30m |
| 2026-06-16 | VTM9905 | - | Jun 16, 10:25 UTC | Jun 17, 05:10 UTC | 18h 46m |
| 2026-06-12 | VTM9902 | - | Jun 12, 10:45 UTC | Jun 13, 05:00 UTC | 18h 15m |
| 2026-06-10 | VTM9905 | - | Jun 10, 10:15 UTC | Jun 11, 04:35 UTC | 18h 20m |
| 2026-06-05 | VTMY9905 | - | Jun 5, 10:30 UTC | Jun 6, 05:00 UTC | 18h 30m |
| 2026-06-05 | VTMY9905 | - | Jun 5, 01:25 UTC | Jun 5, 11:25 UTC | 10h 0m |
| 2026-06-04 | VTM9902 | - | Jun 4, 10:55 UTC | Jun 4, 11:30 UTC | 35m |
| 2026-06-02 | VTM9905 | - | Jun 2, 18:30 UTC | Jun 3, 11:30 UTC | 17h 0m |
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 .