BIZTRAC BETA
Other captive investment companies

NORUM UTBYGGING AS

Org. no. 917131406 Limited company (AS) Steinkjer Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 20,000
Operating profit NOK −38,000
Equity NOK 5.5m
Incorporated 2016
Share capital NOK 30,000

Signals

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

NORUM UTBYGGING AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 917131406. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 20,000 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 20,000
Operating profit
NOK −38,000
Equity
NOK 5.5m
Est. value
NOK 5.6m

Financial health · 2025

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

Who owns NORUM UTBYGGING AS?

HÅVARD STAVRUM NORUM
NORUM UTBYGGING AS
NOK 20,000 rev. · NOK −38,000 profit

NORUM UTBYGGING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORUM UTBYGGING AS own?

NORUM UTBYGGING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NORUM UTBYGGING AS

Who owns NORUM UTBYGGING AS?

HÅVARD STAVRUM NORUM is the largest registered owner, with 100.0%.

What is the revenue of NORUM UTBYGGING AS?

NORUM UTBYGGING AS had revenue of NOK 20,000 in 2025.

Where is NORUM UTBYGGING AS based?

NORUM UTBYGGING AS has its business address in Steinkjer.

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.