BIZTRAC BETA
Rental and operating of own or leased real estate

VESTRE LINDHAUGEN AS

Org. no. 922229376 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK 2.6m
Equity NOK 6.8m
Incorporated 2019
Share capital NOK 5.0m

Signals

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

VESTRE LINDHAUGEN AS is registered as a limited company in Bergen, Vestland with organisation number 922229376. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 5.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, leie, drift og annen utvikling av eiendom og annen virksomhet som faller naturlig sammen med dette, samt deltakelse i selskaper med tilsvarende virksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 2.6m in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
Operating profit
NOK 2.6m
Equity
NOK 6.8m
Est. value
NOK 7.5m

Financial health · 2025

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

Who owns VESTRE LINDHAUGEN AS?

EGD NÆRING AS
VESTRE LINDHAUGEN AS
NOK 4.9m rev. · NOK 2.6m profit

VESTRE LINDHAUGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTRE LINDHAUGEN AS

Who owns VESTRE LINDHAUGEN AS?

EGD NÆRING AS is the largest registered owner, with 100.0%.

What is the revenue of VESTRE LINDHAUGEN AS?

VESTRE LINDHAUGEN AS had revenue of NOK 4.9m in 2025.

Where is VESTRE LINDHAUGEN AS based?

VESTRE LINDHAUGEN AS has its business address in Bergen.

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.