BIZTRAC BETA
Rental and operating of own or leased real estate

VISION EIENDOMSINVEST AS

Org. no. 916008031 Limited company (AS) Stavanger Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −30,000
Equity NOK 8.4m
Incorporated 2015
Share capital NOK 8.0m

Signals

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

VISION EIENDOMSINVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 916008031. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 8.0m, divided into 267664 shares. The company's stated purpose is: “Eie og investere i aksjer og andre selskaper og virksomheter, samt deltakelse av enhver art i andre forretningsforetak. Kjøp, salg og utleie av fast eiendom og hva dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −30,000
Equity
NOK 8.4m
Est. value
NOK 7.7m

Financial health · 2025

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

Who owns VISION EIENDOMSINVEST AS?

BIL VEST AS
VISION EIENDOMSINVEST AS
· NOK −30,000 profit

VISION EIENDOMSINVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VISION EIENDOMSINVEST AS own?

VISION EIENDOMSINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VISION EIENDOMSINVEST AS

Who owns VISION EIENDOMSINVEST AS?

BIL VEST AS is the largest registered owner, with 50.0%.

Who is the general manager of VISION EIENDOMSINVEST AS?

Torulf Østrått is registered as general manager of VISION EIENDOMSINVEST AS.

Where is VISION EIENDOMSINVEST AS based?

VISION EIENDOMSINVEST AS has its business address in Stavanger.

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.