BIZTRAC BETA
Sports and recreation education

SPORTY TRENING AS

Org. no. 914211603 Limited company (AS) Asker Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 12,000
Equity NOK −7,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).

SPORTY TRENING AS is registered as a limited company in Asker, Akershus with organisation number 914211603. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Trening, helse og fysioterapi og alt som hører naturlig innen dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 12,000
Equity
NOK −7,000
Est. value
NOK 97,000

Financial health · 2025

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

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

Who owns SPORTY TRENING AS?

GURO KRISTINE RAASTAD
SPORTY TRENING AS
NOK 1.0m rev. · NOK 12,000 profit

SPORTY TRENING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPORTY TRENING AS

Who owns SPORTY TRENING AS?

GURO KRISTINE RAASTAD is the largest registered owner, with 66.0%.

What is the revenue of SPORTY TRENING AS?

SPORTY TRENING AS had revenue of NOK 1.0m in 2025.

Who is the general manager of SPORTY TRENING AS?

Guro Kristine Raastad is registered as general manager of SPORTY TRENING AS.

Where is SPORTY TRENING AS based?

SPORTY TRENING AS has its business address in Spikkestad.

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.