BIZTRAC BETA
Wholesale of motor vehicle parts and accessories

THERMOWIPER NORWAY AS

Org. no. 998774047 Limited company (AS) Nome Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 570,000
Operating profit NOK −303,000
Equity NOK 423,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−303k kr).

THERMOWIPER NORWAY AS is registered as a limited company in Nome, Telemark with organisation number 998774047. The business is classified under wholesale of motor vehicle parts and accessories (NACE 46.720). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Varehandel, import og bilreparasjoner.”. The most recent filed accounts, for the 2024 financial year, show NOK 570,000 in revenue and NOK −303,000 in operating profit.

Key figures · 2024

Revenue
NOK 570,000
Operating profit
NOK −303,000
Equity
NOK 423,000
Est. value
NOK 386,000

Financial health · 2024

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

Who owns THERMOWIPER NORWAY AS?

OLE EDVIN STOA
THERMOWIPER NORWAY AS
NOK 570,000 rev. · NOK −303,000 profit

THERMOWIPER NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THERMOWIPER NORWAY AS

Who owns THERMOWIPER NORWAY AS?

OLE EDVIN STOA is the largest registered owner, with 100.0%.

What is the revenue of THERMOWIPER NORWAY AS?

THERMOWIPER NORWAY AS had revenue of NOK 570,000 in 2024.

Who is the general manager of THERMOWIPER NORWAY AS?

Ole Edvin Stoa is registered as general manager of THERMOWIPER NORWAY AS.

Where is THERMOWIPER NORWAY AS based?

THERMOWIPER NORWAY AS has its business address in Ulefoss.

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.