BIZTRAC BETA
Wholesale of machine tools

SANERINGSVAREHUSET AS

Org. no. 921217765 Limited company (AS) Øvre Eiker Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK −60,000
Equity NOK 524,000
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−60k kr).

SANERINGSVAREHUSET AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 921217765. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Engroshandel med maskinverktøy og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK −60,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK −60,000
Equity
NOK 524,000
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns SANERINGSVAREHUSET AS?

ALRON CHEMICAL CO AB
SANERINGSVAREHUSET AS
NOK 4.6m rev. · NOK −60,000 profit

SANERINGSVAREHUSET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANERINGSVAREHUSET AS

Who owns SANERINGSVAREHUSET AS?

ALRON CHEMICAL CO AB is the largest registered owner, with 100.0%.

What is the revenue of SANERINGSVAREHUSET AS?

SANERINGSVAREHUSET AS had revenue of NOK 4.6m in 2025.

Who is the general manager of SANERINGSVAREHUSET AS?

Jan Erik Nicolai Aamundsen is registered as general manager of SANERINGSVAREHUSET AS.

Where is SANERINGSVAREHUSET AS based?

SANERINGSVAREHUSET AS has its business address in Hokksund.

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.