sensors Mode-S transponder
0D0205
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-TVO · BEECH 200 Super King Air
- Hex
- 0D0205
- Octal
- 03201005
- Decimal
- 852,485
- Country
- MX
- Tail
- XA-TVO
- Type
- BE20
- Flights observed
- 62
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0205 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 |
|---|---|---|---|
| XATVO | - | 62 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | XATVO | - | Jul 16, 12:34 UTC | Jul 16, 13:30 UTC | 55m |
| 2026-07-16 | XATVO | - | Jul 16, 10:45 UTC | Jul 16, 11:45 UTC | 1h 0m |
| 2026-07-15 | XATVO | - | Jul 15, 08:55 UTC | Jul 15, 21:45 UTC | 12h 50m |
| 2026-06-30 | XATVO | - | Jun 30, 15:55 UTC | Jun 30, 16:15 UTC | 20m |
| 2026-06-30 | XATVO | - | Jun 30, 13:10 UTC | Jun 30, 13:25 UTC | 15m |
| 2026-06-28 | XATVO | - | Jun 28, 23:29 UTC | Jun 29, 00:00 UTC | 30m |
| 2026-06-28 | XATVO | - | Jun 28, 21:14 UTC | Jun 28, 21:50 UTC | 35m |
| 2026-06-28 | XATVO | - | Jun 28, 18:55 UTC | Jun 28, 19:40 UTC | 45m |
| 2026-06-25 | XATVO | - | Jun 25, 12:35 UTC | Jun 25, 13:24 UTC | 50m |
| 2026-06-24 | XATVO | - | Jun 24, 21:04 UTC | Jun 24, 21:29 UTC | 25m |
| 2026-06-24 | XATVO | - | Jun 24, 11:05 UTC | Jun 24, 11:45 UTC | 40m |
| 2026-06-23 | XATVO | - | Jun 23, 19:19 UTC | Jun 23, 20:59 UTC | 1h 40m |
| 2026-06-22 | XATVO | - | Jun 22, 22:30 UTC | Jun 22, 22:49 UTC | 20m |
| 2026-06-22 | XATVO | - | Jun 22, 20:34 UTC | Jun 22, 21:49 UTC | 1h 15m |
| 2026-06-17 | XATVO | - | Jun 17, 22:20 UTC | Jun 18, 00:25 UTC | 2h 5m |
| 2026-06-17 | XATVO | - | Jun 17, 13:25 UTC | Jun 17, 13:40 UTC | 15m |
| 2026-06-17 | XATVO | - | Jun 17, 11:25 UTC | Jun 17, 12:55 UTC | 1h 30m |
| 2026-06-12 | XATVO | - | Jun 12, 00:25 UTC | Jun 12, 02:00 UTC | 1h 36m |
| 2026-06-11 | XATVO | VIX → RTE | Jun 11, 12:05 UTC | Jun 11, 14:10 UTC | 2h 5m |
| 2026-06-07 | XATVO | - | Jun 7, 20:05 UTC | Jun 7, 21:00 UTC | 55m |
| 2026-06-03 | XATVO | - | Jun 3, 20:30 UTC | Jun 3, 21:40 UTC | 1h 10m |
| 2026-06-02 | XATVO | - | Jun 2, 15:50 UTC | Jun 2, 16:50 UTC | 1h 0m |
| 2026-06-02 | XATVO | - | Jun 2, 13:20 UTC | Jun 2, 13:50 UTC | 30m |
| 2026-06-02 | XATVO | - | Jun 2, 11:45 UTC | Jun 2, 12:05 UTC | 20m |
| 2026-06-01 | XATVO | - | Jun 1, 18:35 UTC | Jun 1, 18:50 UTC | 15m |
| 2026-06-01 | XATVO | - | Jun 1, 17:25 UTC | Jun 1, 17:50 UTC | 25m |
| 2026-06-01 | XATVO | - | Jun 1, 12:05 UTC | Jun 1, 12:25 UTC | 20m |
| 2026-06-01 | XATVO | - | Jun 1, 11:20 UTC | Jun 1, 11:30 UTC | 10m |
| 2026-05-29 | XATVO | - | May 29, 12:15 UTC | May 29, 14:45 UTC | 2h 30m |
| 2026-05-27 | XATVO | - | May 27, 14:05 UTC | May 27, 16:05 UTC | 2h 0m |
| 2026-05-27 | XATVO | - | May 27, 13:20 UTC | May 27, 13:30 UTC | 10m |
| 2026-05-27 | XATVO | - | May 27, 11:10 UTC | May 27, 11:50 UTC | 40m |
| 2026-05-25 | XATVO | - | May 25, 20:59 UTC | May 25, 21:54 UTC | 55m |
| 2026-05-25 | XATVO | - | May 25, 15:25 UTC | May 25, 16:35 UTC | 1h 10m |
| 2026-05-20 | XATVO | - | May 20, 17:20 UTC | May 20, 19:30 UTC | 2h 10m |
| 2026-05-19 | XATVO | - | May 19, 11:05 UTC | May 19, 13:15 UTC | 2h 10m |
| 2026-05-19 | XATVO | - | May 19, 10:05 UTC | May 19, 10:15 UTC | 10m |
| 2026-05-17 | XATVO | - | May 17, 19:20 UTC | May 17, 20:15 UTC | 55m |
| 2026-05-17 | XATVO | - | May 17, 18:10 UTC | May 17, 18:45 UTC | 35m |
| 2026-05-14 | XATVO | - | May 14, 12:10 UTC | May 14, 12:30 UTC | 20m |
| 2026-05-14 | XATVO | - | May 14, 10:00 UTC | May 14, 11:10 UTC | 1h 10m |
| 2026-05-11 | XATVO | - | May 11, 19:50 UTC | May 11, 21:30 UTC | 1h 40m |
| 2026-05-11 | XATVO | VIX → RTE | May 11, 10:45 UTC | May 11, 12:40 UTC | 1h 55m |
| 2026-05-10 | XATVO | - | May 10, 14:25 UTC | May 10, 15:19 UTC | 55m |
| 2026-05-10 | XATVO | - | May 10, 12:00 UTC | May 10, 13:05 UTC | 1h 5m |
| 2026-05-07 | XATVO | - | May 7, 20:05 UTC | May 7, 20:50 UTC | 45m |
| 2026-05-07 | XATVO | - | May 7, 10:45 UTC | May 7, 11:00 UTC | 15m |
| 2026-05-06 | XATVO | - | May 6, 15:35 UTC | May 6, 17:10 UTC | 1h 35m |
| 2026-05-05 | XATVO | - | May 5, 23:00 UTC | May 6, 00:46 UTC | 1h 45m |
| 2026-05-03 | XATVO | - | May 3, 13:15 UTC | May 3, 15:00 UTC | 1h 45m |
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-TVO page for operator, model, and routing details .