sensors Mode-S transponder
0D104C
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-YNZ · HAWKER BEECHCRAFT Hawker 750/850
- Hex
- 0D104C
- Octal
- 03210114
- Decimal
- 856,140
- Country
- MX
- Tail
- XA-YNZ
- Type
- H25B
- Flights observed
- 135
- Distinct callsigns
- 6
- Country
- MX
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 0D104C 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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | VTM7701 | - | Jul 17, 01:45 UTC | Jul 17, 16:19 UTC | 14h 35m |
| 2026-07-16 | VTM7701 | - | Jul 16, 01:25 UTC | Jul 16, 16:25 UTC | 15h 0m |
| 2026-07-15 | VTM7702 | - | Jul 15, 01:45 UTC | Jul 15, 16:25 UTC | 14h 40m |
| 2026-07-14 | VTM7702 | - | Jul 14, 15:20 UTC | Jul 14, 16:15 UTC | 55m |
| 2026-07-10 | VTM7701 | - | Jul 10, 01:35 UTC | Jul 10, 02:35 UTC | 1h 0m |
| 2026-07-09 | VTM7701 | - | Jul 9, 01:25 UTC | Jul 9, 16:45 UTC | 15h 20m |
| 2026-07-08 | VTM7701 | - | Jul 8, 01:40 UTC | Jul 8, 16:20 UTC | 14h 40m |
| 2026-07-07 | VTM7701 | - | Jul 7, 02:20 UTC | Jul 7, 16:30 UTC | 14h 10m |
| 2026-07-03 | VTM7702 | - | Jul 3, 03:50 UTC | Jul 3, 16:25 UTC | 12h 35m |
| 2026-07-03 | VTM7701 | - | Jul 3, 01:35 UTC | Jul 3, 02:55 UTC | 1h 20m |
| 2026-07-02 | VTM7702 | - | Jul 2, 15:15 UTC | Jul 2, 16:40 UTC | 1h 25m |
| 2026-07-02 | VTM7701 | - | Jul 2, 03:35 UTC | Jul 2, 14:30 UTC | 10h 55m |
| 2026-07-02 | VTM7701 | - | Jul 2, 01:30 UTC | Jul 2, 02:50 UTC | 1h 20m |
| 2026-07-01 | VTM7702 | - | Jul 1, 15:30 UTC | Jul 1, 17:00 UTC | 1h 30m |
| 2026-07-01 | VTM7701 | - | Jul 1, 03:45 UTC | Jul 1, 14:40 UTC | 10h 55m |
| 2026-07-01 | VTM7701 | - | Jul 1, 01:30 UTC | Jul 1, 02:50 UTC | 1h 20m |
| 2026-06-30 | VTM7702 | - | Jun 30, 15:10 UTC | Jun 30, 16:40 UTC | 1h 30m |
| 2026-06-30 | VTM7701 | - | Jun 30, 03:30 UTC | Jun 30, 14:35 UTC | 11h 5m |
| 2026-06-30 | VTM7701 | - | Jun 30, 01:19 UTC | Jun 30, 02:45 UTC | 1h 26m |
| 2026-06-26 | VTM7702 | - | Jun 26, 14:59 UTC | Jun 26, 16:24 UTC | 1h 25m |
| 2026-06-26 | VTM7702 | - | Jun 26, 13:45 UTC | Jun 26, 14:09 UTC | 25m |
| 2026-06-24 | VTM7701 | - | Jun 24, 03:29 UTC | Jun 24, 04:34 UTC | 1h 5m |
| 2026-06-24 | VTM7701 | - | Jun 24, 01:19 UTC | Jun 24, 02:45 UTC | 1h 25m |
| 2026-06-23 | VTM7702 | - | Jun 23, 14:59 UTC | Jun 23, 16:20 UTC | 1h 20m |
| 2026-06-23 | VTM7701 | - | Jun 23, 03:09 UTC | Jun 23, 14:19 UTC | 11h 10m |
| 2026-06-23 | VTM7701 | - | Jun 23, 00:54 UTC | Jun 23, 02:20 UTC | 1h 25m |
| 2026-06-19 | VTM7701 | - | Jun 19, 14:49 UTC | Jun 19, 16:14 UTC | 1h 25m |
| 2026-06-19 | VTM7701 | - | Jun 19, 03:24 UTC | Jun 19, 13:59 UTC | 10h 35m |
| 2026-06-19 | VTM7701 | - | Jun 19, 00:55 UTC | Jun 19, 02:24 UTC | 1h 30m |
| 2026-06-18 | VTM7702 | - | Jun 18, 15:20 UTC | Jun 18, 16:45 UTC | 1h 25m |
| 2026-06-18 | VTM7701 | - | Jun 18, 03:10 UTC | Jun 18, 14:25 UTC | 11h 15m |
| 2026-06-18 | VTM7701 | - | Jun 18, 00:55 UTC | Jun 18, 02:15 UTC | 1h 20m |
| 2026-06-17 | VTM7702 | - | Jun 17, 15:15 UTC | Jun 17, 16:45 UTC | 1h 30m |
| 2026-06-17 | VTM7701 | - | Jun 17, 03:50 UTC | Jun 17, 14:30 UTC | 10h 40m |
| 2026-06-17 | VTM7701 | - | Jun 17, 01:25 UTC | Jun 17, 02:50 UTC | 1h 25m |
| 2026-06-16 | VTM7702 | - | Jun 16, 15:05 UTC | Jun 16, 16:30 UTC | 1h 25m |
| 2026-06-16 | VTM7701 | - | Jun 16, 03:25 UTC | Jun 16, 14:15 UTC | 10h 50m |
| 2026-06-16 | VTM7701 | - | Jun 16, 01:15 UTC | Jun 16, 02:40 UTC | 1h 25m |
| 2026-06-12 | VTM7702 | - | Jun 12, 14:50 UTC | Jun 12, 16:15 UTC | 1h 25m |
| 2026-06-12 | VTM7701 | - | Jun 12, 03:25 UTC | Jun 12, 14:01 UTC | 10h 35m |
| 2026-06-12 | VTM7701 | - | Jun 12, 01:00 UTC | Jun 12, 02:30 UTC | 1h 30m |
| 2026-06-11 | VTM7702 | - | Jun 11, 15:15 UTC | Jun 11, 16:35 UTC | 1h 20m |
| 2026-06-11 | VTM7701 | - | Jun 11, 03:30 UTC | Jun 11, 14:20 UTC | 10h 50m |
| 2026-06-11 | VTM7701 | - | Jun 11, 01:20 UTC | Jun 11, 02:50 UTC | 1h 30m |
| 2026-06-10 | VTM7702 | - | Jun 10, 15:15 UTC | Jun 10, 16:40 UTC | 1h 25m |
| 2026-06-10 | VTM7701 | - | Jun 10, 03:45 UTC | Jun 10, 14:10 UTC | 10h 25m |
| 2026-06-10 | VTM7701 | - | Jun 10, 01:40 UTC | Jun 10, 03:00 UTC | 1h 20m |
| 2026-06-09 | VTM7702 | - | Jun 9, 15:00 UTC | Jun 9, 15:50 UTC | 50m |
| 2026-06-09 | VTM7701 | - | Jun 9, 03:25 UTC | Jun 9, 14:15 UTC | 10h 50m |
| 2026-06-09 | VTM7701 | - | Jun 9, 01:20 UTC | Jun 9, 02:45 UTC | 1h 25m |
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-YNZ page for operator, model, and routing details .