BIZTRAC BETA
Other tour operator activities

STEGANE SPORT AS

Org. no. 998584035 Limited company (AS) Sigdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK −780,000
Equity NOK 3.0m
Incorporated 2012
Share capital NOK 100,000

Signals

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

STEGANE SPORT AS is registered as a limited company in Sigdal, Buskerud with organisation number 998584035. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Reisevirksomhet, sports- og publikumreiser. Arrangør av publikumsturer til store sportsbegivenheter i utlandet. Annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK −780,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK −780,000
Equity
NOK 3.0m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns STEGANE SPORT AS?

RUNOLV STEGANE
STEGANE SPORT AS
NOK 5.0m rev. · NOK −780,000 profit

STEGANE SPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEGANE SPORT AS

Who owns STEGANE SPORT AS?

RUNOLV STEGANE is the largest registered owner, with 100.0%.

What is the revenue of STEGANE SPORT AS?

STEGANE SPORT AS had revenue of NOK 5.0m in 2025.

Who is the general manager of STEGANE SPORT AS?

Runolv Stegane is registered as general manager of STEGANE SPORT AS.

Where is STEGANE SPORT AS based?

STEGANE SPORT AS has its business address in Prestfoss.

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.