biztrac. BETA
COMPANY REGISTER PROFILE
922779368 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

HETLEVIK AS

Org. no. 922779368 Limited company (AS) Bergen Incorporated 2019 Active
Operating profit NOK −104,000
Equity NOK 19.4m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−104k kr).

HETLEVIK AS is registered as a limited company in Bergen, Vestland with organisation number 922779368. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Drive investeringsvirksomhet, forvaltning av verdipapir, kjøp og salg av dette, drive forretningsmessig virksomhet, eiendomsselskap med forvaltning, kjøp og salg av eiendommer. Samt annet som er i beslektet med ovenfornevnte merknader, samt delta i andre selskap med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −104,000
▲ +76 %
Equity
NOK 19.4m
▲ +19 %
Est. value
NOK 24.9m

Financial health · 2025

Liquidity
65.83
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
98.8%
Very good
Equity as a share of total capital

Who owns HETLEVIK AS?

HETLEVIK AS
· NOK −104,000 profit

HETLEVIK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HETLEVIK AS own?

HETLEVIK AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about HETLEVIK AS

Who owns HETLEVIK AS?

Bjørn Ove Hetlevik is the largest registered owner, with 100.0%.

Who is the general manager of HETLEVIK AS?

Bjørn Ove Hetlevik is registered as general manager of HETLEVIK AS.

Where is HETLEVIK AS based?

HETLEVIK AS has its business address in Fana.

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.