BIZTRAC BETA
Rental and operating of own or leased real estate

VITRIUM AS

Org. no. 985684367 Limited company (AS) Rakkestad Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 214,000
Operating profit NOK −1.4m
Equity NOK 26.0m
Incorporated 2003
Share capital NOK 270,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

VITRIUM AS is registered as a limited company in Rakkestad, Østfold with organisation number 985684367. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 270,000, divided into 100 shares. The company's stated purpose is: “Erverv og drift av fast eiendom. Erverv og forvaltning av aksjer og verdipapirer, samt forøvrig delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 214,000 in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 214,000
Operating profit
NOK −1.4m
Equity
NOK 26.0m
Est. value
NOK 23.8m

Financial health · 2024

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

Who owns VITRIUM AS?

JAN PETTER LUNDEBY
VITRIUM AS
NOK 214,000 rev. · NOK −1.4m profit

VITRIUM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VITRIUM AS own?

VITRIUM AS holds stakes in 10 companies:

See the full ownership structure →

Group structure

VITRIUM AS er morselskap for 6 datterselskaper:

Frequently asked questions about VITRIUM AS

Who owns VITRIUM AS?

JAN PETTER LUNDEBY is the largest registered owner, with 100.0%.

What is the revenue of VITRIUM AS?

VITRIUM AS had revenue of NOK 214,000 in 2024.

Where is VITRIUM AS based?

VITRIUM AS has its business address in Rakkestad.

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.