BIZTRAC BETA
Development of building projects

ULVOLDEN EIENDOM AS

Org. no. 913129342 Limited company (AS) Vågå Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −14,000
Equity NOK 596,000
Incorporated 2014
Share capital NOK 105,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14k kr).

ULVOLDEN EIENDOM AS is registered as a limited company in Vågå, Innlandet with organisation number 913129342. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 105,000, divided into 100 shares. The company's stated purpose is: “Eiendomsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 596,000
Est. value
NOK 544,000

Financial health · 2024

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

Who owns ULVOLDEN EIENDOM AS?

ULVOLDEN AS
ULVOLDEN EIENDOM AS
NOK 0 rev. · NOK −14,000 profit

ULVOLDEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ULVOLDEN EIENDOM AS own?

ULVOLDEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ULVOLDEN EIENDOM AS

Who owns ULVOLDEN EIENDOM AS?

ULVOLDEN AS is the largest registered owner, with 100.0%.

What is the revenue of ULVOLDEN EIENDOM AS?

ULVOLDEN EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of ULVOLDEN EIENDOM AS?

Stein Per Ulvolden is registered as general manager of ULVOLDEN EIENDOM AS.

Where is ULVOLDEN EIENDOM AS based?

ULVOLDEN EIENDOM AS has its business address in Vågå.

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.