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
- 139
- Distinct callsigns
- 11
- Country
- MX
- Last broadcast
- 1h 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 11 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | VTM4401 | - | Jul 18, 00:50 UTC | Jul 18, 01:30 UTC | 40m |
| 2026-07-17 | VTM4401 | - | Jul 17, 00:40 UTC | Jul 17, 14:04 UTC | 13h 25m |
| 2026-07-16 | VTM4401 | - | Jul 16, 00:45 UTC | Jul 16, 13:49 UTC | 13h 5m |
| 2026-07-15 | VTM4402 | - | Jul 15, 15:15 UTC | Jul 15, 16:10 UTC | 55m |
| 2026-07-15 | VTM4401 | - | Jul 15, 00:45 UTC | Jul 15, 14:05 UTC | 13h 20m |
| 2026-07-14 | VTM4402 | - | Jul 14, 00:45 UTC | Jul 14, 14:15 UTC | 13h 30m |
| 2026-07-13 | VTM4401 | - | Jul 13, 00:45 UTC | Jul 13, 15:05 UTC | 14h 20m |
| 2026-07-12 | VTM4401 | - | Jul 12, 00:50 UTC | Jul 12, 15:05 UTC | 14h 15m |
| 2026-07-11 | VTM4402 | TIJ → TIJ | Jul 11, 00:45 UTC | Jul 11, 13:55 UTC | 13h 10m |
| 2026-07-10 | VTM4402 | - | Jul 10, 12:50 UTC | Jul 10, 14:00 UTC | 1h 10m |
| 2026-07-09 | VTM5002 | - | Jul 9, 11:55 UTC | Jul 10, 03:25 UTC | 15h 30m |
| 2026-07-09 | VTM4401 | - | Jul 9, 00:50 UTC | Jul 9, 12:00 UTC | 11h 10m |
| 2026-07-08 | VTM4401 | - | Jul 8, 00:50 UTC | Jul 8, 14:35 UTC | 13h 45m |
| 2026-07-07 | VTM4401 | - | Jul 7, 00:55 UTC | Jul 7, 13:45 UTC | 12h 50m |
| 2026-07-06 | VTM4401 | - | Jul 6, 00:40 UTC | Jul 6, 15:05 UTC | 14h 25m |
| 2026-07-05 | VTM4401 | - | Jul 5, 01:15 UTC | Jul 5, 15:40 UTC | 14h 25m |
| 2026-07-04 | VTM4401 | - | Jul 4, 00:55 UTC | Jul 4, 13:50 UTC | 12h 55m |
| 2026-07-03 | VTM4402 | - | Jul 3, 00:50 UTC | Jul 3, 14:05 UTC | 13h 15m |
| 2026-07-02 | VTM4402 | - | Jul 2, 00:55 UTC | Jul 2, 14:05 UTC | 13h 10m |
| 2026-07-01 | VTM4402 | - | Jul 1, 00:55 UTC | Jul 1, 14:05 UTC | 13h 10m |
| 2026-06-30 | VTM4402 | - | Jun 30, 00:45 UTC | Jun 30, 14:00 UTC | 13h 16m |
| 2026-06-29 | VTM4401 | - | Jun 29, 00:39 UTC | Jun 29, 15:24 UTC | 14h 45m |
| 2026-06-28 | VTM4401 | - | Jun 28, 00:35 UTC | Jun 28, 15:40 UTC | 15h 5m |
| 2026-06-27 | VTM4402 | - | Jun 27, 00:44 UTC | Jun 27, 14:09 UTC | 13h 25m |
| 2026-06-26 | VTM4402 | - | Jun 26, 13:04 UTC | Jun 26, 14:05 UTC | 1h 0m |
| 2026-06-25 | VTM4401 | - | Jun 25, 01:04 UTC | Jun 25, 02:14 UTC | 1h 10m |
| 2026-06-24 | VTM4401 | - | Jun 24, 00:34 UTC | Jun 24, 13:44 UTC | 13h 10m |
| 2026-06-23 | VTM4401 | - | Jun 23, 00:50 UTC | Jun 23, 14:04 UTC | 13h 15m |
| 2026-06-22 | VTM4401 | - | Jun 22, 00:55 UTC | Jun 22, 15:10 UTC | 14h 15m |
| 2026-06-21 | VTM4401 | - | Jun 21, 00:40 UTC | Jun 21, 15:09 UTC | 14h 30m |
| 2026-06-20 | VTM4402 | - | Jun 20, 13:09 UTC | Jun 20, 14:14 UTC | 1h 5m |
| 2026-06-19 | VTM4401 | - | Jun 19, 00:55 UTC | Jun 19, 01:59 UTC | 1h 5m |
| 2026-06-18 | VTM4402 | - | Jun 18, 04:55 UTC | Jun 18, 13:50 UTC | 8h 55m |
| 2026-06-18 | VTM5002 | - | Jun 18, 02:50 UTC | Jun 18, 03:30 UTC | 40m |
| 2026-06-17 | VTM5002 | - | Jun 17, 13:50 UTC | Jun 17, 14:10 UTC | 20m |
| 2026-06-17 | VTM5002 | - | Jun 17, 04:55 UTC | Jun 17, 13:05 UTC | 8h 10m |
| 2026-06-17 | VTM5002 | - | Jun 17, 02:45 UTC | Jun 17, 03:20 UTC | 35m |
| 2026-06-16 | VTM5002 | - | Jun 16, 14:05 UTC | Jun 16, 14:25 UTC | 20m |
| 2026-06-16 | VTM5002 | - | Jun 16, 04:45 UTC | Jun 16, 13:25 UTC | 8h 40m |
| 2026-06-16 | VTM5001 | - | Jun 16, 03:00 UTC | Jun 16, 03:39 UTC | 40m |
| 2026-06-15 | VTM5002 | - | Jun 15, 14:45 UTC | Jun 15, 15:04 UTC | 20m |
| 2026-06-15 | VTM5002 | - | Jun 15, 13:20 UTC | Jun 15, 14:05 UTC | 45m |
| 2026-06-15 | VTM5002 | - | Jun 15, 12:25 UTC | Jun 15, 12:39 UTC | 15m |
| 2026-06-15 | VTM5001 | - | Jun 15, 04:20 UTC | Jun 15, 04:40 UTC | 20m |
| 2026-06-15 | VTM5001 | - | Jun 15, 02:44 UTC | Jun 15, 03:24 UTC | 40m |
| 2026-06-14 | VTM5002 | - | Jun 14, 14:25 UTC | Jun 14, 14:45 UTC | 20m |
| 2026-06-14 | VTM5002 | - | Jun 14, 13:00 UTC | Jun 14, 13:40 UTC | 40m |
| 2026-06-14 | VTM5002 | - | Jun 14, 12:05 UTC | Jun 14, 12:20 UTC | 15m |
| 2026-06-14 | VTM5002 | - | Jun 14, 04:35 UTC | Jun 14, 04:55 UTC | 20m |
| 2026-06-14 | VTM5002 | - | Jun 14, 03:15 UTC | Jun 14, 03:50 UTC | 35m |
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 .