biztrac. BETA
COMPANY REGISTER PROFILE
830368892 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
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 2025 NOK 1.8m
Operating profit NOK −5.3m
Equity NOK 101.7m
Incorporated 2022
Share capital NOK 2.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5,3 mill kr).

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 2025 financial year, show NOK 1.8m in revenue and NOK −5.3m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +0 %
Operating profit
NOK −5.3m
▼ −17 %
Equity
NOK 101.7m
▼ −5 %
Est. value
NOK 72.2m

Financial health · 2025

Liquidity
1.89
Good
Current assets ÷ current liabilities
Profitability
-4.9%
Not satisfactory
Return on total assets
Solidity
98.6%
Very good
Equity as a share of total capital

Who owns SNØ VINTERARENA AS?

SNØ VINTERARENA AS
NOK 1.8m rev. · NOK −5.3m 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 2025.

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 03.10.2026.

Report a problem

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