BIZTRAC BETA
Rental and operating of own or leased real estate

HELLEBÆK AS

Org. no. 928083217 Limited company (AS) Kongsberg Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −78,000
Equity NOK 28.4m
Incorporated 2021
Share capital NOK 1.5m

Signals

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

HELLEBÆK AS is registered as a limited company in Kongsberg, Buskerud with organisation number 928083217. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 1.5m, divided into 6000 shares. The company's stated purpose is: “Å eie aksjer i andre selskap, samt annen virksomhet som står i nær sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −78,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −78,000
Equity
NOK 28.4m
Est. value
NOK 79.2m

Financial health · 2025

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

Who owns HELLEBÆK AS?

GEIR SYVERTSEN AS
HELLEBÆK AS
NOK 0 rev. · NOK −78,000 profit

HELLEBÆK AS has 9 registered shareholders:

All shareholders and roles →

Which companies does HELLEBÆK AS own?

HELLEBÆK AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about HELLEBÆK AS

Who owns HELLEBÆK AS?

GEIR SYVERTSEN AS is the largest registered owner, with 21.9%.

What is the revenue of HELLEBÆK AS?

HELLEBÆK AS had revenue of NOK 0 in 2025.

Who is the general manager of HELLEBÆK AS?

Per Winsvold Mikkelsen is registered as general manager of HELLEBÆK AS.

Where is HELLEBÆK AS based?

HELLEBÆK AS has its business address in Kongsberg.

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.