biztrac. BETA
COMPANY REGISTER PROFILE
922089825 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of hardware, building materials, paints and glass

PROLOCK AS

Org. no. 922089825 Limited company (AS) Bærum Incorporated 2018 Active
Revenue 2025 NOK 1.3m
Operating profit NOK 475,000
Equity NOK 989,000
Incorporated 2018
Share capital NOK 300,000

PROLOCK AS is registered as a limited company in Bærum, Akershus with organisation number 922089825. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2018. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av låser og maskiner. Kjøp og salg av aksjer, verdipapirer og andre formuesverdier av enhver art. Deltagelse i og finansiering av andre forretningsforetagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 475,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▼ −39 %
Operating profit
NOK 475,000
▲ +10 %
Equity
NOK 989,000
▲ +59 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
15.32
Very good
Current assets ÷ current liabilities
Profitability
21.8%
Very good
Return on total assets
Solidity
49.5%
Very good
Equity as a share of total capital

Who owns PROLOCK AS?

PROLOCK AS
NOK 1.3m rev. · NOK 475,000 profit

PROLOCK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROLOCK AS

Who owns PROLOCK AS?

Svein Inge Myhre is the largest registered owner, with 100.0%.

What is the revenue of PROLOCK AS?

PROLOCK AS had revenue of NOK 1.3m in 2025.

Who is the general manager of PROLOCK AS?

Svein Inge Myhre is registered as general manager of PROLOCK AS.

Where is PROLOCK AS based?

PROLOCK AS has its business address in Rud.

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.