BIZTRAC BETA
Wholesale of hardware, plumbing and heating equipment and supplies

SPARMAX AS

Org. no. 892878862 Limited company (AS) Ringerike Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 108.9m
Operating profit NOK −1.9m
Equity NOK 29.6m
Incorporated 2008
Employees 28
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,9 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SPARMAX AS is registered as a limited company in Ringerike, Buskerud with organisation number 892878862. The business is classified under wholesale of hardware, plumbing and heating equipment and supplies (NACE 46.840). The company was incorporated in 2008 and has 28 registered employees. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er import og salg av møbler, interiør, baderom og velværeprodukter.”. The most recent filed accounts, for the 2024 financial year, show NOK 108.9m in revenue and NOK −1.9m in operating profit.

Key figures · 2024

Revenue
NOK 108.9m
Operating profit
NOK −1.9m
Equity
NOK 29.6m
Est. value
NOK 49.2m

Financial health · 2024

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

Who owns SPARMAX AS?

SPARMAX HOLDING AS
SPARMAX AS
NOK 108.9m rev. · NOK −1.9m profit

SPARMAX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPARMAX AS

Who owns SPARMAX AS?

SPARMAX HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SPARMAX AS?

SPARMAX AS had revenue of NOK 108.9m in 2024.

Where is SPARMAX AS based?

SPARMAX 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.