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
- 90
- Distinct callsigns
- 11
- Country
- MX
- Last broadcast
- 19h 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 11 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | VTM7756 | - | Jul 17, 05:30 UTC | Jul 17, 12:25 UTC | 6h 55m |
| 2026-07-17 | VTM181 | - | Jul 17, 02:30 UTC | Jul 17, 02:45 UTC | 15m |
| 2026-07-14 | VTM181 | - | Jul 14, 17:45 UTC | Jul 14, 20:20 UTC | 2h 35m |
| 2026-07-13 | VTM181 | LRD → SDF | Jul 13, 23:35 UTC | Jul 14, 01:55 UTC | 2h 20m |
| 2026-07-13 | VTM8802 | - | Jul 13, 15:50 UTC | Jul 13, 22:25 UTC | 6h 35m |
| 2026-07-03 | VTM8802 | - | Jul 3, 13:05 UTC | Jul 3, 13:15 UTC | 10m |
| 2026-07-03 | VTM6657 | - | Jul 3, 03:15 UTC | Jul 3, 11:50 UTC | 8h 35m |
| 2026-07-02 | VTM6657 | - | Jul 2, 13:50 UTC | Jul 3, 11:50 UTC | 22h 0m |
| 2026-07-02 | VTM7756 | - | Jul 2, 11:25 UTC | Jul 3, 05:50 UTC | 18h 25m |
| 2026-07-02 | VTM7756 | - | Jul 2, 05:20 UTC | Jul 3, 03:15 UTC | 21h 55m |
| 2026-07-01 | VTM7756 | - | Jul 1, 11:30 UTC | Jul 2, 05:35 UTC | 18h 5m |
| 2026-07-01 | VTM7756 | - | Jul 1, 05:05 UTC | Jul 1, 12:25 UTC | 7h 20m |
| 2026-06-30 | VTM7756 | - | Jun 30, 11:40 UTC | Jul 1, 05:30 UTC | 17h 50m |
| 2026-06-26 | VTM7701 | - | Jun 26, 03:29 UTC | Jun 26, 04:39 UTC | 1h 10m |
| 2026-06-26 | VTM7701 | - | Jun 26, 01:20 UTC | Jun 26, 02:44 UTC | 1h 25m |
| 2026-06-25 | VTM7702 | - | Jun 25, 15:50 UTC | Jun 25, 17:14 UTC | 1h 25m |
| 2026-06-25 | VTM6657 | - | Jun 25, 05:20 UTC | Jun 25, 14:50 UTC | 9h 30m |
| 2026-06-24 | VTM7756 | - | Jun 24, 11:24 UTC | Jun 25, 06:00 UTC | 18h 35m |
| 2026-06-24 | VTM7756 | - | Jun 24, 05:24 UTC | Jun 24, 12:09 UTC | 6h 45m |
| 2026-06-23 | VTM7756 | - | Jun 23, 11:35 UTC | Jun 24, 05:40 UTC | 18h 5m |
| 2026-06-23 | VTM7756 | - | Jun 23, 05:04 UTC | Jun 23, 12:35 UTC | 7h 30m |
| 2026-06-19 | VTM7756 | - | Jun 19, 05:24 UTC | Jun 19, 12:34 UTC | 7h 10m |
| 2026-06-18 | VTM6657 | - | Jun 18, 12:10 UTC | Jun 19, 05:59 UTC | 17h 49m |
| 2026-06-11 | VTM7756 | - | Jun 11, 11:30 UTC | Jun 12, 05:15 UTC | 17h 45m |
| 2026-06-11 | VTM7756 | - | Jun 11, 05:10 UTC | Jun 12, 04:45 UTC | 23h 36m |
| 2026-06-10 | VTM7756 | - | Jun 10, 11:45 UTC | Jun 11, 05:45 UTC | 18h 0m |
| 2026-06-10 | VTM6657 | - | Jun 10, 05:30 UTC | Jun 10, 12:10 UTC | 6h 40m |
| 2026-06-09 | VTM7756 | - | Jun 9, 11:35 UTC | Jun 10, 05:45 UTC | 18h 10m |
| 2026-06-09 | VTM7756 | - | Jun 9, 05:40 UTC | Jun 9, 12:30 UTC | 6h 50m |
| 2026-06-05 | VTM7756 | - | Jun 5, 06:35 UTC | Jun 5, 12:35 UTC | 6h 0m |
| 2026-06-04 | VTM7756 | - | Jun 4, 11:45 UTC | Jun 5, 07:05 UTC | 19h 20m |
| 2026-06-04 | VTM7756 | - | Jun 4, 05:50 UTC | Jun 4, 12:35 UTC | 6h 45m |
| 2026-06-03 | VTM6657 | - | Jun 3, 11:35 UTC | Jun 4, 06:15 UTC | 18h 40m |
| 2026-06-03 | VTM6657 | - | Jun 3, 05:40 UTC | Jun 3, 12:20 UTC | 6h 40m |
| 2026-06-02 | VTM7756 | - | Jun 2, 12:50 UTC | Jun 3, 12:20 UTC | 23h 30m |
| 2026-06-02 | VTM7756 | - | Jun 2, 12:25 UTC | Jun 3, 05:50 UTC | 17h 25m |
| 2026-06-02 | VTM6657 | - | Jun 2, 07:35 UTC | Jun 3, 05:50 UTC | 22h 15m |
| 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 |
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 .