biztrac. BETA
COMPANY REGISTER PROFILE
918100687 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

VESTGRENSA EIENDOM AS

Org. no. 918100687 Limited company (AS) Oslo Incorporated 2016 Active
Revenue 2025 NOK 10.1m
Operating profit NOK 5.6m
Equity NOK 9.1m
Incorporated 2016
Share capital NOK 300,000

Signals

1 flags
  • Nylig endring 2026-09-17 Adresseendring registrert 2026-09-17.

VESTGRENSA EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 918100687. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Fast eiendom, herunder utleie, drift, kjøp og salg samt investering i aksjer og andre verdipapirer, herunder aktiv deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.1m in revenue and NOK 5.6m in operating profit.

Key figures · 2025

Revenue
NOK 10.1m
▲ +10 %
Operating profit
NOK 5.6m
▲ +6 %
Equity
NOK 9.1m
▼ −4 %
Est. value
NOK 18.8m

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
13.6%
Good
Return on total assets
Solidity
22.0%
Good
Equity as a share of total capital

Who owns VESTGRENSA EIENDOM AS?

VESTGRENSA EIENDOM AS
NOK 10.1m rev. · NOK 5.6m profit

VESTGRENSA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTGRENSA EIENDOM AS

Who owns VESTGRENSA EIENDOM AS?

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

What is the revenue of VESTGRENSA EIENDOM AS?

VESTGRENSA EIENDOM AS had revenue of NOK 10.1m in 2025.

Where is VESTGRENSA EIENDOM AS based?

VESTGRENSA 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 03.10.2026.

Report a problem

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