BIZTRAC BETA
Manufacture of plastic plates, sheets, tubes and profiles

HALLINGPLAST AS

Org. no. 919522461 Limited company (AS) Hol Incorporated 1977 Active
Ownership graph ↗
Revenue 2024 NOK 774.1m
Operating profit NOK 14.7m
Equity NOK 231.9m
Incorporated 1977
Employees 114
Share capital NOK 5.0m

HALLINGPLAST AS is registered as a limited company in Hol, Buskerud with organisation number 919522461. The business is classified under manufacture of plastic plates, sheets, tubes and profiles (NACE 22.210). The company was incorporated in 1977 and has 114 registered employees. Registered share capital is NOK 5.0m, divided into 1000 shares. The company's stated purpose is: “Produksjon og handel av rør og rørdeler av plastmaterialer. ”. The most recent filed accounts, for the 2024 financial year, show NOK 774.1m in revenue and NOK 14.7m in operating profit.

Key figures · 2024

Revenue
NOK 774.1m
Operating profit
NOK 14.7m
Equity
NOK 231.9m
Est. value
NOK 180.8m

Financial health · 2024

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

Who owns HALLINGPLAST AS?

HALLINGPLAST AS
HALLINGPLAST AS
NOK 774.1m rev. · NOK 14.7m profit

HALLINGPLAST AS has 8 registered shareholders:

All shareholders and roles →

Which companies does HALLINGPLAST AS own?

HALLINGPLAST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about HALLINGPLAST AS

Who owns HALLINGPLAST AS?

HALLINGPLAST AS is the largest registered owner, with 23.5%.

What is the revenue of HALLINGPLAST AS?

HALLINGPLAST AS had revenue of NOK 774.1m in 2024.

Who is the general manager of HALLINGPLAST AS?

Sverre Tragethon is registered as general manager of HALLINGPLAST AS.

Where is HALLINGPLAST AS based?

HALLINGPLAST AS has its business address in Ål.

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.