BIZTRAC BETA
Rental and operating of own or leased real estate

KONGSBERG INDUSTRIBYGG AS

Org. no. 921580592 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 47.1m
Operating profit NOK 21.8m
Equity NOK 342.4m
Incorporated 2018
Share capital NOK 30,000

Signals

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

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

Key figures · 2024

Revenue
NOK 47.1m
Operating profit
NOK 21.8m
Equity
NOK 342.4m
Est. value
NOK 296.3m

Financial health · 2024

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

Who owns KONGSBERG INDUSTRIBYGG AS?

KTP HOLDING I AS
KONGSBERG INDUSTRIBYGG AS
NOK 47.1m rev. · NOK 21.8m profit

KONGSBERG INDUSTRIBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSBERG INDUSTRIBYGG AS

Who owns KONGSBERG INDUSTRIBYGG AS?

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

What is the revenue of KONGSBERG INDUSTRIBYGG AS?

KONGSBERG INDUSTRIBYGG AS had revenue of NOK 47.1m in 2024.

Where is KONGSBERG INDUSTRIBYGG AS based?

KONGSBERG INDUSTRIBYGG 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.