BIZTRAC BETA
Wholesale of other household goods

SMI SNOW MAKERS AS

Org. no. 982305934 Limited company (AS) Drammen Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 10.3m
Operating profit NOK −877,000
Equity NOK 3.6m
Incorporated 2000
Share capital NOK 100,000

Signals

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

SMI SNOW MAKERS AS is registered as a limited company in Drammen, Buskerud with organisation number 982305934. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Import og salg av utstyr til sportsanlegg, konsulent og ingeniørtjenester, service og tilhørende delleveranser samt investering i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.3m in revenue and NOK −877,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.3m
Operating profit
NOK −877,000
Equity
NOK 3.6m
Est. value
NOK 5.1m

Financial health · 2025

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

Who owns SMI SNOW MAKERS AS?

KRISTOFER TANBERG
SMI SNOW MAKERS AS
NOK 10.3m rev. · NOK −877,000 profit

SMI SNOW MAKERS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMI SNOW MAKERS AS

Who owns SMI SNOW MAKERS AS?

KRISTOFER TANBERG is the largest registered owner, with 100.0%.

What is the revenue of SMI SNOW MAKERS AS?

SMI SNOW MAKERS AS had revenue of NOK 10.3m in 2025.

Who is the general manager of SMI SNOW MAKERS AS?

Kristofer Tanberg is registered as general manager of SMI SNOW MAKERS AS.

Where is SMI SNOW MAKERS AS based?

SMI SNOW MAKERS AS has its business address in Drammen.

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.