sensors Mode-S transponder
0D10CF
ICAO 24-bit transponder address · allocated to Mexico
- Hex
- 0D10CF
- Octal
- 03210317
- Decimal
- 856,271
- Country
- MX
- Flights observed
- 27
- Distinct callsigns
- 0
- Country
- MX
- Last broadcast
- Jul 26, 00:35 UTC
Last known position
Country allocation
The ICAO 24-bit address 0D10CF 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.
Recent flights last 27
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | - | - | Jul 25, 17:30 UTC | Jul 26, 00:35 UTC | 7h 5m |
| 2026-07-21 | - | - | Jul 21, 19:55 UTC | Jul 22, 00:35 UTC | 4h 40m |
| 2026-07-20 | - | VER → VER | Jul 20, 13:30 UTC | Jul 20, 18:40 UTC | 5h 10m |
| 2026-07-19 | - | - | Jul 19, 04:05 UTC | Jul 19, 04:25 UTC | 20m |
| 2026-07-17 | - | - | Jul 17, 23:39 UTC | Jul 18, 00:04 UTC | 25m |
| 2026-07-08 | - | - | Jul 8, 16:00 UTC | Jul 8, 16:50 UTC | 50m |
| 2026-07-06 | - | - | Jul 6, 21:50 UTC | Jul 7, 16:15 UTC | 18h 25m |
| 2026-07-06 | - | - | Jul 6, 21:15 UTC | Jul 7, 16:15 UTC | 19h 0m |
| 2026-07-06 | - | CUN → VER | Jul 6, 19:00 UTC | Jul 6, 20:30 UTC | 1h 30m |
| 2026-07-04 | - | - | Jul 4, 19:35 UTC | Jul 4, 21:10 UTC | 1h 35m |
| 2026-07-03 | - | - | Jul 3, 16:00 UTC | Jul 4, 01:50 UTC | 9h 50m |
| 2026-06-30 | - | - | Jun 30, 22:55 UTC | Jun 30, 23:35 UTC | 40m |
| 2026-06-25 | - | - | Jun 25, 21:59 UTC | Jun 25, 22:24 UTC | 25m |
| 2026-06-23 | - | - | Jun 23, 15:30 UTC | Jun 23, 15:50 UTC | 20m |
| 2026-06-18 | - | - | Jun 18, 19:50 UTC | Jun 18, 20:15 UTC | 25m |
| 2026-06-15 | - | - | Jun 15, 17:20 UTC | Jun 15, 17:59 UTC | 40m |
| 2026-06-12 | - | - | Jun 12, 17:40 UTC | Jun 12, 18:05 UTC | 25m |
| 2026-06-11 | - | - | Jun 11, 22:15 UTC | Jun 11, 22:25 UTC | 10m |
| 2026-06-05 | - | - | Jun 5, 22:20 UTC | Jun 5, 22:25 UTC | 5m |
| 2026-06-04 | - | - | Jun 4, 00:35 UTC | Jun 4, 00:40 UTC | 5m |
| 2026-05-30 | - | - | May 30, 15:50 UTC | May 30, 17:05 UTC | 1h 15m |
| 2026-05-29 | - | - | May 29, 17:45 UTC | May 29, 18:10 UTC | 25m |
| 2026-05-29 | - | - | May 29, 16:10 UTC | May 29, 16:30 UTC | 20m |
| 2026-05-28 | - | - | May 28, 16:50 UTC | May 28, 17:10 UTC | 20m |
| 2026-05-28 | - | - | May 28, 15:25 UTC | May 28, 15:45 UTC | 20m |
| 2026-04-17 | - | - | Apr 17, 18:20 UTC | Apr 17, 18:40 UTC | 20m |
| 2026-04-17 | - | - | Apr 17, 17:05 UTC | Apr 17, 17:15 UTC | 10m |
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.