sensors Mode-S transponder
0D11ED
ICAO 24-bit transponder address · allocated to Mexico
- Hex
- 0D11ED
- Octal
- 03210755
- Decimal
- 856,557
- Country
- MX
- Flights observed
- 76
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 0D11ED 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AMX091 | Aeroméxico | 8 | 2026-06-05 |
| AMX090 | Aeroméxico | 8 | 2026-06-04 |
| AMX006 | - | 7 | 2026-06-09 |
| AMX005 | - | 7 | 2026-06-08 |
| AMX015 | Aeroméxico | 5 | 2026-06-03 |
| AMX034 | Aeroméxico | 4 | 2026-06-11 |
| AMX014 | Aeroméxico | 4 | 2026-06-03 |
| AMX039 | Aeroméxico | 3 | 2026-05-26 |
| AMX022 | Aeroméxico | 3 | 2026-06-10 |
| AMX021 | Aeroméxico | 3 | 2026-06-10 |
| AMX002 | - | 3 | 2026-05-28 |
| AMX9469 | Aeroméxico | 2 | 2026-04-30 |
| AMX9468 | - | 2 | 2026-04-29 |
| AMX181 | Aeroméxico | 2 | 2026-04-26 |
| AMX179 | Aeroméxico | 2 | 2026-04-29 |
| AMX036 | Aeroméxico | 2 | 2026-05-27 |
| AMX026 | Aeroméxico | 2 | 2026-05-30 |
| AMX025 | Aeroméxico | 2 | 2026-05-30 |
| XA AMQ | - | 1 | 2026-05-15 |
| AMX561 | Aeroméxico | 1 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-12 | AMX035 | - | Jun 12, 07:30 UTC | Jun 12, 08:30 UTC | 1h 0m |
| 2026-06-11 | AMX034 | MEX → MTY | Jun 11, 17:05 UTC | Jun 12, 02:55 UTC | 9h 50m |
| 2026-06-11 | AMX034 | MEX → MTY | Jun 11, 13:30 UTC | Jun 11, 14:45 UTC | 1h 15m |
| 2026-06-10 | AMX022 | MAD → MEX | Jun 10, 22:10 UTC | Jun 11, 08:50 UTC | 10h 40m |
| 2026-06-10 | AMX021 | MEX → MAD | Jun 10, 03:45 UTC | Jun 10, 14:05 UTC | 10h 20m |
| 2026-06-09 | AMX006 | - | Jun 9, 13:15 UTC | Jun 10, 00:05 UTC | 10h 50m |
| 2026-06-08 | AMX005 | - | Jun 8, 23:50 UTC | Jun 9, 09:55 UTC | 10h 5m |
| 2026-06-07 | AMX022 | MAD → MEX | Jun 7, 22:25 UTC | Jun 8, 09:25 UTC | 11h 0m |
| 2026-06-07 | AMX021 | MEX → MAD | Jun 7, 03:50 UTC | Jun 7, 13:15 UTC | 9h 25m |
| 2026-06-06 | AMX006 | - | Jun 6, 13:15 UTC | Jun 7, 00:44 UTC | 11h 30m |
| 2026-06-05 | AMX005 | - | Jun 5, 23:40 UTC | Jun 6, 09:24 UTC | 9h 45m |
| 2026-06-05 | AMX091 | ICN → MEX | Jun 5, 15:30 UTC | Jun 5, 15:40 UTC | 10m |
| 2026-06-05 | AMX091 | ICN → MEX | Jun 5, 02:55 UTC | Jun 5, 13:50 UTC | 10h 55m |
| 2026-06-04 | AMX090 | MTY → ICN | Jun 4, 06:15 UTC | Jun 4, 20:10 UTC | 13h 55m |
| 2026-06-04 | AMX090 | MTY → ICN | Jun 4, 03:20 UTC | Jun 4, 04:20 UTC | 1h 0m |
| 2026-06-03 | AMX015 | GRU → MEX | Jun 3, 13:20 UTC | Jun 3, 22:25 UTC | 9h 5m |
| 2026-06-03 | AMX014 | MEX → GRU | Jun 3, 01:45 UTC | Jun 3, 10:10 UTC | 8h 25m |
| 2026-06-02 | AMX015 | GRU → MEX | Jun 2, 14:00 UTC | Jun 2, 23:05 UTC | 9h 5m |
| 2026-06-02 | AMX014 | MEX → GRU | Jun 2, 01:35 UTC | Jun 2, 10:10 UTC | 8h 35m |
| 2026-06-01 | AMX015 | GRU → MEX | Jun 1, 21:35 UTC | Jun 1, 22:20 UTC | 45m |
| 2026-06-01 | AMX015 | GRU → MEX | Jun 1, 13:20 UTC | Jun 1, 21:05 UTC | 7h 45m |
| 2026-06-01 | AMX014 | MEX → GRU | Jun 1, 01:40 UTC | Jun 1, 10:25 UTC | 8h 45m |
| 2026-05-30 | AMX026 | AMS → MEX | May 30, 20:35 UTC | May 31, 09:50 UTC | 13h 15m |
| 2026-05-30 | AMX025 | MEX → AMS | May 30, 04:55 UTC | May 30, 14:50 UTC | 9h 55m |
| 2026-05-29 | AMX006 | - | May 29, 13:40 UTC | May 30, 00:40 UTC | 11h 0m |
| 2026-05-28 | AMX005 | - | May 28, 23:25 UTC | May 29, 09:10 UTC | 9h 45m |
| 2026-05-28 | AMX002 | - | May 28, 15:05 UTC | May 28, 20:10 UTC | 5h 5m |
| 2026-05-28 | AMX002 | - | May 28, 09:10 UTC | May 28, 15:00 UTC | 5h 50m |
| 2026-05-27 | AMX036 | GDL → MAD | May 27, 17:25 UTC | May 28, 02:45 UTC | 9h 20m |
| 2026-05-26 | AMX036 | GDL → MAD | May 26, 23:19 UTC | May 27, 19:35 UTC | 20h 16m |
| 2026-05-26 | AMX039 | MAD → GDL | May 26, 21:40 UTC | May 27, 19:35 UTC | 21h 56m |
| 2026-05-26 | AMX039 | MAD → GDL | May 26, 20:00 UTC | May 27, 19:15 UTC | 23h 15m |
| 2026-05-26 | AMX039 | MAD → GDL | May 26, 13:40 UTC | May 27, 00:19 UTC | 10h 40m |
| 2026-05-26 | AMX001 | - | May 26, 00:39 UTC | May 26, 10:54 UTC | 10h 15m |
| 2026-05-24 | AMX026 | AMS → MEX | May 24, 20:25 UTC | May 25, 07:45 UTC | 11h 20m |
| 2026-05-24 | AMX025 | MEX → AMS | May 24, 05:05 UTC | May 24, 15:15 UTC | 10h 10m |
| 2026-05-23 | AMX006 | - | May 23, 13:30 UTC | May 24, 01:30 UTC | 12h 1m |
| 2026-05-22 | AMX005 | - | May 22, 23:35 UTC | May 23, 09:45 UTC | 10h 9m |
| 2026-05-22 | AMX002 | - | May 22, 09:10 UTC | May 22, 20:05 UTC | 10h 55m |
| 2026-05-21 | AMX034 | MEX → MTY | May 21, 17:05 UTC | May 22, 03:00 UTC | 9h 55m |
| 2026-05-21 | AMX034 | MEX → MTY | May 21, 13:40 UTC | May 21, 14:50 UTC | 1h 10m |
| 2026-05-20 | AMX022 | MAD → MEX | May 20, 22:00 UTC | May 21, 08:50 UTC | 10h 50m |
| 2026-05-20 | AMX021 | MEX → MAD | May 20, 04:20 UTC | May 20, 14:35 UTC | 10h 16m |
| 2026-05-18 | AMX006 | - | May 18, 13:35 UTC | May 19, 01:10 UTC | 11h 34m |
| 2026-05-17 | AMX005 | - | May 17, 23:40 UTC | May 18, 09:35 UTC | 9h 55m |
| 2026-05-17 | AMX091 | ICN → MEX | May 17, 16:10 UTC | May 17, 16:15 UTC | 5m |
| 2026-05-17 | AMX091 | ICN → MEX | May 17, 03:15 UTC | May 17, 14:35 UTC | 11h 20m |
| 2026-05-16 | AMX090 | MTY → ICN | May 16, 06:20 UTC | May 16, 20:25 UTC | 14h 5m |
| 2026-05-16 | AMX090 | MTY → ICN | May 16, 03:05 UTC | May 16, 04:15 UTC | 1h 10m |
| 2026-05-15 | AMX091 | ICN → MEX | May 15, 16:25 UTC | May 15, 16:35 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.