BIZTRAC BETA
Rental and operating of own or leased real estate

URSTAD EIENDOM AS

Org. no. 980635864 Limited company (AS) Moss Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 521,000
Operating profit NOK −168,000
Equity NOK 43,000
Incorporated 1999
Share capital NOK 418,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−168k kr).

URSTAD EIENDOM AS is registered as a limited company in Moss, Østfold with organisation number 980635864. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 418,000, divided into 4180 shares. The company's stated purpose is: “Besittelse og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 521,000 in revenue and NOK −168,000 in operating profit.

Key figures · 2025

Revenue
NOK 521,000
Operating profit
NOK −168,000
Equity
NOK 43,000
Est. value
NOK 810,000

Financial health · 2024

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

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

Who owns URSTAD EIENDOM AS?

VIGDIS URSTAD
URSTAD EIENDOM AS
NOK 521,000 rev. · NOK −168,000 profit

URSTAD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about URSTAD EIENDOM AS

Who owns URSTAD EIENDOM AS?

VIGDIS URSTAD is the largest registered owner, with 51.0%.

What is the revenue of URSTAD EIENDOM AS?

URSTAD EIENDOM AS had revenue of NOK 521,000 in 2025.

Who is the general manager of URSTAD EIENDOM AS?

Arne Urstad is registered as general manager of URSTAD EIENDOM AS.

Where is URSTAD EIENDOM AS based?

URSTAD EIENDOM AS has its business address in Rygge.

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.