sensors Mode-S transponder
0180A1
ICAO 24-bit transponder address · allocated to Libya
Currently assigned to 5A-BRC · AIRBUS A-320
- Hex
- 0180A1
- Octal
- 00300241
- Decimal
- 98,465
- Country
- LY
- Tail
- 5A-BRC
- Type
- A320
- Flights observed
- 73
- Distinct callsigns
- 20
- Country
- LY
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 0180A1 falls within the block assigned to Libya (LY) by ICAO Annex 10, Volume III. Every aircraft registered in Libya 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 |
|---|---|---|---|
| BNL302 | Blue Nile Ethiopia Trading | 17 | 2026-05-25 |
| BNL301 | Blue Nile Ethiopia Trading | 10 | 2026-05-25 |
| BNL235 | - | 10 | 2026-05-26 |
| BNL236 | - | 9 | 2026-05-25 |
| BNL104 | Blue Nile Ethiopia Trading | 3 | 2026-05-23 |
| BNL103 | Blue Nile Ethiopia Trading | 3 | 2026-05-23 |
| BNL464 | Blue Nile Ethiopia Trading | 2 | 2026-05-29 |
| BNL463 | Blue Nile Ethiopia Trading | 2 | 2026-05-29 |
| BNL462 | Blue Nile Ethiopia Trading | 2 | 2026-05-16 |
| BNL233 | - | 2 | 2026-05-29 |
| BNL231 | - | 2 | 2026-05-13 |
| BNL102 | Blue Nile Ethiopia Trading | 2 | 2026-04-14 |
| BNL332 | Blue Nile Ethiopia Trading | 1 | 2026-04-21 |
| BNL331 | Blue Nile Ethiopia Trading | 1 | 2026-04-21 |
| BNL304 | Blue Nile Ethiopia Trading | 1 | 2026-04-26 |
| BNL234 | Blue Nile Ethiopia Trading | 1 | 2026-05-16 |
| BNL232 | - | 1 | 2026-05-13 |
| BNL122 | Blue Nile Ethiopia Trading | 1 | 2026-04-14 |
| BNL121 | Blue Nile Ethiopia Trading | 1 | 2026-04-14 |
| BNL101 | Blue Nile Ethiopia Trading | 1 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | BNL464 | CAI → MJI | May 29, 19:45 UTC | May 29, 21:55 UTC | 2h 10m |
| 2026-05-29 | BNL463 | MJI → CAI | May 29, 16:30 UTC | May 29, 16:45 UTC | 15m |
| 2026-05-29 | BNL233 | - | May 29, 12:10 UTC | May 29, 12:20 UTC | 10m |
| 2026-05-26 | BNL235 | - | May 26, 17:25 UTC | May 26, 19:50 UTC | 2h 25m |
| 2026-05-25 | BNL236 | - | May 25, 19:54 UTC | May 25, 20:30 UTC | 35m |
| 2026-05-25 | BNL302 | IST → BEN | May 25, 11:45 UTC | May 25, 18:00 UTC | 6h 15m |
| 2026-05-25 | BNL301 | BEN → IST | May 25, 08:10 UTC | May 25, 09:55 UTC | 1h 45m |
| 2026-05-23 | BNL104 | TUN → BEN | May 23, 22:25 UTC | May 23, 23:20 UTC | 55m |
| 2026-05-23 | BNL103 | BEN → TUN | May 23, 08:00 UTC | May 23, 20:20 UTC | 12h 21m |
| 2026-05-22 | BNL463 | MJI → CAI | May 22, 16:10 UTC | May 22, 22:10 UTC | 6h 0m |
| 2026-05-21 | BNL236 | - | May 21, 19:55 UTC | May 22, 12:20 UTC | 16h 25m |
| 2026-05-21 | BML235 | - | May 21, 12:10 UTC | May 21, 18:15 UTC | 6h 5m |
| 2026-05-16 | BNL234 | MJI → BEN | May 16, 17:25 UTC | May 16, 17:40 UTC | 15m |
| 2026-05-16 | BNL462 | CAI → MJI | May 16, 11:55 UTC | May 16, 14:16 UTC | 2h 20m |
| 2026-05-15 | BNL464 | CAI → MJI | May 15, 17:40 UTC | May 15, 22:25 UTC | 4h 45m |
| 2026-05-13 | BNL232 | - | May 13, 17:20 UTC | May 13, 17:50 UTC | 30m |
| 2026-05-13 | BNL462 | CAI → MJI | May 13, 08:45 UTC | May 13, 15:00 UTC | 6h 15m |
| 2026-05-13 | BNL231 | - | May 13, 05:55 UTC | May 13, 06:35 UTC | 40m |
| 2026-05-09 | BNL302 | IST → BEN | May 9, 19:00 UTC | May 9, 20:30 UTC | 1h 30m |
| 2026-05-09 | BNL301 | BEN → IST | May 9, 07:40 UTC | May 9, 09:35 UTC | 1h 55m |
| 2026-05-07 | BNL236 | - | May 7, 20:15 UTC | May 7, 20:35 UTC | 20m |
| 2026-05-07 | BNL235 | - | May 7, 17:55 UTC | May 7, 18:10 UTC | 15m |
| 2026-05-06 | BNL302 | IST → BEN | May 6, 07:40 UTC | May 6, 13:15 UTC | 5h 35m |
| 2026-05-04 | BNL236 | - | May 4, 19:55 UTC | May 4, 20:10 UTC | 15m |
| 2026-05-04 | BNL302 | IST → BEN | May 4, 12:00 UTC | May 4, 17:45 UTC | 5h 45m |
| 2026-05-03 | BNL301 | BEN → IST | May 3, 20:05 UTC | May 4, 09:10 UTC | 13h 5m |
| 2026-05-02 | BNL302 | IST → BEN | May 2, 12:20 UTC | May 3, 08:05 UTC | 19h 44m |
| 2026-05-02 | BNL302 | IST → BEN | May 2, 11:25 UTC | May 3, 08:05 UTC | 20h 39m |
| 2026-05-01 | BNL301 | BEN → IST | May 1, 17:30 UTC | May 2, 08:40 UTC | 15h 10m |
| 2026-05-01 | BNL302 | IST → BEN | May 1, 12:20 UTC | May 2, 08:40 UTC | 20h 20m |
| 2026-05-01 | BNL302 | IST → BEN | May 1, 11:55 UTC | May 2, 08:40 UTC | 20h 45m |
| 2026-05-01 | BNL302 | IST → BEN | May 1, 08:20 UTC | May 2, 08:15 UTC | 23h 55m |
| 2026-05-01 | BNL302 | IST → BEN | May 1, 07:45 UTC | May 1, 19:55 UTC | 12h 10m |
| 2026-04-30 | BNL302 | IST → BEN | Apr 30, 14:25 UTC | May 1, 13:25 UTC | 23h 0m |
| 2026-04-29 | BNL233 | - | Apr 29, 20:15 UTC | Apr 30, 12:15 UTC | 15h 59m |
| 2026-04-29 | BNL302 | IST → BEN | Apr 29, 11:35 UTC | Apr 29, 18:10 UTC | 6h 35m |
| 2026-04-28 | BNL301 | BEN → IST | Apr 28, 19:50 UTC | Apr 29, 08:45 UTC | 12h 55m |
| 2026-04-28 | BNL235 | - | Apr 28, 08:40 UTC | Apr 28, 18:05 UTC | 9h 25m |
| 2026-04-27 | BNL231 | - | Apr 27, 20:00 UTC | Apr 28, 06:35 UTC | 10h 35m |
| 2026-04-27 | BNL235 | - | Apr 27, 17:30 UTC | Apr 27, 18:20 UTC | 50m |
| 2026-04-27 | BNL302 | IST → BEN | Apr 27, 11:40 UTC | Apr 27, 13:15 UTC | 1h 35m |
| 2026-04-26 | BNL304 | IST → BEN | Apr 26, 16:00 UTC | Apr 27, 08:50 UTC | 16h 50m |
| 2026-04-25 | BNL236 | - | Apr 25, 16:25 UTC | Apr 26, 16:05 UTC | 23h 40m |
| 2026-04-25 | BNL235 | - | Apr 25, 14:00 UTC | Apr 25, 14:30 UTC | 30m |
| 2026-04-24 | BNL235 | - | Apr 24, 19:55 UTC | Apr 25, 14:30 UTC | 18h 35m |
| 2026-04-24 | BNL235 | - | Apr 24, 17:55 UTC | Apr 25, 14:30 UTC | 20h 35m |
| 2026-04-23 | BNL236 | - | Apr 23, 20:20 UTC | Apr 24, 20:10 UTC | 23h 50m |
| 2026-04-23 | BNL236 | - | Apr 23, 18:10 UTC | Apr 23, 20:25 UTC | 2h 15m |
| 2026-04-22 | BNL236 | - | Apr 22, 20:45 UTC | Apr 23, 18:10 UTC | 21h 25m |
| 2026-04-22 | BNL235 | - | Apr 22, 15:45 UTC | Apr 22, 18:45 UTC | 3h 0m |
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 5A-BRC page for operator, model, and routing details .