BIZTRAC BETA
Activities of advertising agencies

SPORT CONNECT AS

Org. no. 998778948 Limited company (AS) Hemsedal Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 127,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

SPORT CONNECT AS is registered as a limited company in Hemsedal, Buskerud with organisation number 998778948. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av markedsføringstjenester, sponsorvirksomhet, samt virksomhet i relasjon til dette, herunder kjøp og salg av tilknyttede markedsrettigheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 127,000
Est. value
NOK 207,000

Financial health · 2024

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

Who owns SPORT CONNECT AS?

ØYSTEIN SANDSTRØM MOEN
SPORT CONNECT AS
NOK 0 rev. · NOK −3,000 profit

SPORT CONNECT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPORT CONNECT AS

Who owns SPORT CONNECT AS?

ØYSTEIN SANDSTRØM MOEN is the largest registered owner, with 100.0%.

What is the revenue of SPORT CONNECT AS?

SPORT CONNECT AS had revenue of NOK 0 in 2024.

Who is the general manager of SPORT CONNECT AS?

Øystein Sandstrøm Moen is registered as general manager of SPORT CONNECT AS.

Where is SPORT CONNECT AS based?

SPORT CONNECT AS has its business address in Hemsedal.

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.