BIZTRAC BETA
Buying and selling of own real estate

VESTHEIM EIENDOM AS

Org. no. 966974605 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 77,000
Operating profit NOK −162,000
Equity NOK 2.1m
Incorporated 1993
Share capital NOK 291,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−162k kr).
  • Nylig endring 2026-02-03 Adresseendring registrert 2026-02-03.

VESTHEIM EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 966974605. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1993. Registered share capital is NOK 291,000, divided into 291 shares. The company's stated purpose is: “Utvikle, eie og forvalte fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 77,000 in revenue and NOK −162,000 in operating profit.

Key figures · 2024

Revenue
NOK 77,000
Operating profit
NOK −162,000
Equity
NOK 2.1m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns VESTHEIM EIENDOM AS?

SALOMONSEN HOLDING AS
VESTHEIM EIENDOM AS
NOK 77,000 rev. · NOK −162,000 profit

VESTHEIM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTHEIM EIENDOM AS

Who owns VESTHEIM EIENDOM AS?

SALOMONSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VESTHEIM EIENDOM AS?

VESTHEIM EIENDOM AS had revenue of NOK 77,000 in 2024.

Who is the general manager of VESTHEIM EIENDOM AS?

Cathrine Seehusen Bentsrud is registered as general manager of VESTHEIM EIENDOM AS.

Where is VESTHEIM EIENDOM AS based?

VESTHEIM EIENDOM 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 15.06.2026.

Report a problem

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