sensors Mode-S transponder
0D05D5
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-SKY · GULFSTREAM 5
- Hex
- 0D05D5
- Octal
- 03202725
- Decimal
- 853,461
- Country
- MX
- Tail
- XA-SKY
- Type
- GLF5
- Flights observed
- 21
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- Jul 25, 00:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 0D05D5 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 |
|---|---|---|---|
| XASKY | - | 21 | 2026-07-24 |
Recent flights last 21
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | XASKY | - | Jul 24, 19:20 UTC | Jul 25, 00:40 UTC | 5h 20m |
| 2026-07-22 | XASKY | - | Jul 22, 17:10 UTC | Jul 22, 19:20 UTC | 2h 10m |
| 2026-07-21 | XASKY | - | Jul 21, 20:45 UTC | Jul 21, 22:05 UTC | 1h 20m |
| 2026-07-19 | XASKY | TEB → SAN | Jul 19, 23:30 UTC | Jul 20, 04:20 UTC | 4h 50m |
| 2026-07-16 | XASKY | ATL → TEB | Jul 16, 00:05 UTC | Jul 16, 02:00 UTC | 1h 55m |
| 2026-07-14 | XASKY | - | Jul 14, 22:55 UTC | Jul 15, 00:35 UTC | 1h 40m |
| 2026-07-14 | XASKY | - | Jul 14, 13:05 UTC | Jul 14, 15:55 UTC | 2h 50m |
| 2026-07-13 | XASKY | - | Jul 13, 00:05 UTC | Jul 13, 01:15 UTC | 1h 10m |
| 2026-07-11 | XASKY | - | Jul 11, 17:10 UTC | Jul 11, 22:20 UTC | 5h 10m |
| 2026-07-06 | XASKY | - | Jul 6, 23:25 UTC | Jul 7, 00:50 UTC | 1h 25m |
| 2026-07-06 | XASKY | - | Jul 6, 21:10 UTC | Jul 6, 22:15 UTC | 1h 5m |
| 2026-06-30 | XASKY | - | Jun 30, 05:35 UTC | Jun 30, 06:00 UTC | 25m |
| 2026-06-29 | XASKY | - | Jun 29, 18:34 UTC | Jun 29, 19:49 UTC | 1h 15m |
| 2026-06-13 | XASKY | - | Jun 13, 13:55 UTC | Jun 13, 15:10 UTC | 1h 15m |
| 2026-06-12 | XASKY | - | Jun 12, 17:45 UTC | Jun 12, 19:05 UTC | 1h 20m |
| 2026-06-06 | XASKY | - | Jun 6, 16:10 UTC | Jun 7, 03:40 UTC | 11h 30m |
| 2026-05-29 | XASKY | - | May 29, 00:25 UTC | May 29, 10:30 UTC | 10h 5m |
| 2026-05-17 | XASKY | - | May 17, 16:45 UTC | May 17, 20:35 UTC | 3h 50m |
| 2026-05-15 | XASKY | - | May 15, 16:55 UTC | May 15, 20:30 UTC | 3h 35m |
| 2026-04-26 | XASKY | - | Apr 26, 18:35 UTC | Apr 26, 22:45 UTC | 4h 10m |
| 2026-04-21 | XASKY | - | Apr 21, 20:55 UTC | Apr 22, 01:00 UTC | 4h 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-SKY page for operator, model, and routing details .