BIZTRAC BETA
Uoppgitt

HAVELAND INVEST AS

Org. no. 924922117 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK 102,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

HAVELAND INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 924922117. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 102,000
Est. value
NOK 120,000

Financial health · 2024

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.1%
Good
Equity as a share of total capital

Who owns HAVELAND INVEST AS?

JOHAN CATO HAVELAND
HAVELAND INVEST AS
NOK 0 rev. · NOK −5,000 profit

HAVELAND INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAVELAND INVEST AS own?

HAVELAND INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HAVELAND INVEST AS

Who owns HAVELAND INVEST AS?

JOHAN CATO HAVELAND is the largest registered owner, with 100.0%.

What is the revenue of HAVELAND INVEST AS?

HAVELAND INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of HAVELAND INVEST AS?

Johan Cato Haveland is registered as general manager of HAVELAND INVEST AS.

Where is HAVELAND INVEST AS based?

HAVELAND INVEST AS has its business address in Bergen.

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.