BIZTRAC BETA
Construction of residential and non-residential buildings

VELBYGD EIENDOMSINVEST AS

Org. no. 920950108 Limited company (AS) Haugesund Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −432,000
Equity NOK 19.5m
Incorporated 2018
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−432k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VELBYGD EIENDOMSINVEST AS is registered as a limited company in Haugesund, Rogaland with organisation number 920950108. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Felles investeringsselskap for investeringer og prosjekter som Abra Eiendom AS, direkte eller indirekte, eier sammen med Ramo Eiendom AS.”.

Key figures · 2024

Operating profit
NOK −432,000
Equity
NOK 19.5m
Est. value
NOK 20.0m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.6%
Satisfactory
Equity as a share of total capital

Who owns VELBYGD EIENDOMSINVEST AS?

ABRA EIENDOM AS
VELBYGD EIENDOMSINVEST AS
· NOK −432,000 profit

VELBYGD EIENDOMSINVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VELBYGD EIENDOMSINVEST AS own?

VELBYGD EIENDOMSINVEST AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about VELBYGD EIENDOMSINVEST AS

Who owns VELBYGD EIENDOMSINVEST AS?

ABRA EIENDOM AS is the largest registered owner, with 90.1%.

Where is VELBYGD EIENDOMSINVEST AS based?

VELBYGD EIENDOMSINVEST AS has its business address in Haugesund.

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.