BIZTRAC BETA
Retail sale of sports equipment

HAGSTRØM MOTORSPORT AS

Org. no. 815795342 Limited company (AS) Nes Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 516,000
Operating profit NOK 310
Equity NOK 10,000
Incorporated 2015
Share capital NOK 30,000

HAGSTRØM MOTORSPORT AS is registered as a limited company in Nes, Akershus with organisation number 815795342. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tilpassing/montering av styling/tuningprodukter. Import/salg med bil/racing relaterte produkter, samt utleie av utstyr til motorsport.”. The most recent filed accounts, for the 2025 financial year, show NOK 516,000 in revenue and NOK 310 in operating profit.

Key figures · 2025

Revenue
NOK 516,000
Operating profit
NOK 310
Equity
NOK 10,000
Est. value
NOK 6,000

Financial health · 2025

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

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

Who owns HAGSTRØM MOTORSPORT AS?

ANDERS HAGSTRØM
HAGSTRØM MOTORSPORT AS
NOK 516,000 rev. · NOK 310 profit

HAGSTRØM MOTORSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAGSTRØM MOTORSPORT AS

Who owns HAGSTRØM MOTORSPORT AS?

ANDERS HAGSTRØM is the largest registered owner, with 100.0%.

What is the revenue of HAGSTRØM MOTORSPORT AS?

HAGSTRØM MOTORSPORT AS had revenue of NOK 516,000 in 2025.

Who is the general manager of HAGSTRØM MOTORSPORT AS?

Anders Hagstrøm is registered as general manager of HAGSTRØM MOTORSPORT AS.

Where is HAGSTRØM MOTORSPORT AS based?

HAGSTRØM MOTORSPORT AS has its business address in Oppaker.

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.