BIZTRAC BETA
Activities of fitness centres

TEAM SKI PROJECT AS

Org. no. 935272270 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 267,000
Operating profit NOK −133,000
Equity NOK 257,000
Incorporated 2025
Share capital NOK 310,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−133k kr).

TEAM SKI PROJECT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 935272270. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2025. Registered share capital is NOK 310,000, divided into 100000 shares. The company's stated purpose is: “Utvikle utøvere innen langrenn og skiskyting med den målsetning at utøvere når sitt maksimale nivå.”. The most recent filed accounts, for the 2025 financial year, show NOK 267,000 in revenue and NOK −133,000 in operating profit.

Key figures · 2025

Revenue
NOK 267,000
Operating profit
NOK −133,000
Equity
NOK 257,000
Est. value
NOK 322,000

Financial health · 2025

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

Who owns TEAM SKI PROJECT AS?

SVENN-ARNE NORDHEIM
TEAM SKI PROJECT AS
NOK 267,000 rev. · NOK −133,000 profit

TEAM SKI PROJECT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEAM SKI PROJECT AS

Who owns TEAM SKI PROJECT AS?

SVENN-ARNE NORDHEIM is the largest registered owner, with 34.0%.

What is the revenue of TEAM SKI PROJECT AS?

TEAM SKI PROJECT AS had revenue of NOK 267,000 in 2025.

Who is the general manager of TEAM SKI PROJECT AS?

Svenn-Arne Nordheim is registered as general manager of TEAM SKI PROJECT AS.

Where is TEAM SKI PROJECT AS based?

TEAM SKI PROJECT AS has its business address in Frogner.

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.