Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0F03

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-GGB · BOEING 737-400

Hex
0D0F03
Octal
03207403
Decimal
855,811
Country
MX
Tail
XA-GGB
Type
B734
No current signal · last broadcast 11h ago
Flights observed
99
Distinct callsigns
13
Country
MX
Last broadcast
11h ago

Last known position

Most recent position reported by Mode-S 0D0F03.

Country allocation

The ICAO 24-bit address 0D0F03 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 13 distinct

Callsign Airline Flights Last seen
ESF522 - 26 2026-07-10
ESF322 - 15 2026-07-17
ESF337 - 12 2026-07-07
ESF521 - 10 2026-07-14
ESF321 - 9 2026-07-17
ESF338 - 7 2026-07-03
ESF302 Estafeta Carga Aerea 4 2026-05-18
ESF501 Estafeta Carga Aerea 3 2026-07-10
ESF500 - 3 2026-07-14
ESF313 Estafeta Carga Aerea 3 2026-05-20
ESF301 - 3 2026-05-17
ESF314 - 2 2026-05-15
ESF200 Estafeta Carga Aerea 1 2026-07-01

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 ESF322 - Jul 17, 14:50 UTCJul 17, 15:05 UTC15m
2026-07-17 ESF321 - Jul 17, 03:14 UTCJul 17, 03:34 UTC20m
2026-07-16 ESF322 - Jul 16, 14:50 UTCJul 16, 15:05 UTC15m
2026-07-16 ESF321 - Jul 16, 03:10 UTCJul 16, 03:25 UTC15m
2026-07-15 ESF322 - Jul 15, 14:50 UTCJul 15, 15:05 UTC15m
2026-07-15 ESF321 - Jul 15, 03:05 UTCJul 15, 03:20 UTC15m
2026-07-14 ESF521 - Jul 14, 07:00 UTCJul 14, 14:55 UTC7h 55m
2026-07-14 ESF500 - Jul 14, 04:30 UTCJul 14, 05:05 UTC35m
2026-07-10 ESF501 MTY → SLP Jul 10, 13:05 UTCJul 10, 13:20 UTC15m
2026-07-10 ESF522 - Jul 10, 11:10 UTCJul 10, 11:35 UTC25m
2026-07-10 ESF321 - Jul 10, 04:00 UTCJul 10, 04:20 UTC20m
2026-07-09 ESF322 - Jul 9, 14:20 UTCJul 9, 14:35 UTC15m
2026-07-09 ESF321 - Jul 9, 03:15 UTCJul 9, 03:35 UTC20m
2026-07-08 ESF322 CUL → HMO Jul 8, 14:50 UTCJul 8, 15:05 UTC15m
2026-07-08 ESF321 - Jul 8, 03:10 UTCJul 8, 03:35 UTC25m
2026-07-07 ESF322 CUL → HMO Jul 7, 14:30 UTCJul 7, 14:45 UTC15m
2026-07-07 ESF337 - Jul 7, 07:15 UTCJul 7, 07:40 UTC25m
2026-07-07 ESF337 - Jul 7, 05:30 UTCJul 7, 06:30 UTC1h 0m
2026-07-03 ESF338 - Jul 3, 12:20 UTCJul 3, 12:40 UTC20m
2026-07-03 ESF521 MTY → PBC Jul 3, 06:30 UTCJul 3, 11:25 UTC4h 55m
2026-07-02 ESF522 - Jul 2, 06:35 UTCJul 2, 11:55 UTC5h 20m
2026-07-01 ESF200 SLW → MTY Jul 1, 23:40 UTCJul 2, 00:10 UTC30m
2026-06-30 ESF521 - Jun 30, 07:10 UTCJun 30, 07:25 UTC15m
2026-06-30 ESF500 - Jun 30, 04:45 UTCJun 30, 05:15 UTC30m
2026-06-26 ESF501 MTY → SLP Jun 26, 12:39 UTCJun 26, 12:59 UTC20m
2026-06-26 ESF522 PBC → MTY Jun 26, 06:50 UTCJun 26, 11:40 UTC4h 50m
2026-06-25 ESF337 - Jun 25, 11:54 UTCJun 26, 05:55 UTC18h 0m
2026-06-25 ESF337 PBC → PBC Jun 25, 06:44 UTCJun 25, 11:15 UTC4h 30m
2026-06-24 ESF337 PBC → PBC Jun 24, 12:14 UTCJun 25, 05:55 UTC17h 40m
2026-06-24 ESF338 HMO → PBC Jun 24, 03:00 UTCJun 24, 11:29 UTC8h 30m
2026-06-23 ESF322 CUL → HMO Jun 23, 14:29 UTCJun 23, 14:44 UTC15m
2026-06-23 ESF337 - Jun 23, 06:55 UTCJun 23, 07:15 UTC20m
2026-06-23 ESF337 - Jun 23, 05:04 UTCJun 23, 06:09 UTC1h 5m
2026-06-19 ESF338 SLP → PBC Jun 19, 11:59 UTCJun 19, 12:59 UTC1h 0m
2026-06-19 ESF338 SLP → PBC Jun 19, 02:59 UTCJun 19, 11:20 UTC8h 20m
2026-06-18 ESF322 CUL → HMO Jun 18, 14:30 UTCJun 18, 14:45 UTC15m
2026-06-18 ESF321 - Jun 18, 03:20 UTCJun 18, 03:35 UTC15m
2026-06-17 ESF322 CUL → HMO Jun 17, 14:35 UTCJun 17, 14:50 UTC15m
2026-06-17 ESF321 - Jun 17, 03:00 UTCJun 17, 03:20 UTC20m
2026-06-16 ESF322 CUL → HMO Jun 16, 14:35 UTCJun 16, 14:55 UTC20m
2026-06-16 ESF321 - Jun 16, 03:15 UTCJun 16, 03:30 UTC15m
2026-06-12 ESF322 CUL → HMO Jun 12, 14:30 UTCJun 12, 14:45 UTC15m
2026-06-12 ESF521 MTY → SLP Jun 12, 06:40 UTCJun 12, 06:55 UTC15m
2026-06-11 ESF522 MTY → MTY Jun 11, 06:35 UTCJun 11, 11:35 UTC5h 0m
2026-06-10 ESF522 - Jun 10, 07:15 UTCJun 10, 11:50 UTC4h 35m
2026-06-09 ESF522 - Jun 9, 07:05 UTCJun 9, 11:40 UTC4h 35m
2026-06-09 ESF500 - Jun 9, 04:50 UTCJun 9, 05:15 UTC25m
2026-06-05 ESF501 MTY → SLP Jun 5, 13:15 UTCJun 5, 13:30 UTC15m
2026-06-05 ESF522 MTY → MTY Jun 5, 07:00 UTCJun 5, 11:55 UTC4h 55m
2026-06-04 ESF522 - Jun 4, 07:05 UTCJun 4, 11:50 UTC4h 45m

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-GGB page for operator, model, and routing details .

Mode-S 0D0F03 frequently asked

What is Mode-S code 0D0F03?
0D0F03 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-GGB.
Where is Mode-S 0D0F03 registered?
Mode-S code 0D0F03 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0F03 broadcasting right now?
No active broadcast right now. Last signal was 11h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0F03, octal 03207403, decimal 855,811.
What flights does 0D0F03 operate?
Mode-S 0D0F03 has broadcast 13 distinct callsigns, including ESF522, ESF322, ESF337, ESF521, ESF321.