BIZTRAC BETA
Wholesale of motor vehicle parts and accessories

SNOW BLOWER CAR PRODUCTS AS

Org. no. 821462452 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 203,000
Operating profit NOK −17,000
Equity NOK 54,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

SNOW BLOWER CAR PRODUCTS AS is registered as a limited company in Oslo, Oslo with organisation number 821462452. The business is classified under wholesale of motor vehicle parts and accessories (NACE 46.720). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Importere varer fra Kina for salg til grossister.”. The most recent filed accounts, for the 2025 financial year, show NOK 203,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 203,000
Operating profit
NOK −17,000
Equity
NOK 54,000
Est. value
NOK 91,000

Financial health · 2025

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

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

Who owns SNOW BLOWER CAR PRODUCTS AS?

KJETIL SINNES GAUSLAA
SNOW BLOWER CAR PRODUCTS AS
NOK 203,000 rev. · NOK −17,000 profit

SNOW BLOWER CAR PRODUCTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNOW BLOWER CAR PRODUCTS AS

Who owns SNOW BLOWER CAR PRODUCTS AS?

KJETIL SINNES GAUSLAA is the largest registered owner, with 100.0%.

What is the revenue of SNOW BLOWER CAR PRODUCTS AS?

SNOW BLOWER CAR PRODUCTS AS had revenue of NOK 203,000 in 2025.

Where is SNOW BLOWER CAR PRODUCTS AS based?

SNOW BLOWER CAR PRODUCTS AS has its business address in Oslo.

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.