BIZTRAC BETA
Rental and operating of own or leased real estate

SNØ VINTERARENA AS

Org. no. 830368892 Limited company (AS) Lørenskog Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK −4.5m
Equity NOK 107.1m
Incorporated 2022
Share capital NOK 2.1m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,5 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SNØ VINTERARENA AS is registered as a limited company in Lørenskog, Akershus with organisation number 830368892. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 2.1m, divided into 2077126 shares. The company's stated purpose is: “Eie, drive og leie ut selskapets eiendom, samt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK −4.5m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK −4.5m
Equity
NOK 107.1m
Est. value
NOK 75.6m

Financial health · 2024

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

Who owns SNØ VINTERARENA AS?

SNØ OSLO HOLDING AS
SNØ VINTERARENA AS
NOK 1.8m rev. · NOK −4.5m profit

SNØ VINTERARENA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNØ VINTERARENA AS

Who owns SNØ VINTERARENA AS?

SNØ OSLO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SNØ VINTERARENA AS?

SNØ VINTERARENA AS had revenue of NOK 1.8m in 2024.

Where is SNØ VINTERARENA AS based?

SNØ VINTERARENA AS has its business address in Lørenskog.

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.