sensors Mode-S transponder

0D0EF2

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-RFD · CESSNA 208 Caravan

Hex
0D0EF2
Octal
03207362
Decimal
855,794
Country
MX
Tail
XA-RFD
Type
C208
No current signal · last broadcast 14d ago
Flights observed
222
Distinct callsigns
20
Country
MX
Last broadcast
14d ago

Last known position

Most recent position reported by Mode-S 0D0EF2.

Country allocation

The ICAO 24-bit address 0D0EF2 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 20 distinct

Callsign Airline Flights Last seen
XARFD - 69 2026-07-13
RFD281 Aerotransportes Rafilher 13 2026-05-23
RFD301 - 11 2026-07-09
RFD300 - 11 2026-07-09
RFD280 Aerotransportes Rafilher 10 2026-05-24
RFD20 - 7 2026-06-19
RFD19 - 7 2026-06-19
RFD11 - 7 2026-06-16
RFD141 - 6 2026-06-20
RFD111 - 6 2026-06-18
RFD106 - 6 2026-06-17
RFD251 Aerotransportes Rafilher 5 2026-06-19
RFD250 Aerotransportes Rafilher 5 2026-06-19
RFD12 - 5 2026-06-16
RFD105 Aerotransportes Rafilher 5 2026-06-17
RFD104 Aerotransportes Rafilher 5 2026-06-17
RFD140 - 4 2026-07-11
RFD - 4 2026-05-29
RFD201 Aerotransportes Rafilher 3 2026-05-22
RFD200 Aerotransportes Rafilher 3 2026-05-09

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 XARFD - Jul 13, 19:40 UTCJul 13, 20:45 UTC1h 5m
2026-07-13 XARFD - Jul 13, 17:45 UTCJul 13, 18:50 UTC1h 5m
2026-07-13 XARFD - Jul 13, 15:35 UTCJul 13, 16:45 UTC1h 10m
2026-07-13 XARFD - Jul 13, 14:00 UTCJul 13, 15:00 UTC1h 0m
2026-07-12 XARFD - Jul 12, 23:20 UTCJul 13, 00:30 UTC1h 10m
2026-07-12 XARFD - Jul 12, 21:40 UTCJul 12, 22:35 UTC55m
2026-07-12 XARFD - Jul 12, 19:40 UTCJul 12, 20:45 UTC1h 5m
2026-07-12 XARFD - Jul 12, 17:50 UTCJul 12, 18:50 UTC1h 0m
2026-07-11 RFD252 - Jul 11, 20:30 UTCJul 11, 20:55 UTC25m
2026-07-11 RFD253 - Jul 11, 16:50 UTCJul 11, 17:10 UTC20m
2026-07-11 RFD140 - Jul 11, 15:00 UTCJul 11, 16:05 UTC1h 5m
2026-07-09 RFD300 - Jul 9, 20:45 UTCJul 9, 21:25 UTC40m
2026-07-09 RFD301 - Jul 9, 17:10 UTCJul 9, 17:55 UTC45m
2026-07-07 RFD300 - Jul 7, 20:50 UTCJul 7, 21:35 UTC45m
2026-07-07 RFD301 - Jul 7, 17:25 UTCJul 7, 18:10 UTC45m
2026-07-04 RFD300 - Jul 4, 20:55 UTCJul 4, 21:45 UTC50m
2026-07-04 RFD301 - Jul 4, 17:25 UTCJul 4, 18:15 UTC50m
2026-07-02 RFD300 - Jul 2, 20:45 UTCJul 2, 21:30 UTC45m
2026-07-02 RFD301 - Jul 2, 17:15 UTCJul 2, 18:00 UTC45m
2026-06-27 RFD300 - Jun 27, 16:39 UTCJun 27, 17:20 UTC40m
2026-06-27 RFD301 - Jun 27, 13:09 UTCJun 27, 14:00 UTC50m
2026-06-25 RFD300 - Jun 25, 16:50 UTCJun 25, 17:34 UTC45m
2026-06-25 RFD301 - Jun 25, 13:24 UTCJun 25, 14:04 UTC40m
2026-06-23 RFD300 - Jun 23, 17:04 UTCJun 23, 17:39 UTC35m
2026-06-23 RFD301 - Jun 23, 13:34 UTCJun 23, 14:19 UTC45m
2026-06-20 RFD141 - Jun 20, 12:04 UTCJun 20, 12:59 UTC55m
2026-06-20 RFD142 TAM → MTY Jun 20, 01:09 UTCJun 20, 02:14 UTC1h 5m
2026-06-19 RFD145 MTY → TAM Jun 19, 21:59 UTCJun 19, 23:09 UTC1h 10m
2026-06-19 RFD19 - Jun 19, 20:04 UTCJun 19, 21:14 UTC1h 10m
2026-06-19 RFD20 - Jun 19, 18:20 UTCJun 19, 19:04 UTC45m
2026-06-19 RFD250 AGU → MTY Jun 19, 16:49 UTCJun 19, 17:14 UTC25m
2026-06-19 RFD251 MTY → AGU Jun 19, 13:04 UTCJun 19, 13:24 UTC20m
2026-06-18 XARFD - Jun 18, 23:50 UTCJun 19, 00:49 UTC59m
2026-06-18 XARFD - Jun 18, 22:00 UTCJun 18, 23:05 UTC1h 5m
2026-06-18 XARFD - Jun 18, 19:45 UTCJun 18, 20:50 UTC1h 5m
2026-06-18 XARFD - Jun 18, 17:45 UTCJun 18, 18:50 UTC1h 5m
2026-06-18 RFD250 AGU → MTY Jun 18, 16:00 UTCJun 18, 16:25 UTC25m
2026-06-18 RFD251 MTY → AGU Jun 18, 12:10 UTCJun 18, 12:35 UTC25m
2026-06-18 RFD111 - Jun 18, 00:35 UTCJun 18, 01:05 UTC30m
2026-06-17 RFD106 - Jun 17, 21:20 UTCJun 17, 21:55 UTC35m
2026-06-17 RFD105 SLP → MTY Jun 17, 20:15 UTCJun 17, 20:40 UTC25m
2026-06-17 RFD104 MTY → SLP Jun 17, 17:20 UTCJun 17, 17:45 UTC25m
2026-06-17 RFD250 AGU → MTY Jun 17, 16:10 UTCJun 17, 16:35 UTC25m
2026-06-17 RFD251 MTY → AGU Jun 17, 12:25 UTCJun 17, 12:45 UTC20m
2026-06-16 XARFD - Jun 16, 23:50 UTCJun 17, 00:50 UTC1h 0m
2026-06-16 XARFD - Jun 16, 22:05 UTCJun 16, 23:05 UTC1h 0m
2026-06-16 XARFD - Jun 16, 19:55 UTCJun 16, 21:00 UTC1h 5m
2026-06-16 XARFD - Jun 16, 17:59 UTCJun 16, 19:10 UTC1h 10m
2026-06-16 XARFD - Jun 16, 15:55 UTCJun 16, 16:55 UTC1h 0m
2026-06-16 XARFD - Jun 16, 14:05 UTCJun 16, 15:09 UTC1h 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-RFD page for operator, model, and routing details .

Mode-S 0D0EF2 frequently asked

What is Mode-S code 0D0EF2?
0D0EF2 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-RFD.
Where is Mode-S 0D0EF2 registered?
Mode-S code 0D0EF2 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0EF2 broadcasting right now?
No active broadcast right now. Last signal was 14d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0EF2, octal 03207362, decimal 855,794.
What flights does 0D0EF2 operate?
Mode-S 0D0EF2 has broadcast 20 distinct callsigns, including XARFD, RFD281, RFD301, RFD300, RFD280.