sensors Mode-S transponder
0D0CD0
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-EEE · SWEARINGEN Metro
- Hex
- 0D0CD0
- Octal
- 03206320
- Decimal
- 855,248
- Country
- MX
- Tail
- XA-EEE
- Type
- SW4
- Flights observed
- 51
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0CD0 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VTM503 | - | 51 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | VTM503 | - | Jul 24, 16:25 UTC | Jul 24, 17:30 UTC | 1h 5m |
| 2026-07-22 | VTM503 | - | Jul 22, 19:50 UTC | Jul 22, 20:05 UTC | 15m |
| 2026-07-21 | VTM503 | - | Jul 21, 22:35 UTC | Jul 21, 22:55 UTC | 20m |
| 2026-07-15 | VTM503 | - | Jul 15, 04:30 UTC | Jul 15, 05:05 UTC | 35m |
| 2026-07-15 | VTM503 | - | Jul 15, 02:15 UTC | Jul 15, 02:35 UTC | 20m |
| 2026-07-14 | VTM503 | - | Jul 14, 21:45 UTC | Jul 14, 22:00 UTC | 15m |
| 2026-06-27 | VTM503 | - | Jun 27, 21:55 UTC | Jun 28, 00:15 UTC | 2h 20m |
| 2026-06-27 | VTM503 | - | Jun 27, 16:59 UTC | Jun 27, 19:00 UTC | 2h 0m |
| 2026-06-26 | VTM503 | - | Jun 26, 05:44 UTC | Jun 26, 09:20 UTC | 3h 35m |
| 2026-06-26 | VTM503 | - | Jun 26, 03:10 UTC | Jun 26, 04:00 UTC | 50m |
| 2026-06-11 | VTM503 | - | Jun 11, 18:55 UTC | Jun 11, 19:50 UTC | 55m |
| 2026-06-11 | VTM503 | - | Jun 11, 17:05 UTC | Jun 11, 18:05 UTC | 1h 0m |
| 2026-06-08 | VTM503 | - | Jun 8, 21:00 UTC | Jun 8, 23:50 UTC | 2h 50m |
| 2026-06-08 | VTM503 | - | Jun 8, 16:05 UTC | Jun 8, 19:05 UTC | 3h 0m |
| 2026-06-08 | VTM503 | - | Jun 8, 12:15 UTC | Jun 8, 14:40 UTC | 2h 25m |
| 2026-06-07 | VTM503 | LRD → BMI | Jun 7, 03:00 UTC | Jun 7, 06:55 UTC | 3h 55m |
| 2026-06-07 | VTM503 | - | Jun 7, 00:49 UTC | Jun 7, 01:35 UTC | 45m |
| 2026-06-06 | VTM503 | - | Jun 6, 20:05 UTC | Jun 6, 20:19 UTC | 15m |
| 2026-05-22 | VTM503 | - | May 22, 16:55 UTC | May 22, 19:25 UTC | 2h 30m |
| 2026-05-22 | VTM503 | - | May 22, 12:20 UTC | May 22, 15:55 UTC | 3h 35m |
| 2026-05-22 | VTM503 | - | May 22, 06:50 UTC | May 22, 07:05 UTC | 15m |
| 2026-05-21 | VTM503 | - | May 21, 07:20 UTC | May 21, 10:20 UTC | 3h 0m |
| 2026-05-21 | VTM503 | LRD → SHV | May 21, 03:55 UTC | May 21, 05:45 UTC | 1h 50m |
| 2026-05-21 | VTM503 | - | May 21, 00:50 UTC | May 21, 01:55 UTC | 1h 5m |
| 2026-05-20 | VTM503 | - | May 20, 19:55 UTC | May 20, 20:15 UTC | 20m |
| 2026-05-18 | VTM503 | - | May 18, 20:45 UTC | May 18, 21:00 UTC | 15m |
| 2026-05-18 | VTM503 | - | May 18, 18:15 UTC | May 18, 18:25 UTC | 10m |
| 2026-05-16 | VTM503 | - | May 16, 16:31 UTC | May 16, 21:05 UTC | 4h 35m |
| 2026-05-15 | VTM503 | - | May 15, 03:45 UTC | May 15, 07:15 UTC | 3h 30m |
| 2026-05-15 | VTM503 | - | May 15, 01:10 UTC | May 15, 02:00 UTC | 50m |
| 2026-05-14 | VTM503 | - | May 14, 20:10 UTC | May 14, 20:25 UTC | 15m |
| 2026-05-07 | VTM503 | - | May 7, 21:30 UTC | May 8, 00:29 UTC | 3h 0m |
| 2026-05-07 | VTM503 | - | May 7, 17:20 UTC | May 7, 19:30 UTC | 2h 10m |
| 2026-05-07 | VTM503 | - | May 7, 00:05 UTC | May 7, 03:00 UTC | 2h 55m |
| 2026-05-06 | VTM503 | - | May 6, 21:25 UTC | May 6, 22:10 UTC | 45m |
| 2026-05-04 | VTM503 | - | May 4, 21:25 UTC | May 4, 22:30 UTC | 1h 5m |
| 2026-05-02 | VTM503 | - | May 2, 21:50 UTC | May 3, 00:25 UTC | 2h 35m |
| 2026-05-01 | VTM503 | - | May 1, 17:40 UTC | May 1, 18:20 UTC | 40m |
| 2026-05-01 | VTM503 | - | May 1, 10:35 UTC | May 1, 13:15 UTC | 2h 40m |
| 2026-05-01 | VTM503 | - | May 1, 04:50 UTC | May 1, 05:55 UTC | 1h 5m |
| 2026-05-01 | VTM503 | - | May 1, 03:35 UTC | May 1, 04:05 UTC | 30m |
| 2026-05-01 | VTM503 | - | May 1, 00:50 UTC | May 1, 01:05 UTC | 15m |
| 2026-04-30 | VTM503 | - | Apr 30, 23:00 UTC | May 1, 00:00 UTC | 1h 0m |
| 2026-04-30 | VTM503 | PHX → LRD | Apr 30, 05:40 UTC | Apr 30, 08:30 UTC | 2h 50m |
| 2026-04-29 | VTM503 | - | Apr 29, 07:59 UTC | Apr 29, 11:40 UTC | 3h 41m |
| 2026-04-29 | VTM503 | - | Apr 29, 05:40 UTC | Apr 29, 06:19 UTC | 40m |
| 2026-04-29 | VTM503 | - | Apr 29, 00:15 UTC | Apr 29, 00:25 UTC | 10m |
| 2026-04-22 | VTM503 | - | Apr 22, 20:30 UTC | Apr 22, 21:25 UTC | 55m |
| 2026-04-13 | VTM503 | - | Apr 13, 19:50 UTC | Apr 13, 20:00 UTC | 10m |
| 2026-04-13 | VTM503 | - | Apr 13, 19:20 UTC | Apr 13, 20:00 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-EEE page for operator, model, and routing details .