BIZTRAC BETA
Freight coastal transport

KLØVERLAKS II AS

Org. no. 927901188 Limited company (AS) Austevoll Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 33.0m
Operating profit NOK 18.3m
Equity NOK −414,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−414k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KLØVERLAKS II AS is registered as a limited company in Austevoll, Vestland with organisation number 927901188. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie og drifte skip til transport av fisk og tilsvarende formål, samt det som naturlig måtte stå i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 33.0m in revenue and NOK 18.3m in operating profit.

Key figures · 2024

Revenue
NOK 33.0m
Operating profit
NOK 18.3m
Equity
NOK −414,000
Est. value
NOK 90.6m

Financial health · 2024

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KLØVERLAKS II AS?

LACO AS
KLØVERLAKS II AS
NOK 33.0m rev. · NOK 18.3m profit

KLØVERLAKS II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLØVERLAKS II AS

Who owns KLØVERLAKS II AS?

LACO AS is the largest registered owner, with 100.0%.

What is the revenue of KLØVERLAKS II AS?

KLØVERLAKS II AS had revenue of NOK 33.0m in 2024.

Where is KLØVERLAKS II AS based?

KLØVERLAKS II 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 15.06.2026.

Report a problem

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