BIZTRAC BETA
COMPANY REGISTER PROFILE
936745318 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Motion picture, video and television programme production activities

SPORTSHISTORIER AS

Org. no. 936745318 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-19.

SPORTSHISTORIER AS is registered as a limited company in Oslo, Oslo with organisation number 936745318. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Formidling av journalistikk, sportshistorier, øyeblikk og levere underholdningstjenester tilpasset flere plattformer - være seg på TV, radio og sosiale medier.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 24,000
Est. value
NOK 43,000

Financial health · 2025

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

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

Who owns SPORTSHISTORIER AS?

VEGARD AULSTAD
SPORTSHISTORIER AS
· NOK −7,000 profit

SPORTSHISTORIER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPORTSHISTORIER AS

Who owns SPORTSHISTORIER AS?

VEGARD AULSTAD is the largest registered owner, with 100.0%.

Who is the general manager of SPORTSHISTORIER AS?

Vegard Aulstad is registered as general manager of SPORTSHISTORIER AS.

Where is SPORTSHISTORIER AS based?

SPORTSHISTORIER AS has its business address in Oslo.

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.