BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

PROLAKK AS

Org. no. 917677182 Limited company (AS) Molde Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 14.8m
Operating profit NOK 575,000
Equity NOK 1.5m
Incorporated 2016
Share capital NOK 30,000

PROLAKK AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 917677182. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg og omsetning av malervarer, billakk og tilbehør, samt alt som står i forbindelse med dette, herunder deltagelse i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.8m in revenue and NOK 575,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.8m
Operating profit
NOK 575,000
Equity
NOK 1.5m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns PROLAKK AS?

FRODE WIIG RØBERG
PROLAKK AS
NOK 14.8m rev. · NOK 575,000 profit

PROLAKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PROLAKK AS own?

PROLAKK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PROLAKK AS

Who owns PROLAKK AS?

FRODE WIIG RØBERG is the largest registered owner, with 100.0%.

What is the revenue of PROLAKK AS?

PROLAKK AS had revenue of NOK 14.8m in 2025.

Who is the general manager of PROLAKK AS?

Frode Wiig Røberg is registered as general manager of PROLAKK AS.

Where is PROLAKK AS based?

PROLAKK AS has its business address in Molde.

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.