sensors Mode-S transponder
0D0EA8
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VFM · BOEING 737-400
- Hex
- 0D0EA8
- Octal
- 03207250
- Decimal
- 855,720
- Country
- MX
- Tail
- XA-VFM
- Type
- B734
- Flights observed
- 59
- Distinct callsigns
- 6
- Country
- MX
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0EA8 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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VTM902 | - | Jun 2, 03:25 UTC | Jun 2, 12:20 UTC | 8h 55m |
| 2026-05-23 | VTM904 | - | May 23, 18:20 UTC | May 23, 19:50 UTC | 1h 30m |
| 2026-05-22 | VTM904 | - | May 22, 10:50 UTC | May 22, 12:05 UTC | 1h 15m |
| 2026-05-22 | VTM904 | - | May 22, 07:15 UTC | May 22, 09:20 UTC | 2h 5m |
| 2026-05-21 | VTM904 | - | May 21, 21:10 UTC | May 22, 05:35 UTC | 8h 25m |
| 2026-05-21 | VTM904 | - | May 21, 07:25 UTC | May 21, 09:40 UTC | 2h 15m |
| 2026-05-21 | VTM904 | - | May 21, 02:45 UTC | May 21, 05:35 UTC | 2h 50m |
| 2026-05-21 | VTM904 | - | May 21, 00:30 UTC | May 21, 01:00 UTC | 30m |
| 2026-05-20 | VTM904 | - | May 20, 21:55 UTC | May 20, 23:30 UTC | 1h 35m |
| 2026-05-20 | VTM904 | - | May 20, 04:25 UTC | May 20, 04:35 UTC | 10m |
| 2026-05-20 | VTM904 | - | May 20, 03:00 UTC | May 20, 03:20 UTC | 20m |
| 2026-05-17 | VTM904 | - | May 17, 17:01 UTC | May 17, 17:20 UTC | 20m |
| 2026-05-15 | VTM904 | - | May 15, 00:55 UTC | May 15, 01:20 UTC | 25m |
| 2026-05-09 | VTM5001 | - | May 9, 17:00 UTC | May 9, 17:20 UTC | 20m |
| 2026-05-09 | VTM5002 | - | May 9, 13:50 UTC | May 9, 14:10 UTC | 20m |
| 2026-05-09 | VTM5002 | - | May 9, 04:30 UTC | May 9, 13:05 UTC | 8h 35m |
| 2026-05-09 | VTM5001 | - | May 9, 03:00 UTC | May 9, 03:35 UTC | 35m |
| 2026-05-08 | VTM2208 | - | May 8, 15:15 UTC | May 8, 15:25 UTC | 10m |
| 2026-05-08 | VTM2208 | - | May 8, 14:20 UTC | May 8, 14:35 UTC | 15m |
| 2026-05-08 | VTM2207 | - | May 8, 04:44 UTC | May 8, 05:00 UTC | 15m |
| 2026-05-07 | VTM2208 | - | May 7, 15:30 UTC | May 7, 15:45 UTC | 15m |
| 2026-05-07 | VTM2207 | - | May 7, 04:50 UTC | May 7, 05:05 UTC | 15m |
| 2026-05-05 | VTM2208 | - | May 5, 15:15 UTC | May 5, 15:30 UTC | 15m |
| 2026-05-05 | VTM2207 | - | May 5, 04:45 UTC | May 5, 05:00 UTC | 15m |
| 2026-05-05 | VTM2207 | - | May 5, 03:40 UTC | May 5, 03:50 UTC | 10m |
| 2026-04-30 | VTM2208 | - | Apr 30, 14:50 UTC | Apr 30, 15:00 UTC | 10m |
| 2026-04-30 | VTM2208 | HMO → HMO | Apr 30, 14:15 UTC | Apr 30, 14:40 UTC | 25m |
| 2026-04-30 | VTM2208 | - | Apr 30, 13:50 UTC | Apr 30, 14:10 UTC | 20m |
| 2026-04-30 | VTM2207 | - | Apr 30, 04:45 UTC | Apr 30, 05:00 UTC | 15m |
| 2026-04-29 | VTM2208 | - | Apr 29, 15:05 UTC | Apr 29, 15:15 UTC | 10m |
| 2026-04-29 | VTM2208 | - | Apr 29, 14:10 UTC | Apr 29, 14:25 UTC | 15m |
| 2026-04-29 | VTM2207 | - | Apr 29, 04:39 UTC | Apr 29, 04:55 UTC | 15m |
| 2026-04-29 | VTM2207 | HMO → HMO | Apr 29, 04:00 UTC | Apr 29, 04:05 UTC | 5m |
| 2026-04-28 | VTM2208 | - | Apr 28, 15:05 UTC | Apr 28, 15:20 UTC | 15m |
| 2026-04-28 | VTM2208 | - | Apr 28, 14:15 UTC | Apr 28, 14:30 UTC | 15m |
| 2026-04-28 | VTM2207 | - | Apr 28, 04:45 UTC | Apr 28, 05:05 UTC | 20m |
| 2026-04-24 | VTM2208 | - | Apr 24, 14:50 UTC | Apr 24, 15:00 UTC | 10m |
| 2026-04-24 | VTM2208 | - | Apr 24, 14:05 UTC | Apr 24, 14:10 UTC | 5m |
| 2026-04-24 | VTM2207 | - | Apr 24, 04:35 UTC | Apr 24, 04:50 UTC | 15m |
| 2026-04-24 | VTM2207 | - | Apr 24, 03:55 UTC | Apr 24, 04:30 UTC | 35m |
| 2026-04-23 | VTM2208 | - | Apr 23, 14:50 UTC | Apr 23, 15:00 UTC | 10m |
| 2026-04-23 | VTM2208 | - | Apr 23, 13:50 UTC | Apr 23, 14:05 UTC | 15m |
| 2026-04-23 | VTM2207 | - | Apr 23, 04:40 UTC | Apr 23, 04:55 UTC | 15m |
| 2026-04-22 | VTM2208 | - | Apr 22, 14:50 UTC | Apr 22, 15:05 UTC | 15m |
| 2026-04-22 | VTM2208 | - | Apr 22, 14:10 UTC | Apr 22, 14:15 UTC | 5m |
| 2026-04-22 | VTM2207 | - | Apr 22, 04:35 UTC | Apr 22, 04:50 UTC | 15m |
| 2026-04-21 | VTM2208 | - | Apr 21, 15:01 UTC | Apr 21, 15:10 UTC | 10m |
| 2026-04-21 | VTM2207 | - | Apr 21, 05:05 UTC | Apr 21, 05:20 UTC | 15m |
| 2026-04-17 | VTM2207 | - | Apr 17, 14:35 UTC | Apr 17, 14:45 UTC | 10m |
| 2026-04-17 | VTM2207 | - | Apr 17, 04:25 UTC | Apr 17, 04:40 UTC | 16m |
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-VFM page for operator, model, and routing details .