sensors Mode-S transponder
0D0DC4
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-ADS
- Hex
- 0D0DC4
- Octal
- 03206704
- Decimal
- 855,492
- Country
- MX
- Tail
- XA-ADS
- Type
- CRJ2
- Flights observed
- 66
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0DC4 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 |
|---|---|---|---|
| VTM300 | - | 66 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-06 | VTM300 | - | Jun 6, 02:20 UTC | Jun 6, 05:35 UTC | 3h 15m |
| 2026-06-06 | VTM300 | - | Jun 6, 00:35 UTC | Jun 6, 01:10 UTC | 35m |
| 2026-06-05 | VTM300 | - | Jun 5, 03:05 UTC | Jun 6, 01:10 UTC | 22h 5m |
| 2026-06-05 | VTM300 | - | Jun 5, 01:05 UTC | Jun 6, 01:00 UTC | 23h 55m |
| 2026-06-04 | VTM300 | - | Jun 4, 23:50 UTC | Jun 5, 03:15 UTC | 3h 25m |
| 2026-06-03 | VTM300 | - | Jun 3, 22:05 UTC | Jun 4, 00:55 UTC | 2h 50m |
| 2026-06-03 | VTM300 | - | Jun 3, 20:20 UTC | Jun 3, 20:55 UTC | 35m |
| 2026-05-30 | VTM300 | - | May 30, 19:00 UTC | May 30, 22:30 UTC | 3h 30m |
| 2026-05-30 | VTM300 | LRD → TOL | May 30, 02:06 UTC | May 30, 04:50 UTC | 2h 44m |
| 2026-05-30 | VTM300 | - | May 30, 00:20 UTC | May 30, 01:00 UTC | 40m |
| 2026-05-29 | VTM300 | - | May 29, 02:10 UTC | May 29, 02:40 UTC | 30m |
| 2026-05-28 | VTM300 | - | May 28, 20:20 UTC | May 28, 23:50 UTC | 3h 30m |
| 2026-05-28 | VTM300 | - | May 28, 15:15 UTC | May 28, 18:40 UTC | 3h 25m |
| 2026-05-27 | VTM300 | - | May 27, 19:30 UTC | May 28, 14:00 UTC | 18h 30m |
| 2026-05-26 | VTM300 | - | May 26, 21:09 UTC | May 27, 19:30 UTC | 22h 20m |
| 2026-05-25 | VTM300 | - | May 25, 19:10 UTC | May 25, 22:40 UTC | 3h 30m |
| 2026-05-25 | VTM300 | - | May 25, 12:25 UTC | May 25, 15:40 UTC | 3h 15m |
| 2026-05-25 | VTM300 | - | May 25, 01:55 UTC | May 25, 02:25 UTC | 30m |
| 2026-05-22 | VTM300 | - | May 22, 19:05 UTC | May 22, 20:15 UTC | 1h 10m |
| 2026-05-22 | VTM300 | LRD → PBC | May 22, 14:05 UTC | May 22, 17:55 UTC | 3h 50m |
| 2026-05-21 | VTM300 | - | May 21, 05:30 UTC | May 21, 08:50 UTC | 3h 20m |
| 2026-05-21 | VTM300 | LRD → CLE | May 21, 01:10 UTC | May 21, 03:55 UTC | 2h 45m |
| 2026-05-20 | VTM300 | - | May 20, 23:10 UTC | May 20, 23:45 UTC | 35m |
| 2026-05-20 | VTM300 | - | May 20, 01:05 UTC | May 20, 23:45 UTC | 22h 41m |
| 2026-05-19 | VTM300 | - | May 19, 22:55 UTC | May 20, 02:35 UTC | 3h 40m |
| 2026-05-19 | VTM300 | - | May 19, 07:00 UTC | May 19, 09:50 UTC | 2h 50m |
| 2026-05-19 | VTM300 | - | May 19, 03:35 UTC | May 19, 04:10 UTC | 35m |
| 2026-05-16 | VTM300 | - | May 16, 18:50 UTC | May 16, 19:20 UTC | 30m |
| 2026-05-16 | VTM300 | - | May 16, 03:40 UTC | May 16, 07:11 UTC | 3h 31m |
| 2026-05-15 | VTM300 | LRD → IAG | May 15, 22:40 UTC | May 16, 01:55 UTC | 3h 15m |
| 2026-05-15 | VTM300 | LRD → LRD | May 15, 15:50 UTC | May 15, 21:20 UTC | 5h 30m |
| 2026-05-15 | VTM300 | - | May 15, 04:15 UTC | May 15, 07:05 UTC | 2h 50m |
| 2026-05-14 | VTM300 | LRD → YIP | May 14, 23:55 UTC | May 15, 02:50 UTC | 2h 55m |
| 2026-05-14 | VTM300 | LRD → LRD | May 14, 18:10 UTC | May 14, 22:50 UTC | 4h 40m |
| 2026-05-13 | VTM300 | - | May 13, 02:55 UTC | May 13, 06:20 UTC | 3h 25m |
| 2026-05-12 | VTM300 | - | May 12, 23:35 UTC | May 13, 01:55 UTC | 2h 20m |
| 2026-05-12 | VTM300 | LRD → SHV | May 12, 21:50 UTC | May 12, 23:01 UTC | 1h 10m |
| 2026-05-12 | VTM300 | - | May 12, 19:55 UTC | May 12, 20:35 UTC | 40m |
| 2026-05-11 | VTM300 | - | May 11, 17:25 UTC | May 11, 20:55 UTC | 3h 30m |
| 2026-05-09 | VTM300 | - | May 9, 15:20 UTC | May 9, 18:30 UTC | 3h 10m |
| 2026-05-08 | VTM300 | - | May 8, 19:05 UTC | May 9, 14:20 UTC | 19h 15m |
| 2026-05-08 | VTM300 | LRD → LRD | May 8, 18:40 UTC | May 9, 14:20 UTC | 19h 40m |
| 2026-05-08 | VTM300 | - | May 8, 00:40 UTC | May 8, 03:04 UTC | 2h 25m |
| 2026-05-07 | VTM300 | - | May 7, 20:40 UTC | May 7, 22:00 UTC | 1h 20m |
| 2026-05-07 | VTM300 | - | May 7, 19:25 UTC | May 7, 19:55 UTC | 30m |
| 2026-05-07 | VTM300 | - | May 7, 16:20 UTC | May 7, 16:45 UTC | 25m |
| 2026-05-06 | VTM300 | - | May 6, 22:00 UTC | May 7, 00:45 UTC | 2h 45m |
| 2026-05-06 | VTM300 | - | May 6, 20:05 UTC | May 6, 20:40 UTC | 35m |
| 2026-05-01 | VTM300 | - | May 1, 21:20 UTC | May 1, 22:55 UTC | 1h 35m |
| 2026-05-01 | VTM300 | IAG → SHV | May 1, 16:45 UTC | May 1, 19:50 UTC | 3h 5m |
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-ADS page for operator, model, and routing details .