BIZTRAC BETA
Plumbing installation

SPORTEK AS

Org. no. 935726328 Limited company (AS) Øygarden Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 85,000
Operating profit NOK −52,000
Equity NOK 41,000
Incorporated 2025
Share capital NOK 100,000

Signals

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

SPORTEK AS is registered as a limited company in Øygarden, Vestland with organisation number 935726328. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Selge varer og tjenester innen rørleggerarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 85,000 in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 85,000
Operating profit
NOK −52,000
Equity
NOK 41,000
Est. value
NOK 42,000

Financial health · 2025

Liquidity
5.82
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.3%
Weak
Equity as a share of total capital

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

Who owns SPORTEK AS?

JARLE AASEN TINGVOLL
SPORTEK AS
NOK 85,000 rev. · NOK −52,000 profit

SPORTEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPORTEK AS

Who owns SPORTEK AS?

JARLE AASEN TINGVOLL is the largest registered owner, with 100.0%.

What is the revenue of SPORTEK AS?

SPORTEK AS had revenue of NOK 85,000 in 2025.

Who is the general manager of SPORTEK AS?

Jarle Aasen Tingvoll is registered as general manager of SPORTEK AS.

Where is SPORTEK AS based?

SPORTEK AS has its business address in Skogsvåg.

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.