BIZTRAC BETA
Development of building projects

V7 EIENDOM AS

Org. no. 818982992 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 309,000
Operating profit NOK 153,000
Equity NOK 11.0m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

V7 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 818982992. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1200 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andre eierandeler i andre selskaper og foretak samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 309,000 in revenue and NOK 153,000 in operating profit.

Key figures · 2025

Revenue
NOK 309,000
Operating profit
NOK 153,000
Equity
NOK 11.0m
Est. value
NOK 8.0m

Financial health · 2025

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

Who owns V7 EIENDOM AS?

ELEMENTUM AS
V7 EIENDOM AS
NOK 309,000 rev. · NOK 153,000 profit

V7 EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does V7 EIENDOM AS own?

V7 EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about V7 EIENDOM AS

Who owns V7 EIENDOM AS?

ELEMENTUM AS is the largest registered owner, with 50.0%.

What is the revenue of V7 EIENDOM AS?

V7 EIENDOM AS had revenue of NOK 309,000 in 2025.

Where is V7 EIENDOM AS based?

V7 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.