biztrac. BETA
COMPANY REGISTER PROFILE
914047757 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

OPILIO AS

Org. no. 914047757 Limited company (AS) Austevoll Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 212.9m
Operating profit NOK 51.8m
Equity NOK 78.6m
Incorporated 2014
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-07-09 Adresseendring registrert 2026-07-09.

OPILIO AS is registered as a limited company in Austevoll, Vestland with organisation number 914047757. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie og drive fiskefartøy, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 212.9m in revenue and NOK 51.8m in operating profit.

Key figures · 2025

Revenue
NOK 212.9m
▲ +79 %
Operating profit
NOK 51.8m
▲ +316 %
Equity
NOK 78.6m
▲ +74 %
Est. value
NOK 85.6m

Financial health · 2025

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
20.6%
Very good
Return on total assets
Solidity
32.0%
Good
Equity as a share of total capital

Who owns OPILIO AS?

OPILIO AS
NOK 212.9m rev. · NOK 51.8m profit

OPILIO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OPILIO AS own?

OPILIO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OPILIO AS

Who owns OPILIO AS?

BR. BIRKELAND AS is the largest registered owner, with 100.0%.

What is the revenue of OPILIO AS?

OPILIO AS had revenue of NOK 212.9m in 2025.

Who is the general manager of OPILIO AS?

Åsmund Klokkeide Birkeland is registered as general manager of OPILIO AS.

Where is OPILIO AS based?

OPILIO AS has its business address in Storebø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.