BIZTRAC BETA
Activities of agents involved in the wholesale of timber and building materials

UNILIN NORWAY AS

Org. no. 918119361 Limited company (AS) Ringerike Incorporated 1974 Active
Ownership graph ↗
Revenue 2024 NOK 21.4m
Operating profit NOK 1.0m
Equity NOK 7.5m
Incorporated 1974
Employees 11
Share capital NOK 62,000

UNILIN NORWAY AS is registered as a limited company in Ringerike, Buskerud with organisation number 918119361. The business is classified under activities of agents involved in the wholesale of timber and building materials (NACE 46.130). The company was incorporated in 1974 and has 11 registered employees. Registered share capital is NOK 62,000, divided into 15500 shares. The company's stated purpose is: “Handel, derunder import og eksport, industri, agenturvirksomhet og forhold som har sammenheng med dette. ”. The most recent filed accounts, for the 2024 financial year, show NOK 21.4m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 21.4m
Operating profit
NOK 1.0m
Equity
NOK 7.5m
Est. value
NOK 8.2m

Financial health · 2024

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

Who owns UNILIN NORWAY AS?

PERGO HOLDING BV
UNILIN NORWAY AS
NOK 21.4m rev. · NOK 1.0m profit

UNILIN NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNILIN NORWAY AS

Who owns UNILIN NORWAY AS?

PERGO HOLDING BV is the largest registered owner, with 100.0%.

What is the revenue of UNILIN NORWAY AS?

UNILIN NORWAY AS had revenue of NOK 21.4m in 2024.

Who is the general manager of UNILIN NORWAY AS?

John Magne Pedersen is registered as general manager of UNILIN NORWAY AS.

Where is UNILIN NORWAY AS based?

UNILIN NORWAY AS has its business address in Hønefoss.

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.