BIZTRAC BETA
Manufacture of locks and hinges

VELO LÅS & BESLAG AS

Org. no. 997218442 Limited company (AS) Sortland Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 344,000
Equity NOK 885,000
Incorporated 2011
Share capital NOK 300,000

VELO LÅS & BESLAG AS is registered as a limited company in Sortland, Nordland with organisation number 997218442. The business is classified under manufacture of locks and hinges (NACE 25.620). The company was incorporated in 2011. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Alt innen lås og beslag og det som naturlig måtte ligge innunder dette for bygg, anlegg og det private marked, samt salg av varer og tjenester i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 344,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 344,000
Equity
NOK 885,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
3.50
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.3%
Good
Equity as a share of total capital

Who owns VELO LÅS & BESLAG AS?

BK LARSEN EIENDOM AS
VELO LÅS & BESLAG AS
NOK 4.1m rev. · NOK 344,000 profit

VELO LÅS & BESLAG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VELO LÅS & BESLAG AS

Who owns VELO LÅS & BESLAG AS?

BK LARSEN EIENDOM AS is the largest registered owner, with 97.0%.

What is the revenue of VELO LÅS & BESLAG AS?

VELO LÅS & BESLAG AS had revenue of NOK 4.1m in 2024.

Who is the general manager of VELO LÅS & BESLAG AS?

Bob Kenny Larsen is registered as general manager of VELO LÅS & BESLAG AS.

Where is VELO LÅS & BESLAG AS based?

VELO LÅS & BESLAG AS has its business address in Sortland.

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.