BIZTRAC BETA
Wholesale of other machinery and equipment

PARLOCK AS

Org. no. 927057093 Limited company (AS) Øvre Eiker Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 26.4m
Operating profit NOK 4.8m
Equity NOK 8.4m
Incorporated 2021
Share capital NOK 270,000

Signals

1 flags
  • Nylig endring 2026-03-09 Adresseendring registrert 2026-03-09.

PARLOCK AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 927057093. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2021. Registered share capital is NOK 270,000, divided into 15900 shares. The company's stated purpose is: “Produksjon, handels- og agenturvirksomhet innen ventilasjonsprodukter og frekvensomformere og hva dermed står i forbindelse, samt ved kjøp av aksjer eller på annen måte å delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.4m in revenue and NOK 4.8m in operating profit.

Key figures · 2024

Revenue
NOK 26.4m
Operating profit
NOK 4.8m
Equity
NOK 8.4m
Est. value
NOK 20.7m

Financial health · 2024

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

Who owns PARLOCK AS?

SOLER & PALAU VENTILATION GROUP
PARLOCK AS
NOK 26.4m rev. · NOK 4.8m profit

PARLOCK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PARLOCK AS

Who owns PARLOCK AS?

SOLER & PALAU VENTILATION GROUP is the largest registered owner, with 75.2%.

What is the revenue of PARLOCK AS?

PARLOCK AS had revenue of NOK 26.4m in 2024.

Who is the general manager of PARLOCK AS?

Tor Espen Lie is registered as general manager of PARLOCK AS.

Where is PARLOCK AS based?

PARLOCK AS has its business address in Fiskum.

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.