BIZTRAC BETA
Manufacture of locks and hinges

LÅSESMEDEN TROMSØ AS

Org. no. 994193872 Limited company (AS) Tromsø Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 46.6m
Operating profit NOK 11.2m
Equity NOK 22.8m
Incorporated 2009
Employees 22
Share capital NOK 100,000

LÅSESMEDEN TROMSØ AS is registered as a limited company in Tromsø, Troms with organisation number 994193872. The business is classified under manufacture of locks and hinges (NACE 25.620). The company was incorporated in 2009 and has 22 registered employees. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Produksjon, salg, montasje og service på låser, nøkler, beslag og andre nærliggende produkter samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 46.6m in revenue and NOK 11.2m in operating profit.

Key figures · 2024

Revenue
NOK 46.6m
Operating profit
NOK 11.2m
Equity
NOK 22.8m
Est. value
NOK 48.4m

Financial health · 2024

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

Who owns LÅSESMEDEN TROMSØ AS?

PROSERO SECURITY AS
LÅSESMEDEN TROMSØ AS
NOK 46.6m rev. · NOK 11.2m profit

LÅSESMEDEN TROMSØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LÅSESMEDEN TROMSØ AS

Who owns LÅSESMEDEN TROMSØ AS?

PROSERO SECURITY AS is the largest registered owner, with 100.0%.

What is the revenue of LÅSESMEDEN TROMSØ AS?

LÅSESMEDEN TROMSØ AS had revenue of NOK 46.6m in 2024.

Who is the general manager of LÅSESMEDEN TROMSØ AS?

Thomas Kirkenes Henriksen-Aamot is registered as general manager of LÅSESMEDEN TROMSØ AS.

Where is LÅSESMEDEN TROMSØ AS based?

LÅSESMEDEN TROMSØ AS has its business address in Tromsø.

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.