BIZTRAC BETA
Rental and operating of own or leased real estate

VILLENGA EIENDOM BHG AS

Org. no. 933978141 Limited company (AS) Haugesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 25,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

VILLENGA EIENDOM BHG AS is registered as a limited company in Haugesund, Rogaland with organisation number 933978141. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie, drifte og/eller drive utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 25,000
Est. value
NOK 23,000

Financial health · 2024

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

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

Who owns VILLENGA EIENDOM BHG AS?

SFR EIENDOM AS
VILLENGA EIENDOM BHG AS
NOK 0 rev. · NOK −6,000 profit

VILLENGA EIENDOM BHG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VILLENGA EIENDOM BHG AS er morselskap for 210 datterselskaper:

Frequently asked questions about VILLENGA EIENDOM BHG AS

Who owns VILLENGA EIENDOM BHG AS?

SFR EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of VILLENGA EIENDOM BHG AS?

VILLENGA EIENDOM BHG AS had revenue of NOK 0 in 2024.

Where is VILLENGA EIENDOM BHG AS based?

VILLENGA EIENDOM BHG 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.