BIZTRAC BETA
Industrial product and fashion design activities

STEPLOCK NORWAY AS

Org. no. 921136153 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 184.4m
Operating profit NOK 21.8m
Equity NOK 20.0m
Incorporated 2018
Employees 12
Share capital NOK 30,000

STEPLOCK NORWAY AS is registered as a limited company in Drammen, Buskerud with organisation number 921136153. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2018 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produktutvikling innen låsesystemer, salg av låser og tekniske konsultasjoner om brann- og eksplosjonsproblemer og relaterte aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 184.4m in revenue and NOK 21.8m in operating profit.

Key figures · 2025

Revenue
NOK 184.4m
Operating profit
NOK 21.8m
Equity
NOK 20.0m
Est. value
NOK 118.7m

Financial health · 2025

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

Who owns STEPLOCK NORWAY AS?

STEAB FRVALTNING AB
STEPLOCK NORWAY AS
NOK 184.4m rev. · NOK 21.8m profit

STEPLOCK NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEPLOCK NORWAY AS

Who owns STEPLOCK NORWAY AS?

STEAB FRVALTNING AB is the largest registered owner, with 100.0%.

What is the revenue of STEPLOCK NORWAY AS?

STEPLOCK NORWAY AS had revenue of NOK 184.4m in 2025.

Who is the general manager of STEPLOCK NORWAY AS?

Anders Møller is registered as general manager of STEPLOCK NORWAY AS.

Where is STEPLOCK NORWAY AS based?

STEPLOCK NORWAY AS has its business address in Drammen.

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.