sensors Mode-S transponder
0D0019
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-ECA · BOEING 737-300
- Hex
- 0D0019
- Octal
- 03200031
- Decimal
- 851,993
- Country
- MX
- Tail
- XA-ECA
- Type
- B733
- Flights observed
- 177
- Distinct callsigns
- 3
- Country
- MX
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0019 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | VTM7520 | - | Jul 17, 13:35 UTC | Jul 17, 14:04 UTC | 30m |
| 2026-07-17 | VTM7521 | - | Jul 17, 11:15 UTC | Jul 17, 12:25 UTC | 1h 10m |
| 2026-07-17 | VTM7521 | - | Jul 17, 04:44 UTC | Jul 17, 05:04 UTC | 20m |
| 2026-07-16 | VTM7521 | MTY → MTY | Jul 16, 13:45 UTC | Jul 17, 01:00 UTC | 11h 15m |
| 2026-07-16 | VTM7521 | - | Jul 16, 11:10 UTC | Jul 16, 12:20 UTC | 1h 10m |
| 2026-07-16 | VTM7521 | - | Jul 16, 04:30 UTC | Jul 16, 04:45 UTC | 15m |
| 2026-07-15 | VTM7520 | MTY → MTY | Jul 15, 13:05 UTC | Jul 16, 00:35 UTC | 11h 30m |
| 2026-07-15 | VTM7520 | - | Jul 15, 11:10 UTC | Jul 15, 12:20 UTC | 1h 10m |
| 2026-07-15 | VTM7521 | - | Jul 15, 04:25 UTC | Jul 15, 04:45 UTC | 20m |
| 2026-07-14 | VTM7520 | MTY → MTY | Jul 14, 13:20 UTC | Jul 15, 01:00 UTC | 11h 39m |
| 2026-07-14 | VTM7520 | - | Jul 14, 11:10 UTC | Jul 14, 12:25 UTC | 1h 15m |
| 2026-07-14 | VTM7521 | - | Jul 14, 04:45 UTC | Jul 14, 05:05 UTC | 20m |
| 2026-07-14 | VTM7521 | - | Jul 14, 00:20 UTC | Jul 14, 00:55 UTC | 35m |
| 2026-07-10 | VTM7521 | - | Jul 10, 13:00 UTC | Jul 10, 13:30 UTC | 30m |
| 2026-07-10 | VTM7521 | - | Jul 10, 11:10 UTC | Jul 10, 12:20 UTC | 1h 10m |
| 2026-07-09 | VTM7520 | MTY → MTY | Jul 9, 13:05 UTC | Jul 10, 00:15 UTC | 11h 10m |
| 2026-07-09 | VTM7520 | - | Jul 9, 11:10 UTC | Jul 9, 12:20 UTC | 1h 10m |
| 2026-07-09 | VTM7521 | - | Jul 9, 04:20 UTC | Jul 9, 04:40 UTC | 20m |
| 2026-07-08 | VTM7521 | - | Jul 8, 13:05 UTC | Jul 9, 00:25 UTC | 11h 20m |
| 2026-07-08 | VTM7520 | - | Jul 8, 11:15 UTC | Jul 8, 12:25 UTC | 1h 10m |
| 2026-07-08 | VTM7521 | - | Jul 8, 04:45 UTC | Jul 8, 05:05 UTC | 20m |
| 2026-07-07 | VTM7520 | MTY → MTY | Jul 7, 13:25 UTC | Jul 8, 00:30 UTC | 11h 5m |
| 2026-07-07 | VTM7520 | - | Jul 7, 11:25 UTC | Jul 7, 12:40 UTC | 1h 15m |
| 2026-07-07 | VTM7520 | - | Jul 7, 04:45 UTC | Jul 7, 05:05 UTC | 20m |
| 2026-07-06 | VTM7520 | - | Jul 6, 23:55 UTC | Jul 7, 00:40 UTC | 45m |
| 2026-07-03 | VTM7520 | - | Jul 3, 12:35 UTC | Jul 3, 13:10 UTC | 35m |
| 2026-07-03 | VTM7520 | - | Jul 3, 10:45 UTC | Jul 3, 11:50 UTC | 1h 5m |
| 2026-07-03 | VTM7521 | - | Jul 3, 04:15 UTC | Jul 3, 04:35 UTC | 20m |
| 2026-07-02 | VTM7520 | MTY → MTY | Jul 2, 12:50 UTC | Jul 3, 01:25 UTC | 12h 35m |
| 2026-07-02 | VTM7521 | - | Jul 2, 10:45 UTC | Jul 2, 11:55 UTC | 1h 10m |
| 2026-07-02 | VTM7521 | - | Jul 2, 04:35 UTC | Jul 2, 04:55 UTC | 20m |
| 2026-07-01 | VTM7520 | MTY → MTY | Jul 1, 12:35 UTC | Jul 2, 01:05 UTC | 12h 30m |
| 2026-07-01 | VTM7520 | - | Jul 1, 10:30 UTC | Jul 1, 11:40 UTC | 1h 10m |
| 2026-07-01 | VTM7521 | - | Jul 1, 04:25 UTC | Jul 1, 04:50 UTC | 25m |
| 2026-06-30 | VTM7521 | MTY → MTY | Jun 30, 12:45 UTC | Jul 1, 00:50 UTC | 12h 5m |
| 2026-06-30 | VTM7520 | - | Jun 30, 10:45 UTC | Jun 30, 11:55 UTC | 1h 10m |
| 2026-06-30 | VTM7521 | - | Jun 30, 04:40 UTC | Jun 30, 05:05 UTC | 25m |
| 2026-06-30 | VTM7521 | - | Jun 30, 00:25 UTC | Jun 30, 01:04 UTC | 40m |
| 2026-06-26 | VTM7520 | - | Jun 26, 12:34 UTC | Jun 26, 13:04 UTC | 30m |
| 2026-06-26 | VTM7520 | - | Jun 26, 10:30 UTC | Jun 26, 11:45 UTC | 1h 15m |
| 2026-06-26 | VTM7521 | - | Jun 26, 04:39 UTC | Jun 26, 04:59 UTC | 20m |
| 2026-06-25 | VTM7521 | MTY → MTY | Jun 25, 13:50 UTC | Jun 26, 00:35 UTC | 10h 45m |
| 2026-06-25 | VTM7520 | - | Jun 25, 10:35 UTC | Jun 25, 11:44 UTC | 1h 10m |
| 2026-06-25 | VTM7521 | - | Jun 25, 04:35 UTC | Jun 25, 04:54 UTC | 20m |
| 2026-06-24 | VTM7521 | MTY → MTY | Jun 24, 12:34 UTC | Jun 25, 00:55 UTC | 12h 20m |
| 2026-06-24 | VTM7520 | - | Jun 24, 10:19 UTC | Jun 24, 11:29 UTC | 1h 10m |
| 2026-06-24 | VTM7521 | - | Jun 24, 04:50 UTC | Jun 24, 05:09 UTC | 20m |
| 2026-06-23 | VTM7521 | - | Jun 23, 13:19 UTC | Jun 24, 00:34 UTC | 11h 15m |
| 2026-06-23 | VTM7520 | - | Jun 23, 11:19 UTC | Jun 23, 12:29 UTC | 1h 10m |
| 2026-06-23 | VTM7521 | - | Jun 23, 04:50 UTC | Jun 23, 05:09 UTC | 20m |
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-ECA page for operator, model, and routing details .