sensors Mode-S transponder
0180AD
ICAO 24-bit transponder address · allocated to Libya
Currently assigned to 5A-GRS · BOEING 777-200
- Hex
- 0180AD
- Octal
- 00300255
- Decimal
- 98,477
- Country
- LY
- Tail
- 5A-GRS
- Type
- B772
- Flights observed
- 35
- Distinct callsigns
- 14
- Country
- LY
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 0180AD 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OYA571 | Fly OYA | 7 | 2026-05-30 |
| OYA570 | Fly OYA | 7 | 2026-05-23 |
| OYA592 | Fly OYA | 3 | 2026-04-30 |
| OYA5551 | - | 3 | 2026-05-16 |
| OYA5571 | Fly OYA | 2 | 2026-05-17 |
| OYA5541 | Fly OYA | 2 | 2026-05-14 |
| OYA5521 | Fly OYA | 2 | 2026-05-20 |
| OYA5511 | Fly OYA | 2 | 2026-05-19 |
| 00000000 | - | 2 | 2026-05-21 |
| OYA593 | Fly OYA | 1 | 2026-04-16 |
| OYA5561 | - | 1 | 2026-05-16 |
| OYA5531 | Fly OYA | 1 | 2026-05-13 |
| OYA503 | Fly OYA | 1 | 2026-04-26 |
| OYA502 | Fly OYA | 1 | 2026-04-26 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | OYA571 | DWC → MJI | May 30, 09:10 UTC | May 30, 19:30 UTC | 10h 20m |
| 2026-05-23 | OYA570 | MJI → DWC | May 23, 09:45 UTC | May 23, 22:05 UTC | 12h 20m |
| 2026-05-21 | 00000000 | - | May 21, 00:15 UTC | May 21, 00:30 UTC | 15m |
| 2026-05-20 | OYA5521 | JED → MJI | May 20, 05:35 UTC | May 20, 05:55 UTC | 20m |
| 2026-05-19 | OYA5511 | JED → MJI | May 19, 08:50 UTC | May 19, 09:10 UTC | 20m |
| 2026-05-17 | OYA5571 | JED → MJI | May 17, 21:01 UTC | May 17, 21:25 UTC | 25m |
| 2026-05-16 | OYA5561 | - | May 16, 19:20 UTC | May 16, 21:45 UTC | 2h 25m |
| 2026-05-16 | OYA5551 | - | May 16, 00:10 UTC | May 16, 00:45 UTC | 35m |
| 2026-05-15 | OYA5551 | - | May 15, 03:35 UTC | May 16, 00:45 UTC | 21h 9m |
| 2026-05-14 | OYA5541 | JED → MJI | May 14, 21:45 UTC | May 14, 22:20 UTC | 35m |
| 2026-05-13 | OYA5531 | JED → MJI | May 13, 23:05 UTC | May 13, 23:30 UTC | 25m |
| 2026-05-13 | OYA5521 | JED → MJI | May 13, 01:05 UTC | May 13, 03:35 UTC | 2h 30m |
| 2026-05-11 | OYA5511 | JED → MJI | May 11, 21:40 UTC | May 11, 22:15 UTC | 35m |
| 2026-05-10 | OYA5571 | JED → MJI | May 10, 20:50 UTC | May 10, 21:14 UTC | 25m |
| 2026-05-09 | OYA571 | DWC → MJI | May 9, 19:00 UTC | May 9, 19:19 UTC | 20m |
| 2026-05-09 | OYA570 | MJI → DWC | May 9, 06:45 UTC | May 9, 10:55 UTC | 4h 10m |
| 2026-05-08 | OYA5551 | - | May 8, 20:05 UTC | May 8, 22:20 UTC | 2h 15m |
| 2026-05-07 | OYA5541 | JED → MJI | May 7, 21:20 UTC | May 7, 21:50 UTC | 30m |
| 2026-05-02 | OYA571 | DWC → MJI | May 2, 13:45 UTC | May 2, 19:40 UTC | 5h 55m |
| 2026-05-02 | OYA570 | MJI → DWC | May 2, 06:35 UTC | May 2, 11:15 UTC | 4h 40m |
| 2026-04-30 | OYA592 | MJI → CAI | Apr 30, 07:55 UTC | Apr 30, 14:05 UTC | 6h 10m |
| 2026-04-29 | OYA571 | DWC → MJI | Apr 29, 14:10 UTC | Apr 29, 20:20 UTC | 6h 10m |
| 2026-04-29 | OYA570 | MJI → DWC | Apr 29, 06:35 UTC | Apr 29, 11:10 UTC | 4h 36m |
| 2026-04-26 | OYA503 | IST → MJI | Apr 26, 23:10 UTC | Apr 27, 02:10 UTC | 3h 0m |
| 2026-04-26 | OYA502 | MJI → IST | Apr 26, 18:10 UTC | Apr 26, 20:25 UTC | 2h 15m |
| 2026-04-26 | 00000000 | - | Apr 26, 07:45 UTC | Apr 26, 14:25 UTC | 6h 40m |
| 2026-04-25 | OYA571 | DWC → MJI | Apr 25, 15:55 UTC | Apr 25, 21:45 UTC | 5h 50m |
| 2026-04-25 | OYA570 | MJI → DWC | Apr 25, 08:30 UTC | Apr 25, 13:05 UTC | 4h 35m |
| 2026-04-22 | OYA571 | DWC → MJI | Apr 22, 14:05 UTC | Apr 22, 20:10 UTC | 6h 5m |
| 2026-04-22 | OYA570 | MJI → DWC | Apr 22, 06:20 UTC | Apr 22, 10:55 UTC | 4h 35m |
| 2026-04-19 | OYA592 | MJI → CAI | Apr 19, 07:30 UTC | Apr 19, 14:05 UTC | 6h 35m |
| 2026-04-18 | OYA571 | DWC → MJI | Apr 18, 16:20 UTC | Apr 18, 17:25 UTC | 1h 5m |
| 2026-04-18 | OYA570 | MJI → DWC | Apr 18, 09:10 UTC | Apr 18, 13:50 UTC | 4h 40m |
| 2026-04-16 | OYA593 | CAI → MJI | Apr 16, 13:54 UTC | Apr 16, 14:10 UTC | 15m |
| 2026-04-16 | OYA592 | MJI → CAI | Apr 16, 08:00 UTC | Apr 16, 08:19 UTC | 20m |
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-GRS page for operator, model, and routing details .