sensors Mode-S transponder
0D0EC9
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VFQ · BOMBARDIER Regional Jet CRJ-200
- Hex
- 0D0EC9
- Octal
- 03207311
- Decimal
- 855,753
- Country
- MX
- Tail
- XA-VFQ
- Type
- CRJ2
- Flights observed
- 58
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0EC9 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 |
|---|---|---|---|
| VTM680 | - | 58 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-06 | VTM680 | - | Jun 6, 20:35 UTC | Jun 6, 23:55 UTC | 3h 20m |
| 2026-06-06 | VTM680 | - | Jun 6, 18:29 UTC | Jun 6, 19:19 UTC | 50m |
| 2026-06-05 | VTM680 | - | Jun 5, 14:15 UTC | Jun 5, 17:30 UTC | 3h 15m |
| 2026-06-04 | VTM680 | - | Jun 4, 20:45 UTC | Jun 5, 13:25 UTC | 16h 40m |
| 2026-06-04 | VTM680 | - | Jun 4, 16:50 UTC | Jun 4, 17:35 UTC | 45m |
| 2026-06-03 | VTM680 | - | Jun 3, 22:00 UTC | Jun 4, 01:20 UTC | 3h 20m |
| 2026-06-03 | VTM680 | - | Jun 3, 19:45 UTC | Jun 3, 20:20 UTC | 35m |
| 2026-06-02 | VTM680 | - | Jun 2, 20:20 UTC | Jun 3, 20:15 UTC | 23h 55m |
| 2026-06-02 | VTM680 | - | Jun 2, 17:20 UTC | Jun 2, 20:35 UTC | 3h 15m |
| 2026-06-01 | VTM680 | LRD → TOL | Jun 1, 23:00 UTC | Jun 2, 01:45 UTC | 2h 45m |
| 2026-06-01 | VTM680 | - | Jun 1, 21:00 UTC | Jun 1, 21:45 UTC | 45m |
| 2026-06-01 | VTM680 | - | Jun 1, 15:55 UTC | Jun 1, 16:05 UTC | 10m |
| 2026-05-29 | VTM680 | - | May 29, 00:50 UTC | May 29, 17:35 UTC | 16h 45m |
| 2026-05-28 | VTM680 | - | May 28, 04:50 UTC | May 28, 06:00 UTC | 1h 10m |
| 2026-05-28 | VTM680 | - | May 28, 03:00 UTC | May 28, 03:35 UTC | 35m |
| 2026-05-23 | VTM680 | - | May 23, 01:00 UTC | May 23, 01:25 UTC | 25m |
| 2026-05-22 | VTM680 | LRD → LRD | May 22, 16:50 UTC | May 22, 22:05 UTC | 5h 15m |
| 2026-05-21 | VTM680 | - | May 21, 07:30 UTC | May 21, 09:50 UTC | 2h 20m |
| 2026-05-21 | VTM680 | - | May 21, 03:50 UTC | May 21, 06:15 UTC | 2h 25m |
| 2026-05-20 | VTM680 | LRD → LRD | May 20, 19:25 UTC | May 21, 02:35 UTC | 7h 10m |
| 2026-05-19 | VTM680 | - | May 19, 21:30 UTC | May 20, 01:05 UTC | 3h 35m |
| 2026-05-19 | VTM680 | - | May 19, 18:20 UTC | May 19, 20:25 UTC | 2h 5m |
| 2026-05-19 | VTM680 | - | May 19, 16:25 UTC | May 19, 17:30 UTC | 1h 5m |
| 2026-05-19 | VTM680 | - | May 19, 07:30 UTC | May 19, 15:10 UTC | 7h 40m |
| 2026-05-16 | VTM680 | - | May 16, 07:41 UTC | May 16, 09:56 UTC | 2h 15m |
| 2026-05-16 | VTM680 | - | May 16, 05:56 UTC | May 16, 06:50 UTC | 55m |
| 2026-05-15 | VTM680 | - | May 15, 18:05 UTC | May 15, 21:45 UTC | 3h 40m |
| 2026-05-15 | VTM680 | - | May 15, 16:10 UTC | May 15, 17:05 UTC | 55m |
| 2026-05-14 | VTM680 | - | May 14, 06:10 UTC | May 14, 09:40 UTC | 3h 30m |
| 2026-05-14 | VTM680 | LRD → LRD | May 14, 01:10 UTC | May 14, 04:55 UTC | 3h 45m |
| 2026-05-13 | VTM680 | - | May 13, 03:30 UTC | May 13, 07:10 UTC | 3h 40m |
| 2026-05-12 | VTM680 | - | May 12, 23:10 UTC | May 13, 02:25 UTC | 3h 15m |
| 2026-05-12 | VTM680 | - | May 12, 21:05 UTC | May 12, 21:45 UTC | 40m |
| 2026-05-12 | VTM680 | - | May 12, 17:55 UTC | May 12, 18:10 UTC | 15m |
| 2026-05-09 | VTM680 | - | May 9, 22:05 UTC | May 10, 01:55 UTC | 3h 50m |
| 2026-05-09 | VTM680 | LRD → IAG | May 9, 00:35 UTC | May 9, 03:35 UTC | 3h 0m |
| 2026-05-08 | VTM680 | - | May 8, 14:40 UTC | May 8, 23:25 UTC | 8h 45m |
| 2026-05-08 | VTM680 | - | May 8, 10:49 UTC | May 8, 13:25 UTC | 2h 35m |
| 2026-05-07 | VTM680 | - | May 7, 06:10 UTC | May 7, 09:00 UTC | 2h 50m |
| 2026-05-06 | VTM680 | - | May 6, 19:15 UTC | May 7, 04:55 UTC | 9h 40m |
| 2026-05-06 | VTM680 | - | May 6, 16:30 UTC | May 6, 17:25 UTC | 55m |
| 2026-05-05 | VTM680 | - | May 5, 08:40 UTC | May 5, 11:50 UTC | 3h 10m |
| 2026-05-05 | VTM680 | - | May 5, 07:10 UTC | May 5, 08:05 UTC | 55m |
| 2026-05-05 | VTM680 | - | May 5, 01:25 UTC | May 5, 01:35 UTC | 10m |
| 2026-04-30 | VTM680 | - | Apr 30, 21:00 UTC | Apr 30, 22:05 UTC | 1h 5m |
| 2026-04-30 | VTM680 | - | Apr 30, 17:40 UTC | Apr 30, 19:45 UTC | 2h 5m |
| 2026-04-30 | VTM680 | - | Apr 30, 10:00 UTC | Apr 30, 14:20 UTC | 4h 20m |
| 2026-04-29 | VTM680 | - | Apr 29, 15:45 UTC | Apr 29, 19:05 UTC | 3h 20m |
| 2026-04-29 | VTM680 | - | Apr 29, 03:34 UTC | Apr 29, 14:35 UTC | 11h 1m |
| 2026-04-28 | VTM680 | - | Apr 28, 22:25 UTC | Apr 29, 02:35 UTC | 4h 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.
Prefer a tail-number view? See the XA-VFQ page for operator, model, and routing details .