BIZTRAC BETA
Buying and selling of own real estate

VESTRE AKER EIENDOMSSELSKAB AS

Org. no. 915550215 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −60,000
Equity NOK −162,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−162k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−60k kr).

VESTRE AKER EIENDOMSSELSKAB AS is registered as a limited company in Oslo, Oslo with organisation number 915550215. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, investeringer i verdipapirer, samt alt som hører naturlig til dette.”.

Key figures · 2024

Operating profit
NOK −60,000
Equity
NOK −162,000

Financial health · 2024

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

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

Who owns VESTRE AKER EIENDOMSSELSKAB AS?

NEO INVESTMENT GROUP B.V
VESTRE AKER EIENDOMSSELSKAB AS
· NOK −60,000 profit

VESTRE AKER EIENDOMSSELSKAB AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VESTRE AKER EIENDOMSSELSKAB AS own?

VESTRE AKER EIENDOMSSELSKAB AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VESTRE AKER EIENDOMSSELSKAB AS

Who owns VESTRE AKER EIENDOMSSELSKAB AS?

NEO INVESTMENT GROUP B.V is the largest registered owner, with 50.7%.

Where is VESTRE AKER EIENDOMSSELSKAB AS based?

VESTRE AKER EIENDOMSSELSKAB 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.