BIZTRAC BETA
Operation of marine fish farms

HAVBLIKK INVEST AS

Org. no. 992499923 Limited company (AS) Bergen Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 2.8m
Equity NOK −5.9m
Incorporated 2008
Share capital NOK 500,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5,9 mill kr).

HAVBLIKK INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 992499923. The business is classified under operation of marine fish farms (NACE 03.211). The company was incorporated in 2008. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Investering i eiendom og verdipapirer, og utvikling av eiendom og beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 2.8m
Equity
NOK −5.9m
Est. value
NOK 13.8m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-62253.8%
Weak
Equity as a share of total capital

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

Who owns HAVBLIKK INVEST AS?

BO-BYGG AS
HAVBLIKK INVEST AS
NOK 4.2m rev. · NOK 2.8m profit

HAVBLIKK INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HAVBLIKK INVEST AS own?

HAVBLIKK INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAVBLIKK INVEST AS

Who owns HAVBLIKK INVEST AS?

BO-BYGG AS is the largest registered owner, with 50.0%.

What is the revenue of HAVBLIKK INVEST AS?

HAVBLIKK INVEST AS had revenue of NOK 4.2m in 2024.

Where is HAVBLIKK INVEST AS based?

HAVBLIKK INVEST AS has its business address in Paradis.

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.