sensors Mode-S transponder
0180A0
ICAO 24-bit transponder address · allocated to Libya
Currently assigned to 5A-BRB · AIRBUS A-320
- Hex
- 0180A0
- Octal
- 00300240
- Decimal
- 98,464
- Country
- LY
- Tail
- 5A-BRB
- Type
- A320
- Flights observed
- 72
- Distinct callsigns
- 20
- Country
- LY
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address 0180A0 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 |
|---|---|---|---|
| BNL462 | Blue Nile Ethiopia Trading | 9 | 2026-05-11 |
| BNL461 | Blue Nile Ethiopia Trading | 7 | 2026-05-09 |
| BNL303 | Blue Nile Ethiopia Trading | 7 | 2026-05-17 |
| BNL232 | - | 6 | 2026-05-11 |
| BNL464 | Blue Nile Ethiopia Trading | 5 | 2026-05-08 |
| BNL304 | Blue Nile Ethiopia Trading | 5 | 2026-05-14 |
| BNL231 | - | 5 | 2026-04-29 |
| BNL234 | Blue Nile Ethiopia Trading | 4 | 2026-05-02 |
| BNL463 | Blue Nile Ethiopia Trading | 3 | 2026-05-08 |
| BNL331 | Blue Nile Ethiopia Trading | 3 | 2026-05-05 |
| BNL235 | - | 3 | 2026-05-16 |
| BNL233 | - | 3 | 2026-05-08 |
| BNL6001 | - | 2 | 2026-05-17 |
| BNL472 | Blue Nile Ethiopia Trading | 2 | 2026-05-05 |
| BNL332 | Blue Nile Ethiopia Trading | 2 | 2026-05-05 |
| BNL741 | Blue Nile Ethiopia Trading | 1 | 2026-04-20 |
| BNL740 | Blue Nile Ethiopia Trading | 1 | 2026-04-20 |
| BNL451 | Blue Nile Ethiopia Trading | 1 | 2026-04-29 |
| BNL236 | - | 1 | 2026-04-21 |
| BNL104 | Blue Nile Ethiopia Trading | 1 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-17 | BNL6001 | - | May 17, 20:05 UTC | May 18, 15:15 UTC | 19h 10m |
| 2026-05-17 | BNL6001 | - | May 17, 19:20 UTC | May 18, 15:15 UTC | 19h 55m |
| 2026-05-17 | BNL303 | BEN → IST | May 17, 15:50 UTC | May 17, 17:30 UTC | 1h 40m |
| 2026-05-16 | BNL303 | BEN → IST | May 16, 20:50 UTC | May 17, 17:30 UTC | 20h 40m |
| 2026-05-16 | BNL235 | - | May 16, 17:50 UTC | May 16, 18:10 UTC | 20m |
| 2026-05-14 | BNL304 | IST → BEN | May 14, 19:30 UTC | May 14, 21:20 UTC | 1h 50m |
| 2026-05-14 | BNL303 | BEN → IST | May 14, 12:35 UTC | May 14, 17:15 UTC | 4h 40m |
| 2026-05-12 | BNL304 | IST → BEN | May 12, 19:40 UTC | May 13, 08:55 UTC | 13h 15m |
| 2026-05-12 | BNL303 | BEN → IST | May 12, 15:45 UTC | May 12, 17:35 UTC | 1h 50m |
| 2026-05-11 | BNL232 | MJI → BEN | May 11, 16:40 UTC | May 11, 17:35 UTC | 56m |
| 2026-05-11 | BNL462 | CAI → MJI | May 11, 12:00 UTC | May 11, 14:25 UTC | 2h 25m |
| 2026-05-11 | BNL462 | CAI → MJI | May 11, 08:15 UTC | May 11, 09:05 UTC | 50m |
| 2026-05-10 | BNL304 | IST → BEN | May 10, 19:40 UTC | May 11, 06:30 UTC | 10h 50m |
| 2026-05-09 | BNL303 | BEN → IST | May 9, 22:25 UTC | May 10, 17:55 UTC | 19h 30m |
| 2026-05-09 | BNL235 | - | May 9, 16:20 UTC | May 9, 20:05 UTC | 3h 45m |
| 2026-05-09 | BNL462 | CAI → MJI | May 9, 12:05 UTC | May 9, 14:30 UTC | 2h 25m |
| 2026-05-09 | BNL461 | MJI → CAI | May 9, 08:15 UTC | May 9, 09:50 UTC | 1h 35m |
| 2026-05-08 | BNL464 | CAI → MJI | May 8, 20:45 UTC | May 8, 23:00 UTC | 2h 15m |
| 2026-05-08 | BNL463 | MJI → CAI | May 8, 16:25 UTC | May 8, 17:55 UTC | 1h 30m |
| 2026-05-08 | BNL233 | - | May 8, 13:30 UTC | May 8, 13:55 UTC | 25m |
| 2026-05-07 | BNL233 | - | May 7, 14:15 UTC | May 8, 13:55 UTC | 23h 40m |
| 2026-05-07 | BNL233 | - | May 7, 12:00 UTC | May 7, 12:20 UTC | 20m |
| 2026-05-05 | BNL472 | CAI → MRA | May 5, 16:55 UTC | May 5, 22:50 UTC | 5h 55m |
| 2026-05-05 | BNL332 | IST → MRA | May 5, 11:55 UTC | May 5, 14:30 UTC | 2h 35m |
| 2026-05-05 | BNL331 | MRA → IST | May 5, 07:40 UTC | May 5, 09:50 UTC | 2h 10m |
| 2026-05-04 | BNL232 | - | May 4, 16:30 UTC | May 4, 16:50 UTC | 20m |
| 2026-05-04 | BNL462 | CAI → MJI | May 4, 11:50 UTC | May 4, 14:10 UTC | 2h 20m |
| 2026-05-04 | BNL461 | MJI → CAI | May 4, 08:20 UTC | May 4, 08:40 UTC | 20m |
| 2026-05-03 | BNL304 | IST → BEN | May 3, 19:25 UTC | May 4, 06:15 UTC | 10h 50m |
| 2026-05-03 | BNL303 | BEN → IST | May 3, 11:35 UTC | May 3, 16:55 UTC | 5h 20m |
| 2026-05-02 | BNL234 | MJI → BEN | May 2, 16:45 UTC | May 3, 15:50 UTC | 23h 4m |
| 2026-05-02 | BNL234 | MJI → BEN | May 2, 14:05 UTC | May 3, 11:45 UTC | 21h 39m |
| 2026-05-02 | BNL462 | CAI → MJI | May 2, 13:50 UTC | May 3, 11:45 UTC | 21h 54m |
| 2026-05-02 | BNL461 | MJI → CAI | May 2, 08:15 UTC | May 2, 17:00 UTC | 8h 45m |
| 2026-05-01 | BNL464 | CAI → MJI | May 1, 19:55 UTC | May 1, 22:25 UTC | 2h 30m |
| 2026-05-01 | BNL463 | MJI → CAI | May 1, 16:20 UTC | May 1, 18:25 UTC | 2h 5m |
| 2026-04-30 | BNL304 | IST → BEN | Apr 30, 19:25 UTC | May 1, 12:50 UTC | 17h 25m |
| 2026-04-30 | BNL303 | BEN → IST | Apr 30, 08:45 UTC | Apr 30, 17:15 UTC | 8h 30m |
| 2026-04-29 | BNL451 | CAI → BEN | Apr 29, 17:30 UTC | Apr 30, 16:00 UTC | 22h 30m |
| 2026-04-29 | BNL461 | MJI → CAI | Apr 29, 08:25 UTC | Apr 29, 14:35 UTC | 6h 11m |
| 2026-04-29 | BNL231 | - | Apr 29, 06:05 UTC | Apr 29, 06:49 UTC | 45m |
| 2026-04-27 | BNL234 | MJI → BEN | Apr 27, 17:10 UTC | Apr 27, 17:40 UTC | 30m |
| 2026-04-25 | BNL462 | CAI → MJI | Apr 25, 12:30 UTC | Apr 25, 14:55 UTC | 2h 25m |
| 2026-04-25 | BNL461 | MJI → CAI | Apr 25, 08:45 UTC | Apr 25, 10:25 UTC | 1h 40m |
| 2026-04-24 | BNL234 | MJI → BEN | Apr 24, 19:00 UTC | Apr 25, 06:30 UTC | 11h 30m |
| 2026-04-24 | BNL464 | CAI → MJI | Apr 24, 14:55 UTC | Apr 24, 17:05 UTC | 2h 10m |
| 2026-04-24 | BNL463 | MJI → CAI | Apr 24, 11:10 UTC | Apr 24, 12:40 UTC | 1h 30m |
| 2026-04-23 | BNL104 | TUN → BEN | Apr 23, 21:55 UTC | Apr 24, 09:15 UTC | 11h 20m |
| 2026-04-23 | BNL103 | BEN → TUN | Apr 23, 19:25 UTC | Apr 23, 20:15 UTC | 50m |
| 2026-04-22 | BNL232 | - | Apr 22, 16:45 UTC | Apr 22, 17:10 UTC | 25m |
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-BRB page for operator, model, and routing details .