BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

PARKETTGRUPPEN AS

Org. no. 888348972 Limited company (AS) Karmøy Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 76.2m
Operating profit NOK 2.0m
Equity NOK 8.1m
Incorporated 2005
Employees 34
Share capital NOK 660,000

PARKETTGRUPPEN AS is registered as a limited company in Karmøy, Rogaland with organisation number 888348972. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2005 and has 34 registered employees. Registered share capital is NOK 660,000, divided into 660 shares. The company's stated purpose is: “Import, salg og legging av parkett samt dertil hørende virksomhet, herunder også deltagelse i selskaper som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 76.2m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 76.2m
Operating profit
NOK 2.0m
Equity
NOK 8.1m
Est. value
NOK 11.4m

Financial health · 2025

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

Who owns PARKETTGRUPPEN AS?

BRØDRENE OLSEN INVEST AS
PARKETTGRUPPEN AS
NOK 76.2m rev. · NOK 2.0m profit

PARKETTGRUPPEN AS has 4 registered shareholders:

All shareholders and roles →

Which companies does PARKETTGRUPPEN AS own?

PARKETTGRUPPEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PARKETTGRUPPEN AS

Who owns PARKETTGRUPPEN AS?

BRØDRENE OLSEN INVEST AS is the largest registered owner, with 31.4%.

What is the revenue of PARKETTGRUPPEN AS?

PARKETTGRUPPEN AS had revenue of NOK 76.2m in 2025.

Where is PARKETTGRUPPEN AS based?

PARKETTGRUPPEN AS has its business address in Kopervik.

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.