BIZTRAC BETA
Rental and operating of own or leased real estate

KONGSBERG KONTOREIENDOM AS

Org. no. 912891291 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 12.9m
Operating profit NOK 34.6m
Equity NOK 153.6m
Incorporated 2013
Share capital NOK 1.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KONGSBERG KONTOREIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 912891291. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 1.5m, divided into 30000 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andre eiendeler, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.9m in revenue and NOK 34.6m in operating profit.

Key figures · 2024

Revenue
NOK 12.9m
Operating profit
NOK 34.6m
Equity
NOK 153.6m
Est. value
NOK 171.0m

Financial health · 2024

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

Who owns KONGSBERG KONTOREIENDOM AS?

KTP HOLDING III AS
KONGSBERG KONTOREIENDOM AS
NOK 12.9m rev. · NOK 34.6m profit

KONGSBERG KONTOREIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSBERG KONTOREIENDOM AS

Who owns KONGSBERG KONTOREIENDOM AS?

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

What is the revenue of KONGSBERG KONTOREIENDOM AS?

KONGSBERG KONTOREIENDOM AS had revenue of NOK 12.9m in 2024.

Where is KONGSBERG KONTOREIENDOM AS based?

KONGSBERG KONTOREIENDOM AS has its business address in Oslo.

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.