BIZTRAC BETA
Wholesale of clothing and footwear

SPARXWEAR AS

Org. no. 930954128 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 199,000
Operating profit NOK −192,000
Equity NOK −137,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−137k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−192k kr).

SPARXWEAR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930954128. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen klær og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet. I tillegg utføres konsulenttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 199,000 in revenue and NOK −192,000 in operating profit.

Key figures · 2024

Revenue
NOK 199,000
Operating profit
NOK −192,000
Equity
NOK −137,000

Financial health · 2024

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

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

Who owns SPARXWEAR AS?

ALEKSANDER RATHE
SPARXWEAR AS
NOK 199,000 rev. · NOK −192,000 profit

SPARXWEAR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPARXWEAR AS

Who owns SPARXWEAR AS?

ALEKSANDER RATHE is the largest registered owner, with 50.0%.

What is the revenue of SPARXWEAR AS?

SPARXWEAR AS had revenue of NOK 199,000 in 2024.

Where is SPARXWEAR AS based?

SPARXWEAR AS has its business address in Bosberg.

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.