sensors Mode-S transponder
0D0FDB
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-ILS · BOEING 737-400
- Hex
- 0D0FDB
- Octal
- 03207733
- Decimal
- 856,027
- Country
- MX
- Tail
- XA-ILS
- Type
- B734
- Flights observed
- 54
- Distinct callsigns
- 7
- Country
- MX
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0FDB 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 7 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VTM6657 | - | Jun 2, 07:35 UTC | Jun 2, 13:15 UTC | 5h 40m |
| 2026-05-29 | VTM7756 | - | May 29, 05:15 UTC | May 29, 12:35 UTC | 7h 20m |
| 2026-05-27 | VTM7756 | - | May 27, 11:35 UTC | May 28, 06:10 UTC | 18h 35m |
| 2026-05-27 | VTM7756 | - | May 27, 05:19 UTC | May 27, 12:30 UTC | 7h 10m |
| 2026-05-26 | VTM7756 | - | May 26, 11:39 UTC | May 27, 05:29 UTC | 17h 50m |
| 2026-05-26 | VTM7756 | - | May 26, 05:34 UTC | May 26, 12:30 UTC | 6h 55m |
| 2026-05-22 | VTM7756 | - | May 22, 05:35 UTC | May 22, 12:40 UTC | 7h 5m |
| 2026-05-21 | VTM7756 | - | May 21, 11:30 UTC | May 22, 05:35 UTC | 18h 5m |
| 2026-05-21 | VTM7756 | - | May 21, 05:20 UTC | May 21, 12:15 UTC | 6h 55m |
| 2026-05-20 | VTM7756 | - | May 20, 11:40 UTC | May 21, 05:50 UTC | 18h 10m |
| 2026-05-20 | VTM7756 | - | May 20, 05:45 UTC | May 20, 12:25 UTC | 6h 40m |
| 2026-05-19 | VTM7756 | - | May 19, 11:55 UTC | May 20, 05:55 UTC | 18h 1m |
| 2026-05-19 | VTM7756 | - | May 19, 05:15 UTC | May 19, 12:45 UTC | 7h 30m |
| 2026-05-15 | VTM7756 | - | May 15, 11:35 UTC | May 15, 12:30 UTC | 55m |
| 2026-05-12 | VTM2207 | - | May 12, 05:10 UTC | May 12, 05:30 UTC | 20m |
| 2026-05-12 | VTM2207 | - | May 12, 03:35 UTC | May 12, 03:45 UTC | 10m |
| 2026-05-11 | VTM5002 | - | May 11, 14:20 UTC | May 11, 14:40 UTC | 20m |
| 2026-05-11 | VTM5002 | - | May 11, 12:45 UTC | May 11, 13:35 UTC | 50m |
| 2026-05-11 | VTM5002 | - | May 11, 11:50 UTC | May 11, 12:05 UTC | 15m |
| 2026-05-11 | VTM5002 | - | May 11, 05:00 UTC | May 11, 05:25 UTC | 25m |
| 2026-05-11 | VTM5002 | - | May 11, 02:50 UTC | May 11, 03:30 UTC | 40m |
| 2026-05-10 | VTM5002 | - | May 10, 14:04 UTC | May 10, 14:25 UTC | 20m |
| 2026-05-10 | VTM5002 | - | May 10, 12:44 UTC | May 10, 13:30 UTC | 45m |
| 2026-05-10 | VTM5002 | - | May 10, 04:29 UTC | May 10, 12:05 UTC | 7h 35m |
| 2026-05-09 | VTM4402 | - | May 9, 10:50 UTC | May 10, 04:45 UTC | 17h 55m |
| 2026-05-09 | VTM4402 | - | May 9, 00:55 UTC | May 9, 11:15 UTC | 10h 20m |
| 2026-05-08 | VTM4402 | - | May 8, 04:25 UTC | May 8, 14:30 UTC | 10h 5m |
| 2026-05-07 | VTM9904 | - | May 7, 10:50 UTC | May 8, 04:49 UTC | 18h 0m |
| 2026-05-07 | VTM9905 | - | May 7, 10:20 UTC | May 8, 04:49 UTC | 18h 29m |
| 2026-05-07 | VTM9905 | - | May 7, 04:50 UTC | May 8, 04:39 UTC | 23h 50m |
| 2026-05-07 | VTM9905 | - | May 7, 04:30 UTC | May 7, 11:05 UTC | 6h 35m |
| 2026-05-06 | VTM9905 | - | May 6, 09:55 UTC | May 7, 05:00 UTC | 19h 4m |
| 2026-05-06 | VTM9905 | - | May 6, 04:50 UTC | May 7, 04:45 UTC | 23h 54m |
| 2026-05-06 | VTM9905 | - | May 6, 04:20 UTC | May 6, 10:35 UTC | 6h 15m |
| 2026-05-05 | VTM9905 | - | May 5, 10:50 UTC | May 6, 10:35 UTC | 23h 45m |
| 2026-05-05 | VTM9905 | - | May 5, 10:30 UTC | May 6, 04:50 UTC | 18h 20m |
| 2026-04-29 | VTM7756 | - | Apr 29, 11:35 UTC | Apr 30, 05:35 UTC | 18h 0m |
| 2026-04-29 | VTM7756 | - | Apr 29, 05:20 UTC | Apr 29, 12:15 UTC | 6h 56m |
| 2026-04-28 | VTM7756 | - | Apr 28, 11:35 UTC | Apr 29, 05:40 UTC | 18h 5m |
| 2026-04-28 | VTM7756 | - | Apr 28, 05:15 UTC | Apr 28, 12:30 UTC | 7h 15m |
| 2026-04-24 | VTM7756 | - | Apr 24, 05:15 UTC | Apr 24, 12:25 UTC | 7h 10m |
| 2026-04-23 | VTM7756 | - | Apr 23, 11:30 UTC | Apr 24, 05:35 UTC | 18h 5m |
| 2026-04-23 | VTM7756 | - | Apr 23, 05:10 UTC | Apr 23, 12:10 UTC | 7h 0m |
| 2026-04-22 | VTM7756 | - | Apr 22, 11:45 UTC | Apr 23, 05:40 UTC | 17h 55m |
| 2026-04-22 | VTM7756 | - | Apr 22, 05:20 UTC | Apr 22, 12:35 UTC | 7h 15m |
| 2026-04-21 | VTM7756 | - | Apr 21, 11:35 UTC | Apr 22, 05:45 UTC | 18h 10m |
| 2026-04-21 | VTM7756 | - | Apr 21, 05:10 UTC | Apr 21, 12:20 UTC | 7h 10m |
| 2026-04-17 | VTM7756 | - | Apr 17, 11:25 UTC | Apr 17, 12:10 UTC | 45m |
| 2026-04-16 | VTM7756 | - | Apr 16, 11:39 UTC | Apr 16, 12:19 UTC | 40m |
| 2026-04-16 | VTM6657 | - | Apr 16, 05:29 UTC | Apr 16, 05:49 UTC | 20m |
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-ILS page for operator, model, and routing details .