BIZTRAC BETA
Wholesale of other machinery and equipment

POLARDRIKK TRONDHEIM AS

Org. no. 917461333 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 10.7m
Operating profit NOK 422,000
Equity NOK 2.2m
Incorporated 2016
Employees 5
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

POLARDRIKK TRONDHEIM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917461333. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2016 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av vannbehandlingsautomater, kaffemaskiner og beslektede produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.7m in revenue and NOK 422,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.7m
Operating profit
NOK 422,000
Equity
NOK 2.2m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns POLARDRIKK TRONDHEIM AS?

POLARDRIKK GRUPPEN AS
POLARDRIKK TRONDHEIM AS
NOK 10.7m rev. · NOK 422,000 profit

POLARDRIKK TRONDHEIM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about POLARDRIKK TRONDHEIM AS

Who owns POLARDRIKK TRONDHEIM AS?

POLARDRIKK GRUPPEN AS is the largest registered owner, with 51.0%.

What is the revenue of POLARDRIKK TRONDHEIM AS?

POLARDRIKK TRONDHEIM AS had revenue of NOK 10.7m in 2025.

Where is POLARDRIKK TRONDHEIM AS based?

POLARDRIKK TRONDHEIM AS has its business address in Tiller.

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.