sensors Mode-S transponder
A1F4C5
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N225NE · BOEING 767-300 · operated by 2/25/94 LLC
- Hex
- A1F4C5
- Octal
- 50372305
- Decimal
- 10,613,957
- Country
- US
- Tail
- N225NE
- Type
- B763
- Flights observed
- 41
- Distinct callsigns
- 10
- Country
- US
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address A1F4C5 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 10 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OAE2073 | Omni Air International | 10 | 2026-04-16 |
| CMB534 | - | 9 | 2026-05-11 |
| OAE568 | Omni Air International | 5 | 2026-04-21 |
| OAE2059 | Omni Air International | 5 | 2026-04-28 |
| CMB568 | - | 4 | 2026-04-20 |
| OAE556 | Omni Air International | 3 | 2026-05-22 |
| CMB556 | - | 2 | 2026-05-21 |
| OAE323 | Omni Air International | 1 | 2026-04-30 |
| OAE2187 | Omni Air International | 1 | 2026-05-01 |
| 568 | - | 1 | 2026-04-18 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-22 | OAE556 | NZY → SNN | May 22, 18:05 UTC | May 22, 18:40 UTC | 35m |
| 2026-05-22 | OAE556 | NZY → SNN | May 22, 11:15 UTC | May 22, 15:20 UTC | 4h 5m |
| 2026-05-22 | OAE556 | NZY → SNN | May 22, 00:45 UTC | May 22, 06:25 UTC | 5h 40m |
| 2026-05-21 | CMB556 | - | May 21, 20:15 UTC | May 21, 22:15 UTC | 2h 0m |
| 2026-05-21 | CMB556 | - | May 21, 06:20 UTC | May 21, 15:30 UTC | 9h 10m |
| 2026-05-11 | CMB534 | - | May 11, 16:35 UTC | May 11, 17:00 UTC | 26m |
| 2026-05-11 | CMB534 | - | May 11, 09:20 UTC | May 11, 12:45 UTC | 3h 25m |
| 2026-05-10 | CMB534 | - | May 10, 22:05 UTC | May 11, 06:20 UTC | 8h 15m |
| 2026-05-10 | CMB534 | POZ → RMS | May 10, 16:14 UTC | May 10, 17:25 UTC | 1h 10m |
| 2026-05-09 | CMB534 | - | May 9, 18:05 UTC | May 9, 19:14 UTC | 1h 10m |
| 2026-05-09 | CMB534 | - | May 9, 07:10 UTC | May 9, 14:45 UTC | 7h 35m |
| 2026-05-09 | CMB534 | - | May 9, 00:15 UTC | May 9, 03:20 UTC | 3h 5m |
| 2026-05-08 | CMB534 | - | May 8, 19:30 UTC | May 8, 20:45 UTC | 1h 15m |
| 2026-05-08 | CMB534 | - | May 8, 12:25 UTC | May 8, 15:45 UTC | 3h 20m |
| 2026-05-01 | OAE2187 | SEA → BFI | May 1, 22:10 UTC | May 1, 22:30 UTC | 20m |
| 2026-04-30 | OAE323 | AFW → SEA | Apr 30, 15:40 UTC | Apr 30, 16:20 UTC | 40m |
| 2026-04-28 | OAE2059 | AFW → SAL | Apr 28, 17:50 UTC | Apr 28, 20:05 UTC | 2h 15m |
| 2026-04-28 | OAE2059 | AFW → SAL | Apr 28, 13:35 UTC | Apr 28, 15:35 UTC | 2h 0m |
| 2026-04-28 | OAE2059 | AFW → SAL | Apr 28, 07:25 UTC | Apr 28, 10:10 UTC | 2h 45m |
| 2026-04-28 | OAE2059 | AFW → SAL | Apr 28, 06:40 UTC | Apr 28, 06:55 UTC | 15m |
| 2026-04-27 | OAE2059 | AFW → SAL | Apr 27, 23:15 UTC | Apr 28, 02:00 UTC | 2h 45m |
| 2026-04-21 | OAE568 | GRK → AFW | Apr 21, 08:50 UTC | Apr 21, 11:35 UTC | 2h 45m |
| 2026-04-21 | OAE568 | GRK → AFW | Apr 21, 04:40 UTC | Apr 21, 06:10 UTC | 1h 30m |
| 2026-04-20 | OAE568 | GRK → AFW | Apr 20, 20:30 UTC | Apr 21, 02:10 UTC | 5h 40m |
| 2026-04-20 | CMB568 | - | Apr 20, 13:00 UTC | Apr 20, 15:55 UTC | 2h 55m |
| 2026-04-20 | CMB568 | - | Apr 20, 06:50 UTC | Apr 20, 08:55 UTC | 2h 5m |
| 2026-04-19 | CMB568 | HAM → POZ | Apr 19, 14:40 UTC | Apr 19, 15:30 UTC | 50m |
| 2026-04-19 | CMB568 | - | Apr 19, 10:35 UTC | Apr 19, 12:20 UTC | 1h 45m |
| 2026-04-18 | OAE568 | GRK → AFW | Apr 18, 23:35 UTC | Apr 19, 06:50 UTC | 7h 15m |
| 2026-04-18 | OAE568 | GRK → AFW | Apr 18, 19:20 UTC | Apr 18, 20:40 UTC | 1h 20m |
| 2026-04-18 | 568 | - | Apr 18, 14:00 UTC | Apr 18, 15:20 UTC | 1h 20m |
| 2026-04-16 | OAE2073 | AFW → LGB | Apr 16, 13:15 UTC | Apr 16, 13:54 UTC | 40m |
| 2026-04-16 | OAE2073 | AFW → LGB | Apr 16, 11:09 UTC | Apr 16, 13:05 UTC | 1h 55m |
| 2026-04-16 | OAE2073 | AFW → LGB | Apr 16, 10:49 UTC | Apr 16, 11:04 UTC | 15m |
| 2026-04-16 | OAE2073 | AFW → LGB | Apr 16, 07:24 UTC | Apr 16, 07:39 UTC | 15m |
| 2026-04-16 | OAE2073 | AFW → LGB | Apr 16, 05:29 UTC | Apr 16, 06:55 UTC | 1h 25m |
| 2026-04-16 | OAE2073 | AFW → LGB | Apr 16, 04:24 UTC | Apr 16, 04:49 UTC | 25m |
| 2026-04-16 | OAE2073 | AFW → LGB | Apr 16, 01:10 UTC | Apr 16, 01:35 UTC | 25m |
| 2026-04-16 | OAE2073 | AFW → LGB | Apr 16, 00:00 UTC | Apr 16, 01:05 UTC | 1h 5m |
| 2026-04-15 | OAE2073 | AFW → LGB | Apr 15, 19:05 UTC | Apr 15, 20:30 UTC | 1h 25m |
| 2026-04-15 | OAE2073 | AFW → LGB | Apr 15, 17:45 UTC | Apr 15, 19:00 UTC | 1h 15m |
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 N225NE page for operator, model, and routing details .