BIZTRAC BETA
Buying and selling of own real estate

MITTEGETLOKALE VESTLAND AS

Org. no. 923956239 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 30.3m
Operating profit NOK 6.2m
Equity NOK 5.2m
Incorporated 2019
Share capital NOK 749,000

MITTEGETLOKALE VESTLAND AS is registered as a limited company in Bergen, Vestland with organisation number 923956239. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 749,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av eiendom, utvikling, drift og utleie av eiendom mv. og produkter/tjenester som naturlig hører sammen med dette. I tillegg deltakelse i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 30.3m in revenue and NOK 6.2m in operating profit.

Key figures · 2024

Revenue
NOK 30.3m
Operating profit
NOK 6.2m
Equity
NOK 5.2m
Est. value
NOK 17.8m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.6%
Good
Equity as a share of total capital

Who owns MITTEGETLOKALE VESTLAND AS?

KOMET AS
MITTEGETLOKALE VESTLAND AS
NOK 30.3m rev. · NOK 6.2m profit

MITTEGETLOKALE VESTLAND AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MITTEGETLOKALE VESTLAND AS

Who owns MITTEGETLOKALE VESTLAND AS?

KOMET AS is the largest registered owner, with 33.3%.

What is the revenue of MITTEGETLOKALE VESTLAND AS?

MITTEGETLOKALE VESTLAND AS had revenue of NOK 30.3m in 2024.

Where is MITTEGETLOKALE VESTLAND AS based?

MITTEGETLOKALE VESTLAND 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.