BIZTRAC BETA
Rental and operating of own or leased real estate

KONGSBERGPORTEN HOLDING AS

Org. no. 927996502 Limited company (AS) Kongsberg Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −149,000
Equity NOK 40.2m
Incorporated 2021
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−149k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KONGSBERGPORTEN HOLDING AS is registered as a limited company in Kongsberg, Buskerud with organisation number 927996502. 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 60,000, divided into 3000 shares. The company's stated purpose is: “Investering i eiendom og andre selskaper som driver utvikling, forvaltning og drift av eiendom med dertil tilhørende virksomhet.”.

Key figures · 2024

Operating profit
NOK −149,000
Equity
NOK 40.2m
Est. value
NOK 27.9m

Financial health · 2024

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

Who owns KONGSBERGPORTEN HOLDING AS?

BEVER HOLDING AS
KONGSBERGPORTEN HOLDING AS
· NOK −149,000 profit

KONGSBERGPORTEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KONGSBERGPORTEN HOLDING AS own?

KONGSBERGPORTEN HOLDING AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about KONGSBERGPORTEN HOLDING AS

Who owns KONGSBERGPORTEN HOLDING AS?

BEVER HOLDING AS is the largest registered owner, with 100.0%.

Where is KONGSBERGPORTEN HOLDING AS based?

KONGSBERGPORTEN HOLDING AS has its business address in Skollenborg.

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.