BIZTRAC BETA
COMPANY REGISTER PROFILE
989538500 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Retail sale of sports equipment

SELBUSPORTEN HOLDING AS

Org. no. 989538500 Limited company (AS) Selbu Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 373,000
Incorporated 2005
Share capital NOK 200,000

Signals

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

SELBUSPORTEN HOLDING AS is registered as a limited company in Selbu, Trøndelag with organisation number 989538500. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Investering i andre selskaper, kjøp og salg av eiendommer, samt rådgivning og deltagelse i andre virksomheter. ”.

Key figures · 2025

Operating profit
NOK −18,000
▼ −91 %
Equity
NOK 373,000
▼ −31 %
Est. value
NOK 467,000

Financial health · 2025

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

Who owns SELBUSPORTEN HOLDING AS?

SELBUSPORTEN HOLDING AS
· NOK −18,000 profit

SELBUSPORTEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SELBUSPORTEN HOLDING AS own?

SELBUSPORTEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SELBUSPORTEN HOLDING AS

Who owns SELBUSPORTEN HOLDING AS?

OLE JOHAN ØYASÆTER is the largest registered owner, with 100.0%.

Who is the general manager of SELBUSPORTEN HOLDING AS?

Ole Johan Øyasæter is registered as general manager of SELBUSPORTEN HOLDING AS.

Where is SELBUSPORTEN HOLDING AS based?

SELBUSPORTEN HOLDING AS has its business address in Selbu.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.