BIZTRAC BETA
Wholesale of other machinery and equipment

POLARDRIKK BUSKERUD AS

Org. no. 999150373 Limited company (AS) Drammen Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 33,000
Equity NOK 55,000
Incorporated 2012
Share capital NOK 30,000

POLARDRIKK BUSKERUD AS is registered as a limited company in Drammen, Buskerud with organisation number 999150373. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg og service av vannbehandlingsautomater og beslektede produkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 33,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 33,000
Equity
NOK 55,000
Est. value
NOK 152,000

Financial health · 2024

Liquidity
0.66
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns POLARDRIKK BUSKERUD AS?

OLE CHRISTIAN HÆGSTAD
POLARDRIKK BUSKERUD AS
NOK 2.4m rev. · NOK 33,000 profit

POLARDRIKK BUSKERUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POLARDRIKK BUSKERUD AS

Who owns POLARDRIKK BUSKERUD AS?

OLE CHRISTIAN HÆGSTAD is the largest registered owner, with 100.0%.

What is the revenue of POLARDRIKK BUSKERUD AS?

POLARDRIKK BUSKERUD AS had revenue of NOK 2.4m in 2024.

Who is the general manager of POLARDRIKK BUSKERUD AS?

Ole Christian Hægstad is registered as general manager of POLARDRIKK BUSKERUD AS.

Where is POLARDRIKK BUSKERUD AS based?

POLARDRIKK BUSKERUD AS has its business address in Solbergelva.

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.