sensors Mode-S transponder
0D0EE7
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-FMX · GULFSTREAM G500
- Hex
- 0D0EE7
- Octal
- 03207347
- Decimal
- 855,783
- Country
- MX
- Tail
- XA-FMX
- Type
- GA5C
- Flights observed
- 58
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0EE7 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 |
|---|---|---|---|
| XAFMX | - | 58 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | XAFMX | - | Jul 17, 17:30 UTC | Jul 17, 22:05 UTC | 4h 35m |
| 2026-07-16 | XAFMX | NTR → SAN | Jul 16, 16:00 UTC | Jul 16, 18:15 UTC | 2h 15m |
| 2026-07-12 | XAFMX | - | Jul 12, 21:40 UTC | Jul 13, 01:20 UTC | 3h 40m |
| 2026-07-12 | XAFMX | - | Jul 12, 16:30 UTC | Jul 12, 20:05 UTC | 3h 35m |
| 2026-07-07 | XAFMX | - | Jul 7, 20:35 UTC | Jul 7, 23:10 UTC | 2h 35m |
| 2026-07-07 | XAFMX | - | Jul 7, 18:20 UTC | Jul 7, 19:10 UTC | 50m |
| 2026-07-07 | XAFMX | - | Jul 7, 00:30 UTC | Jul 7, 01:50 UTC | 1h 20m |
| 2026-07-06 | XAFMX | - | Jul 6, 19:40 UTC | Jul 6, 20:30 UTC | 50m |
| 2026-07-06 | XAFMX | - | Jul 6, 16:50 UTC | Jul 6, 18:00 UTC | 1h 10m |
| 2026-07-05 | XAFMX | - | Jul 5, 13:30 UTC | Jul 5, 14:20 UTC | 50m |
| 2026-07-04 | XAFMX | - | Jul 4, 19:10 UTC | Jul 4, 19:40 UTC | 30m |
| 2026-07-04 | XAFMX | - | Jul 4, 14:30 UTC | Jul 4, 15:05 UTC | 35m |
| 2026-07-03 | XAFMX | - | Jul 3, 20:15 UTC | Jul 3, 21:05 UTC | 50m |
| 2026-07-03 | XAFMX | - | Jul 3, 18:20 UTC | Jul 3, 19:25 UTC | 1h 5m |
| 2026-06-30 | XAFMX | - | Jun 30, 14:25 UTC | Jun 30, 14:50 UTC | 25m |
| 2026-06-29 | XAFMX | - | Jun 29, 22:39 UTC | Jun 29, 23:49 UTC | 1h 10m |
| 2026-06-29 | XAFMX | - | Jun 29, 16:19 UTC | Jun 29, 17:14 UTC | 55m |
| 2026-06-27 | XAFMX | BGR → NTR | Jun 27, 22:45 UTC | Jun 28, 02:54 UTC | 4h 10m |
| 2026-06-27 | XAFMX | - | Jun 27, 15:30 UTC | Jun 27, 21:55 UTC | 6h 25m |
| 2026-06-26 | XAFMX | VIE → MAD | Jun 26, 13:04 UTC | Jun 26, 15:25 UTC | 2h 20m |
| 2026-06-21 | XAFMX | MAD → VIE | Jun 21, 11:15 UTC | Jun 21, 13:29 UTC | 2h 15m |
| 2026-06-19 | XAFMX | - | Jun 19, 15:49 UTC | Jun 19, 16:44 UTC | 55m |
| 2026-06-13 | XAFMX | - | Jun 13, 02:10 UTC | Jun 13, 11:05 UTC | 8h 54m |
| 2026-06-07 | XAFMX | - | Jun 7, 23:50 UTC | Jun 8, 00:30 UTC | 40m |
| 2026-06-04 | XAFMX | - | Jun 4, 21:30 UTC | Jun 4, 22:05 UTC | 35m |
| 2026-06-04 | XAFMX | - | Jun 4, 17:05 UTC | Jun 4, 18:00 UTC | 55m |
| 2026-05-31 | XAFMX | - | May 31, 23:35 UTC | Jun 1, 00:05 UTC | 30m |
| 2026-05-28 | XAFMX | - | May 28, 22:20 UTC | May 28, 22:40 UTC | 20m |
| 2026-05-27 | XAFMX | - | May 27, 21:15 UTC | May 27, 22:30 UTC | 1h 15m |
| 2026-05-27 | XAFMX | - | May 27, 19:20 UTC | May 27, 19:40 UTC | 20m |
| 2026-05-25 | XAFMX | - | May 25, 13:25 UTC | May 25, 14:35 UTC | 1h 10m |
| 2026-05-22 | XAFMX | EWR → NTR | May 22, 22:20 UTC | May 23, 02:05 UTC | 3h 45m |
| 2026-05-22 | XAFMX | - | May 22, 19:30 UTC | May 22, 20:25 UTC | 55m |
| 2026-05-18 | XAFMX | NTR → BED | May 18, 16:35 UTC | May 18, 20:05 UTC | 3h 29m |
| 2026-05-13 | XAFMX | DFW → NTR | May 13, 23:50 UTC | May 14, 01:00 UTC | 1h 10m |
| 2026-05-13 | XAFMX | NTR → DFW | May 13, 21:00 UTC | May 13, 22:15 UTC | 1h 15m |
| 2026-05-12 | XAFMX | - | May 12, 22:40 UTC | May 12, 23:25 UTC | 45m |
| 2026-05-12 | XAFMX | - | May 12, 15:55 UTC | May 12, 16:40 UTC | 45m |
| 2026-05-11 | XAFMX | - | May 11, 21:45 UTC | May 11, 22:35 UTC | 49m |
| 2026-05-11 | XAFMX | - | May 11, 13:25 UTC | May 11, 13:50 UTC | 25m |
| 2026-05-10 | XAFMX | - | May 10, 17:55 UTC | May 10, 19:00 UTC | 1h 5m |
| 2026-05-10 | XAFMX | - | May 10, 13:55 UTC | May 10, 14:20 UTC | 25m |
| 2026-05-08 | XAFMX | - | May 8, 02:49 UTC | May 8, 04:04 UTC | 1h 15m |
| 2026-05-07 | XAFMX | - | May 7, 22:59 UTC | May 8, 01:55 UTC | 2h 55m |
| 2026-05-05 | XAFMX | - | May 5, 00:25 UTC | May 5, 03:10 UTC | 2h 45m |
| 2026-05-03 | XAFMX | - | May 3, 22:00 UTC | May 3, 22:34 UTC | 35m |
| 2026-04-30 | XAFMX | - | Apr 30, 18:50 UTC | Apr 30, 19:10 UTC | 20m |
| 2026-04-29 | XAFMX | - | Apr 29, 22:10 UTC | Apr 29, 23:05 UTC | 55m |
| 2026-04-29 | XAFMX | - | Apr 29, 20:15 UTC | Apr 29, 20:35 UTC | 20m |
| 2026-04-28 | XAFMX | - | Apr 28, 22:49 UTC | Apr 28, 23:54 UTC | 1h 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-FMX page for operator, model, and routing details .