BIZTRAC BETA
Rental and operating of own or leased real estate

VALO EIGEDOM AS

Org. no. 914754763 Limited company (AS) Kvinnherad Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 852,000
Operating profit NOK 569,000
Equity NOK −886,000
Incorporated 2014
Share capital NOK 40,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−886k kr).

VALO EIGEDOM AS is registered as a limited company in Kvinnherad, Vestland with organisation number 914754763. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 40,000, divided into 400 shares. The company's stated purpose is: “Investering i, utbygging og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 852,000 in revenue and NOK 569,000 in operating profit.

Key figures · 2024

Revenue
NOK 852,000
Operating profit
NOK 569,000
Equity
NOK −886,000
Est. value
NOK 3.9m

Financial health · 2024

Liquidity
0.24
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VALO EIGEDOM AS?

IDEAL EIENDOM AS
VALO EIGEDOM AS
NOK 852,000 rev. · NOK 569,000 profit

VALO EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VALO EIGEDOM AS

Who owns VALO EIGEDOM AS?

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

What is the revenue of VALO EIGEDOM AS?

VALO EIGEDOM AS had revenue of NOK 852,000 in 2024.

Who is the general manager of VALO EIGEDOM AS?

Elin Stene is registered as general manager of VALO EIGEDOM AS.

Where is VALO EIGEDOM AS based?

VALO EIGEDOM AS has its business address in Valen.

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.