BIZTRAC BETA
Operation of sports facilities

LIATOPPEN SKISENTER AS

Org. no. 933147436 Limited company (AS) Ål Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 39,000
Incorporated 2024
Share capital NOK 40,000

LIATOPPEN SKISENTER AS is registered as a limited company in Ål, Buskerud with organisation number 933147436. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Liatoppen skisenter skal ikkje ha erverv til formål. Liatoppen skisenter har som hovudføremål å bygge, eige og drifte anlegg for idrett og fysisk aktivitet. Selskapet har ikkje til formål å skaffe aksjeeigarane økonomisk utbyte.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 39,000
Est. value
NOK 16,000

Financial health · 2025

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

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

Who owns LIATOPPEN SKISENTER AS?

No shareholders are registered for LIATOPPEN SKISENTER AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LIATOPPEN SKISENTER AS

What is the revenue of LIATOPPEN SKISENTER AS?

LIATOPPEN SKISENTER AS had revenue of NOK 0 in 2025.

Who is the general manager of LIATOPPEN SKISENTER AS?

Svein Torsteinsrud Furuhaug is registered as general manager of LIATOPPEN SKISENTER AS.

Where is LIATOPPEN SKISENTER AS based?

LIATOPPEN SKISENTER AS has its business address in Ål.

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.