BIZTRAC BETA
Retail sale of sports equipment

TRENINGSPARK1 AS

Org. no. 917352631 Limited company (AS) Bjerkreim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 185,000
Equity NOK 240,000
Incorporated 2016
Share capital NOK 30,000

TRENINGSPARK1 AS is registered as a limited company in Bjerkreim, Rogaland with organisation number 917352631. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av treningsutstyr, treningsparker, Crossfit rigger, Calisthenics rigger, Parkour parker, Street Workout parker, ballbinger, klatrevegger, buldrervegger, buldrestein og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 185,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 185,000
Equity
NOK 240,000
Est. value
NOK 758,000

Financial health · 2025

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

Who owns TRENINGSPARK1 AS?

LARS MORTEN SANDE TOFTEVÅG
TRENINGSPARK1 AS
NOK 2.1m rev. · NOK 185,000 profit

TRENINGSPARK1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRENINGSPARK1 AS

Who owns TRENINGSPARK1 AS?

LARS MORTEN SANDE TOFTEVÅG is the largest registered owner, with 100.0%.

What is the revenue of TRENINGSPARK1 AS?

TRENINGSPARK1 AS had revenue of NOK 2.1m in 2025.

Who is the general manager of TRENINGSPARK1 AS?

Lars Morten Sande Toftevåg is registered as general manager of TRENINGSPARK1 AS.

Where is TRENINGSPARK1 AS based?

TRENINGSPARK1 AS has its business address in Bjerkreim.

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.