sensors Mode-S transponder
ABFE45
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N872FD · BOEING 777-200LR · operated by FEDERAL EXPRESS CORP
- Hex
- ABFE45
- Octal
- 52777105
- Decimal
- 11,271,749
- Country
- US
- Tail
- N872FD
- Type
- B77L
- Flights observed
- 146
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 5h ago
Current position
Country allocation
The ICAO 24-bit address ABFE45 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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 |
|---|---|---|---|
| FDX6030 | FedEx Express | 8 | 2026-06-11 |
| FDX9004 | FedEx Express | 5 | 2026-06-07 |
| FDX6014 | FedEx Express | 5 | 2026-06-02 |
| FDX5030 | FedEx Express | 5 | 2026-06-04 |
| FDX85 | FedEx Express | 4 | 2026-06-05 |
| FDX7 | FedEx Express | 4 | 2026-05-28 |
| FDX5236 | FedEx Express | 4 | 2026-06-03 |
| FDX5230 | FedEx Express | 4 | 2026-05-13 |
| FDX5161 | FedEx Express | 4 | 2026-04-30 |
| FDX23 | FedEx Express | 4 | 2026-05-24 |
| FDX9007 | FedEx Express | 3 | 2026-06-09 |
| FDX9005 | FedEx Express | 3 | 2026-06-08 |
| FDX6092 | FedEx Express | 3 | 2026-05-06 |
| FDX6018 | FedEx Express | 3 | 2026-05-26 |
| FDX60 | - | 3 | 2026-06-16 |
| FDX5313 | FedEx Express | 3 | 2026-04-23 |
| FDX19 | FedEx Express | 3 | 2026-05-02 |
| FDX9127 | FedEx Express | 2 | 2026-05-25 |
| FDX87 | FedEx Express | 2 | 2026-04-26 |
| FDX77 | FedEx Express | 2 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | FDX295 | - | Jun 17, 08:50 UTC | Jun 17, 09:15 UTC | 25m |
| 2026-06-17 | FDX295 | - | Jun 17, 06:15 UTC | Jun 17, 07:25 UTC | 1h 10m |
| 2026-06-16 | FDX60 | KIX → NRT | Jun 16, 16:25 UTC | Jun 16, 22:45 UTC | 6h 21m |
| 2026-06-16 | FDX5119 | MEM → ANC | Jun 16, 08:44 UTC | Jun 16, 14:25 UTC | 5h 40m |
| 2026-06-15 | FDX5155 | MEM → KIX | Jun 15, 07:15 UTC | Jun 15, 21:16 UTC | 14h 1m |
| 2026-06-15 | FDX5155 | - | Jun 15, 07:20 UTC | Jun 15, 21:25 UTC | 14h 5m |
| 2026-06-14 | FDX5045 | OAK → MEM | Jun 14, 11:55 UTC | Jun 14, 15:10 UTC | 3h 15m |
| 2026-06-13 | FDX5183 | - | Jun 13, 06:25 UTC | Jun 13, 17:15 UTC | 10h 50m |
| 2026-06-11 | FDX5184 | - | Jun 11, 23:00 UTC | Jun 12, 09:00 UTC | 10h 0m |
| 2026-06-11 | FDX60 | ANC → MEM | Jun 11, 11:25 UTC | Jun 11, 15:15 UTC | 3h 50m |
| 2026-06-11 | FDX6030 | ANC → EWR | Jun 11, 02:20 UTC | Jun 11, 08:25 UTC | 6h 5m |
| 2026-06-10 | FDX60 | ANC → MEM | Jun 10, 16:20 UTC | Jun 10, 22:30 UTC | 6h 10m |
| 2026-06-10 | FDX5388 | MEM → ANC | Jun 10, 05:00 UTC | Jun 10, 13:05 UTC | 8h 5m |
| 2026-06-09 | FDX9009 | ANC → NRT | Jun 9, 21:30 UTC | Jun 10, 03:10 UTC | 5h 40m |
| 2026-06-09 | FDX9007 | LGG → IND | Jun 9, 13:15 UTC | Jun 9, 19:00 UTC | 5h 45m |
| 2026-06-08 | FDX9007 | LGG → IND | Jun 8, 18:05 UTC | Jun 9, 11:50 UTC | 17h 45m |
| 2026-06-08 | FDX9007 | LGG → IND | Jun 8, 13:20 UTC | Jun 9, 11:50 UTC | 22h 30m |
| 2026-06-08 | FDX9005 | LAX → SJC | Jun 8, 11:35 UTC | Jun 9, 11:15 UTC | 23h 40m |
| 2026-06-07 | FDX9005 | LAX → SJC | Jun 7, 21:20 UTC | Jun 8, 03:20 UTC | 6h 0m |
| 2026-06-07 | FDX9005 | LAX → SJC | Jun 7, 21:17 UTC | Jun 8, 03:15 UTC | 5h 58m |
| 2026-06-07 | FDX9004 | MEM → MDT | Jun 7, 16:45 UTC | Jun 7, 17:40 UTC | 55m |
| 2026-06-07 | FDX9004 | MEM → MDT | Jun 7, 10:40 UTC | Jun 7, 16:28 UTC | 5h 48m |
| 2026-06-07 | FDX9004 | MEM → MDT | Jun 7, 10:40 UTC | Jun 7, 17:40 UTC | 7h 0m |
| 2026-06-06 | FDX9004 | MEM → MDT | Jun 6, 20:35 UTC | Jun 7, 08:55 UTC | 12h 20m |
| 2026-06-06 | FDX9004 | MEM → MDT | Jun 6, 10:45 UTC | Jun 6, 14:50 UTC | 4h 5m |
| 2026-06-05 | FDX85 | OAK → ANC | Jun 5, 19:25 UTC | Jun 6, 02:15 UTC | 6h 50m |
| 2026-06-05 | FDX85 | OAK → ANC | Jun 5, 19:23 UTC | Jun 6, 02:18 UTC | 6h 55m |
| 2026-06-05 | FDX85 | OAK → ANC | Jun 5, 08:20 UTC | Jun 5, 14:45 UTC | 6h 25m |
| 2026-06-05 | FDX85 | OAK → ANC | Jun 5, 08:17 UTC | Jun 5, 14:41 UTC | 6h 24m |
| 2026-06-04 | FDX5270 | CDG → MEM | Jun 4, 19:02 UTC | Jun 5, 04:08 UTC | 9h 6m |
| 2026-06-04 | FDX5270 | CDG → MEM | Jun 4, 19:05 UTC | Jun 5, 04:25 UTC | 9h 20m |
| 2026-06-04 | FDX5030 | CAN → CDG | Jun 4, 11:20 UTC | Jun 4, 14:30 UTC | 3h 10m |
| 2026-06-04 | FDX5030 | CAN → CDG | Jun 4, 08:45 UTC | Jun 4, 09:10 UTC | 25m |
| 2026-06-04 | FDX5030 | CAN → CDG | Jun 4, 07:05 UTC | Jun 4, 08:10 UTC | 1h 5m |
| 2026-06-03 | FDX6015 | - | Jun 3, 16:20 UTC | Jun 3, 16:45 UTC | 25m |
| 2026-06-03 | FDX5236 | ANC → ICN | Jun 3, 05:20 UTC | Jun 3, 13:35 UTC | 8h 15m |
| 2026-06-02 | FDX5236 | ANC → ICN | Jun 2, 20:00 UTC | Jun 3, 01:45 UTC | 5h 45m |
| 2026-06-02 | FDX6014 | ANC → IND | Jun 2, 10:45 UTC | Jun 2, 16:30 UTC | 5h 45m |
| 2026-06-01 | FDX6014 | ANC → IND | Jun 1, 15:40 UTC | Jun 2, 08:00 UTC | 16h 20m |
| 2026-05-31 | FDX6028 | - | May 31, 09:45 UTC | May 31, 22:10 UTC | 12h 25m |
| 2026-05-30 | FDX5460 | CDG → CAN | May 30, 22:45 UTC | May 31, 01:11 UTC | 2h 26m |
| 2026-05-30 | FDX9160 | CDG → MEM | May 30, 11:50 UTC | May 30, 20:00 UTC | 8h 10m |
| 2026-05-29 | FDX9159 | CDG → MEM | May 29, 21:25 UTC | May 30, 06:05 UTC | 8h 40m |
| 2026-05-29 | FDX10 | MEM → CDG | May 29, 09:10 UTC | May 29, 17:15 UTC | 8h 5m |
| 2026-05-28 | FDX7 | MXP → MEM | May 28, 19:00 UTC | May 29, 04:37 UTC | 9h 37m |
| 2026-05-28 | FDX7 | MXP → MEM | May 28, 19:00 UTC | May 29, 04:35 UTC | 9h 35m |
| 2026-05-28 | FDX7 | MXP → MEM | May 28, 19:00 UTC | May 28, 19:15 UTC | 15m |
| 2026-05-28 | FDX7 | MXP → MEM | May 28, 06:55 UTC | May 28, 16:35 UTC | 9h 40m |
| 2026-05-27 | FDX8 | MEM → DXB | May 27, 19:00 UTC | May 28, 04:10 UTC | 9h 10m |
| 2026-05-27 | FDX5030 | CAN → CDG | May 27, 13:05 UTC | May 27, 16:10 UTC | 3h 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 N872FD page for operator, model, and routing details .