biztrac. BETA
COMPANY REGISTER PROFILE
924634901 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

LÅSMESTER VEST AS

Org. no. 924634901 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 880,000
Equity NOK 2.5m
Incorporated 2020
Share capital NOK 60,000

LÅSMESTER VEST AS is registered as a limited company in Bergen, Vestland with organisation number 924634901. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, drift, utleie og utvikling av eiendom. Det er anledning til å delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 880,000 in operating profit.

Former names: LÅSSENTERET MARVIK AS

Key figures · 2025

Revenue
NOK 1.5m
▲ +64 %
Operating profit
NOK 880,000
▲ +77 %
Equity
NOK 2.5m
▼ −8 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
6.30
Very good
Current assets ÷ current liabilities
Profitability
4.7%
Weak
Return on total assets
Solidity
13.5%
Satisfactory
Equity as a share of total capital

Who owns LÅSMESTER VEST AS?

LÅSMESTER VEST AS
NOK 1.5m rev. · NOK 880,000 profit

LÅSMESTER VEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LÅSMESTER VEST AS

Who owns LÅSMESTER VEST AS?

VUGGA INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of LÅSMESTER VEST AS?

LÅSMESTER VEST AS had revenue of NOK 1.5m in 2025.

Who is the general manager of LÅSMESTER VEST AS?

Roy Håkon Bakke is registered as general manager of LÅSMESTER VEST AS.

Where is LÅSMESTER VEST AS based?

LÅSMESTER VEST AS has its business address in Nesttun.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.