BIZTRAC BETA
Manufacture of locks and hinges

LÅS1 SIKKERHET AS

Org. no. 916970897 Limited company (AS) Lørenskog Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 10.6m
Operating profit NOK 530,000
Equity NOK 3.1m
Incorporated 2016
Employees 5
Share capital NOK 30,000

Signals

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

LÅS1 SIKKERHET AS is registered as a limited company in Lørenskog, Akershus with organisation number 916970897. The business is classified under manufacture of locks and hinges (NACE 25.620). The company was incorporated in 2016 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Alt innen lås og sikkerhet samt alt hva som her står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.6m in revenue and NOK 530,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.6m
Operating profit
NOK 530,000
Equity
NOK 3.1m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns LÅS1 SIKKERHET AS?

ROLIN AS
LÅS1 SIKKERHET AS
NOK 10.6m rev. · NOK 530,000 profit

LÅS1 SIKKERHET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LÅS1 SIKKERHET AS

Who owns LÅS1 SIKKERHET AS?

ROLIN AS is the largest registered owner, with 100.0%.

What is the revenue of LÅS1 SIKKERHET AS?

LÅS1 SIKKERHET AS had revenue of NOK 10.6m in 2024.

Who is the general manager of LÅS1 SIKKERHET AS?

Linda Riediger is registered as general manager of LÅS1 SIKKERHET AS.

Where is LÅS1 SIKKERHET AS based?

LÅS1 SIKKERHET AS has its business address in Lørenskog.

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.