sensors Mode-S transponder
0D0DDE
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VEV · BOEING 737-400
- Hex
- 0D0DDE
- Octal
- 03206736
- Decimal
- 855,518
- Country
- MX
- Tail
- XA-VEV
- Type
- B734
- Flights observed
- 76
- Distinct callsigns
- 10
- Country
- MX
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0DDE 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 10 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VTM9905 | - | Jun 2, 10:45 UTC | Jun 2, 11:40 UTC | 55m |
| 2026-05-30 | VTM1101 | - | May 30, 02:20 UTC | May 30, 03:25 UTC | 1h 5m |
| 2026-05-29 | VTM1101 | - | May 29, 02:35 UTC | May 29, 14:55 UTC | 12h 20m |
| 2026-05-28 | VTM1101 | - | May 28, 02:35 UTC | May 28, 14:50 UTC | 12h 15m |
| 2026-05-27 | VTM1101 | - | May 27, 02:44 UTC | May 27, 15:05 UTC | 12h 20m |
| 2026-05-26 | VTM4401 | - | May 26, 01:05 UTC | May 26, 14:40 UTC | 13h 35m |
| 2026-05-25 | VTM4402 | - | May 25, 15:05 UTC | May 25, 15:35 UTC | 30m |
| 2026-05-24 | VTM4402 | - | May 24, 04:35 UTC | May 24, 15:35 UTC | 11h 0m |
| 2026-05-24 | VTM5002 | - | May 24, 03:15 UTC | May 24, 03:50 UTC | 35m |
| 2026-05-23 | VTM5002 | - | May 23, 13:50 UTC | May 23, 14:10 UTC | 20m |
| 2026-05-23 | VTM5002 | - | May 23, 00:35 UTC | May 23, 13:15 UTC | 12h 40m |
| 2026-05-22 | VTM4402 | - | May 22, 13:15 UTC | May 22, 14:25 UTC | 1h 10m |
| 2026-05-18 | VTM6602 | - | May 18, 12:50 UTC | May 18, 13:10 UTC | 20m |
| 2026-05-18 | VTM6602 | - | May 18, 12:05 UTC | May 18, 12:20 UTC | 15m |
| 2026-05-18 | VTM4401 | - | May 18, 00:45 UTC | May 18, 01:50 UTC | 1h 5m |
| 2026-05-17 | VTM4402 | - | May 17, 03:55 UTC | May 17, 15:20 UTC | 11h 25m |
| 2026-05-17 | VTM5001 | - | May 17, 02:50 UTC | May 17, 03:25 UTC | 35m |
| 2026-05-16 | VTM5002 | - | May 16, 13:46 UTC | May 16, 14:05 UTC | 20m |
| 2026-05-16 | VTM4401 | - | May 16, 00:40 UTC | May 16, 13:05 UTC | 12h 26m |
| 2026-05-15 | VTM4402 | - | May 15, 12:55 UTC | May 15, 14:05 UTC | 1h 10m |
| 2026-05-10 | VTM150 | - | May 10, 04:29 UTC | May 10, 04:50 UTC | 20m |
| 2026-05-10 | VTM150 | - | May 10, 03:10 UTC | May 10, 03:45 UTC | 35m |
| 2026-05-09 | VTM150 | - | May 9, 07:05 UTC | May 10, 03:45 UTC | 20h 40m |
| 2026-05-05 | VTM5002 | - | May 5, 01:55 UTC | May 5, 02:20 UTC | 25m |
| 2026-05-04 | VTM5002 | - | May 4, 14:20 UTC | May 4, 14:40 UTC | 20m |
| 2026-05-04 | VTM5002 | - | May 4, 13:25 UTC | May 4, 13:45 UTC | 20m |
| 2026-05-03 | VTM9901 | - | May 3, 01:15 UTC | May 3, 01:40 UTC | 25m |
| 2026-05-02 | VTM9902 | - | May 2, 12:25 UTC | May 2, 12:55 UTC | 30m |
| 2026-05-02 | VTM9902 | - | May 2, 04:40 UTC | May 2, 10:50 UTC | 6h 10m |
| 2026-05-02 | VTM5001 | - | May 2, 03:05 UTC | May 2, 03:45 UTC | 40m |
| 2026-05-01 | VTM5002 | - | May 1, 13:50 UTC | May 1, 14:10 UTC | 20m |
| 2026-05-01 | VTM5002 | - | May 1, 04:50 UTC | May 1, 13:10 UTC | 8h 20m |
| 2026-05-01 | VTM5001 | - | May 1, 03:20 UTC | May 1, 04:10 UTC | 50m |
| 2026-04-30 | VTM5002 | - | Apr 30, 13:50 UTC | Apr 30, 14:10 UTC | 20m |
| 2026-04-30 | VTM5002 | - | Apr 30, 11:55 UTC | Apr 30, 13:10 UTC | 1h 15m |
| 2026-04-29 | VTM4401 | - | Apr 29, 00:45 UTC | Apr 29, 01:45 UTC | 1h 0m |
| 2026-04-28 | VTM4402 | - | Apr 28, 04:45 UTC | Apr 28, 14:35 UTC | 9h 50m |
| 2026-04-26 | VTM9901 | - | Apr 26, 14:20 UTC | Apr 26, 14:40 UTC | 20m |
| 2026-04-26 | VTM9902 | - | Apr 26, 12:40 UTC | Apr 26, 13:00 UTC | 20m |
| 2026-04-26 | VTM9902 | - | Apr 26, 03:50 UTC | Apr 26, 11:15 UTC | 7h 25m |
| 2026-04-26 | VTM9901 | - | Apr 26, 01:40 UTC | Apr 26, 02:05 UTC | 25m |
| 2026-04-25 | VTM9902 | - | Apr 25, 12:35 UTC | Apr 25, 13:00 UTC | 25m |
| 2026-04-25 | VTM9902 | - | Apr 25, 04:55 UTC | Apr 25, 11:10 UTC | 6h 15m |
| 2026-04-25 | VTM5001 | - | Apr 25, 03:45 UTC | Apr 25, 04:20 UTC | 35m |
| 2026-04-24 | VTM5002 | - | Apr 24, 13:50 UTC | Apr 24, 14:10 UTC | 20m |
| 2026-04-24 | VTM5002 | - | Apr 24, 04:45 UTC | Apr 24, 13:10 UTC | 8h 25m |
| 2026-04-24 | VTM5002 | - | Apr 24, 03:00 UTC | Apr 24, 03:40 UTC | 40m |
| 2026-04-23 | VTM5002 | - | Apr 23, 13:50 UTC | Apr 23, 14:10 UTC | 20m |
| 2026-04-23 | VTM5002 | - | Apr 23, 05:00 UTC | Apr 23, 13:15 UTC | 8h 15m |
| 2026-04-23 | VTM5001 | - | Apr 23, 03:10 UTC | Apr 23, 03:50 UTC | 40m |
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-VEV page for operator, model, and routing details .