sensors Mode-S transponder
0D0E2F
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-KID · LEARJET 35
- Hex
- 0D0E2F
- Octal
- 03207057
- Decimal
- 855,599
- Country
- MX
- Tail
- XA-KID
- Type
- LJ35
- Flights observed
- 57
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0E2F 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 |
|---|---|---|---|
| XAKID | - | 57 | 2026-07-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | XAKID | - | Jul 19, 17:30 UTC | Jul 19, 19:20 UTC | 1h 50m |
| 2026-07-19 | XAKID | - | Jul 19, 13:15 UTC | Jul 19, 15:15 UTC | 2h 0m |
| 2026-07-15 | XAKID | - | Jul 15, 22:35 UTC | Jul 15, 23:55 UTC | 1h 20m |
| 2026-07-15 | XAKID | - | Jul 15, 19:00 UTC | Jul 15, 20:05 UTC | 1h 5m |
| 2026-07-14 | XAKID | - | Jul 14, 20:35 UTC | Jul 15, 00:30 UTC | 3h 54m |
| 2026-07-14 | XAKID | - | Jul 14, 15:35 UTC | Jul 14, 17:25 UTC | 1h 50m |
| 2026-07-13 | XAKID | - | Jul 13, 22:10 UTC | Jul 13, 22:45 UTC | 35m |
| 2026-07-13 | XAKID | - | Jul 13, 19:50 UTC | Jul 13, 20:00 UTC | 10m |
| 2026-07-13 | XAKID | - | Jul 13, 14:40 UTC | Jul 13, 14:55 UTC | 15m |
| 2026-07-11 | XAKID | - | Jul 11, 17:10 UTC | Jul 11, 17:35 UTC | 25m |
| 2026-07-10 | XAKID | MTY → MTY | Jul 10, 13:40 UTC | Jul 10, 21:20 UTC | 7h 40m |
| 2026-07-10 | XAKID | - | Jul 10, 12:05 UTC | Jul 10, 13:10 UTC | 1h 5m |
| 2026-06-26 | XAKID | - | Jun 26, 13:24 UTC | Jun 26, 21:04 UTC | 7h 40m |
| 2026-06-20 | XAKID | - | Jun 20, 21:49 UTC | Jun 20, 22:10 UTC | 20m |
| 2026-06-20 | XAKID | EFD → HMO | Jun 20, 00:24 UTC | Jun 20, 19:24 UTC | 19h 0m |
| 2026-06-19 | XAKID | - | Jun 19, 18:34 UTC | Jun 19, 19:45 UTC | 1h 10m |
| 2026-06-16 | XAKID | - | Jun 16, 16:30 UTC | Jun 16, 17:40 UTC | 1h 10m |
| 2026-06-16 | XAKID | - | Jun 16, 01:55 UTC | Jun 16, 03:15 UTC | 1h 20m |
| 2026-06-15 | XAKID | - | Jun 15, 16:19 UTC | Jun 15, 16:55 UTC | 35m |
| 2026-06-15 | XAKID | - | Jun 15, 15:04 UTC | Jun 15, 15:45 UTC | 40m |
| 2026-06-11 | XAKID | - | Jun 11, 21:00 UTC | Jun 11, 22:15 UTC | 1h 15m |
| 2026-06-10 | XAKID | - | Jun 10, 22:15 UTC | Jun 10, 23:00 UTC | 45m |
| 2026-06-10 | XAKID | - | Jun 10, 18:55 UTC | Jun 10, 20:00 UTC | 1h 5m |
| 2026-06-07 | XAKID | - | Jun 7, 14:35 UTC | Jun 7, 14:50 UTC | 15m |
| 2026-06-07 | XAKID | - | Jun 7, 01:09 UTC | Jun 7, 01:20 UTC | 10m |
| 2026-06-04 | XAKID | - | Jun 4, 19:30 UTC | Jun 4, 20:25 UTC | 55m |
| 2026-06-03 | XAKID | - | Jun 3, 18:15 UTC | Jun 3, 19:35 UTC | 1h 20m |
| 2026-06-03 | XAKID | - | Jun 3, 13:10 UTC | Jun 3, 14:20 UTC | 1h 10m |
| 2026-05-30 | XAKID | - | May 30, 02:00 UTC | May 30, 04:25 UTC | 2h 25m |
| 2026-05-29 | XAKID | - | May 29, 22:55 UTC | May 29, 23:45 UTC | 50m |
| 2026-05-22 | XAKID | - | May 22, 17:05 UTC | May 22, 17:45 UTC | 40m |
| 2026-05-21 | XAKID | - | May 21, 23:15 UTC | May 21, 23:45 UTC | 30m |
| 2026-05-21 | XAKID | - | May 21, 15:10 UTC | May 21, 15:30 UTC | 20m |
| 2026-05-21 | XAKID | - | May 21, 13:25 UTC | May 21, 14:00 UTC | 35m |
| 2026-05-13 | XAKID | - | May 13, 23:55 UTC | May 14, 00:15 UTC | 20m |
| 2026-05-13 | XAKID | - | May 13, 19:25 UTC | May 13, 21:25 UTC | 2h 0m |
| 2026-05-13 | XAKID | - | May 13, 14:25 UTC | May 13, 16:10 UTC | 1h 45m |
| 2026-05-08 | XAKID | - | May 8, 19:25 UTC | May 8, 19:45 UTC | 20m |
| 2026-05-08 | XAKID | - | May 8, 16:15 UTC | May 8, 16:35 UTC | 20m |
| 2026-05-07 | XAKID | - | May 7, 00:50 UTC | May 7, 01:15 UTC | 25m |
| 2026-05-06 | XAKID | - | May 6, 23:50 UTC | May 7, 00:10 UTC | 20m |
| 2026-05-06 | XAKID | - | May 6, 21:35 UTC | May 6, 21:50 UTC | 15m |
| 2026-05-06 | XAKID | - | May 6, 20:25 UTC | May 6, 20:36 UTC | 11m |
| 2026-05-06 | XAKID | - | May 6, 15:10 UTC | May 6, 15:35 UTC | 25m |
| 2026-05-06 | XAKID | - | May 6, 13:10 UTC | May 6, 14:15 UTC | 1h 5m |
| 2026-04-29 | XAKID | - | Apr 29, 22:00 UTC | Apr 29, 22:30 UTC | 30m |
| 2026-04-29 | XAKID | - | Apr 29, 15:30 UTC | Apr 29, 16:05 UTC | 35m |
| 2026-04-28 | XAKID | - | Apr 28, 21:55 UTC | Apr 28, 23:54 UTC | 2h 0m |
| 2026-04-28 | XAKID | - | Apr 28, 16:40 UTC | Apr 28, 18:50 UTC | 2h 10m |
| 2026-04-27 | XAKID | - | Apr 27, 03:10 UTC | Apr 27, 03:55 UTC | 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-KID page for operator, model, and routing details .