BIZTRAC BETA
Rental and operating of own or leased real estate

VALSTAD EIENDOM AS

Org. no. 989129325 Limited company (AS) Eidsvoll Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 894,000
Equity NOK 14.9m
Incorporated 2005
Share capital NOK 666,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-05-02 Aksjekapital registrert 2026-05-02.

VALSTAD EIENDOM AS is registered as a limited company in Eidsvoll, Akershus with organisation number 989129325. 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 666,000, divided into 900000 shares. The company's stated purpose is: “Kjøp, salg, utleie og forvaltning av fast eiendom, samt investering i og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 894,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 894,000
Equity
NOK 14.9m
Est. value
NOK 11.9m

Financial health · 2025

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

Who owns VALSTAD EIENDOM AS?

VEMADO AS
VALSTAD EIENDOM AS
NOK 3.4m rev. · NOK 894,000 profit

VALSTAD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VALSTAD EIENDOM AS

Who owns VALSTAD EIENDOM AS?

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

What is the revenue of VALSTAD EIENDOM AS?

VALSTAD EIENDOM AS had revenue of NOK 3.4m in 2025.

Where is VALSTAD EIENDOM AS based?

VALSTAD EIENDOM AS has its business address in Eidsvoll Verk.

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.