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
- 92
- Distinct callsigns
- 3
- Country
- MX
- Last broadcast
- 6h 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-06-02 | VTM7521 | - | Jun 2, 13:35 UTC | Jun 2, 14:10 UTC | 35m |
| 2026-06-02 | VTM7521 | - | Jun 2, 11:20 UTC | Jun 2, 12:30 UTC | 1h 10m |
| 2026-06-02 | VTM7521 | - | Jun 2, 05:55 UTC | Jun 2, 06:15 UTC | 20m |
| 2026-06-02 | VTM7521 | - | Jun 2, 00:00 UTC | Jun 2, 00:35 UTC | 35m |
| 2026-05-29 | VTM7520 | - | May 29, 13:25 UTC | May 29, 14:00 UTC | 35m |
| 2026-05-29 | VTM7520 | - | May 29, 11:05 UTC | May 29, 12:20 UTC | 1h 15m |
| 2026-05-29 | VTM7520 | - | May 29, 04:55 UTC | May 29, 05:20 UTC | 25m |
| 2026-05-28 | VTM7520 | MTY → MTY | May 28, 13:35 UTC | May 29, 00:45 UTC | 11h 10m |
| 2026-05-28 | VTM7520 | - | May 28, 11:40 UTC | May 28, 12:50 UTC | 1h 10m |
| 2026-05-28 | VTM7521 | - | May 28, 05:35 UTC | May 28, 05:55 UTC | 20m |
| 2026-05-27 | VTM7520 | MTY → MTY | May 27, 12:50 UTC | May 28, 00:45 UTC | 11h 55m |
| 2026-05-27 | VTM7520 | - | May 27, 10:50 UTC | May 27, 12:00 UTC | 1h 10m |
| 2026-05-27 | VTM7521 | - | May 27, 04:39 UTC | May 27, 05:04 UTC | 25m |
| 2026-05-26 | VTM7520 | MTY → MTY | May 26, 13:29 UTC | May 27, 01:05 UTC | 11h 35m |
| 2026-05-26 | VTM7520 | - | May 26, 10:39 UTC | May 26, 12:14 UTC | 1h 35m |
| 2026-05-26 | VTM7521 | - | May 26, 04:54 UTC | May 26, 05:15 UTC | 20m |
| 2026-05-25 | VTM7521 | - | May 25, 23:40 UTC | May 26, 00:09 UTC | 30m |
| 2026-05-22 | VTM7520 | - | May 22, 12:40 UTC | May 22, 13:10 UTC | 30m |
| 2026-05-22 | VTM7520 | - | May 22, 10:30 UTC | May 22, 11:40 UTC | 1h 10m |
| 2026-05-22 | VTM7521 | - | May 22, 04:35 UTC | May 22, 04:55 UTC | 20m |
| 2026-05-21 | VTM7520 | MTY → MTY | May 21, 12:35 UTC | May 22, 00:10 UTC | 11h 35m |
| 2026-05-21 | VTM7520 | - | May 21, 10:25 UTC | May 21, 11:30 UTC | 1h 5m |
| 2026-05-21 | VTM7520 | - | May 21, 04:55 UTC | May 21, 05:15 UTC | 20m |
| 2026-05-20 | VTM7520 | MTY → MTY | May 20, 12:30 UTC | May 21, 00:20 UTC | 11h 50m |
| 2026-05-20 | VTM7520 | - | May 20, 10:25 UTC | May 20, 11:35 UTC | 1h 10m |
| 2026-05-20 | VTM7520 | - | May 20, 04:50 UTC | May 20, 05:15 UTC | 25m |
| 2026-05-19 | VTM7520 | - | May 19, 13:10 UTC | May 20, 00:20 UTC | 11h 10m |
| 2026-05-19 | VTM7520 | - | May 19, 11:00 UTC | May 19, 12:15 UTC | 1h 15m |
| 2026-05-19 | VTM7521 | - | May 19, 04:55 UTC | May 19, 05:15 UTC | 20m |
| 2026-05-18 | VTM7521 | - | May 18, 23:45 UTC | May 19, 00:15 UTC | 30m |
| 2026-05-15 | VTM7520 | - | May 15, 12:30 UTC | May 15, 13:10 UTC | 40m |
| 2026-05-15 | VTM7520 | - | May 15, 10:30 UTC | May 15, 11:40 UTC | 1h 10m |
| 2026-05-15 | VTM7520 | - | May 15, 04:40 UTC | May 15, 05:00 UTC | 20m |
| 2026-05-14 | VTM7520 | MTY → MTY | May 14, 12:35 UTC | May 15, 00:05 UTC | 11h 30m |
| 2026-05-14 | VTM7521 | - | May 14, 10:25 UTC | May 14, 11:40 UTC | 1h 15m |
| 2026-05-14 | VTM7521 | - | May 14, 04:45 UTC | May 14, 05:05 UTC | 20m |
| 2026-05-13 | VTM7521 | MTY → MTY | May 13, 13:00 UTC | May 14, 00:30 UTC | 11h 30m |
| 2026-05-13 | VTM7521 | - | May 13, 10:50 UTC | May 13, 12:05 UTC | 1h 15m |
| 2026-05-13 | VTM7521 | - | May 13, 04:50 UTC | May 13, 05:10 UTC | 20m |
| 2026-05-12 | VTM7521 | MTY → MTY | May 12, 12:30 UTC | May 13, 00:45 UTC | 12h 15m |
| 2026-05-12 | VTM7521 | - | May 12, 10:40 UTC | May 12, 11:45 UTC | 1h 5m |
| 2026-05-12 | VTM7521 | - | May 12, 05:10 UTC | May 12, 05:30 UTC | 20m |
| 2026-05-08 | VTM7520 | - | May 8, 13:25 UTC | May 8, 13:55 UTC | 30m |
| 2026-05-08 | VTM7521 | - | May 8, 11:14 UTC | May 8, 12:20 UTC | 1h 5m |
| 2026-05-08 | VTM7521 | - | May 8, 05:09 UTC | May 8, 05:29 UTC | 20m |
| 2026-05-07 | VTM7521 | MTY → MTY | May 7, 13:20 UTC | May 8, 01:24 UTC | 12h 4m |
| 2026-05-07 | VTM7520 | - | May 7, 11:05 UTC | May 7, 12:15 UTC | 1h 10m |
| 2026-05-07 | VTM7521 | - | May 7, 04:45 UTC | May 7, 05:10 UTC | 25m |
| 2026-05-07 | 00000000 | - | May 7, 02:30 UTC | May 7, 02:50 UTC | 20m |
| 2026-04-30 | VTM7520 | - | Apr 30, 12:55 UTC | Apr 30, 17:15 UTC | 4h 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 .