biztrac. BETA
COMPANY REGISTER PROFILE
989146726 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ULVEN AS

Org. no. 989146726 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 65.8m
Operating profit NOK 19.5m
Equity NOK 1.1bn
Incorporated 2005
Share capital NOK 22.7m

ULVEN AS is registered as a limited company in Oslo, Oslo with organisation number 989146726. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 22.7m, divided into 1 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 65.8m in revenue and NOK 19.5m in operating profit.

Former names: NYE KRISTIANIA EIENDOMSFORVALTNING AS, STOR ULVEN AS

Key figures · 2025

Revenue
NOK 65.8m
▲ +1 %
Operating profit
NOK 19.5m
▲ +115 %
Equity
NOK 1.1bn
▼ −1 %
Est. value
NOK 796.6m

Financial health · 2025

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.1%
Weak
Return on total assets
Solidity
93.8%
Very good
Equity as a share of total capital

Who owns ULVEN AS?

ULVEN AS
NOK 65.8m rev. · NOK 19.5m profit

ULVEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ULVEN AS own?

ULVEN AS holds stakes in 6 companies:

See the full ownership structure →

Group structure

ULVEN AS er morselskap for 67 datterselskaper:

Frequently asked questions about ULVEN AS

Who owns ULVEN AS?

OBOS EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ULVEN AS?

ULVEN AS had revenue of NOK 65.8m in 2025.

Where is ULVEN AS based?

ULVEN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.