BIZTRAC BETA
Operation of sports facilities

HALLINGSKARVET SKISENTER AS

Org. no. 929363922 Limited company (AS) Hol Incorporated 1980 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK 605,000
Equity NOK 4.6m
Incorporated 1980
Employees 5
Share capital NOK 500,000

HALLINGSKARVET SKISENTER AS is registered as a limited company in Hol, Buskerud with organisation number 929363922. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 1980 and has 5 registered employees. Registered share capital is NOK 500,000, divided into 2000000 shares. The company's stated purpose is: “Utvikling, bygging og drift av skisenter og alpin- anlegg samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 605,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK 605,000
Equity
NOK 4.6m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns HALLINGSKARVET SKISENTER AS?

KNUT ANFINSET
HALLINGSKARVET SKISENTER AS
NOK 5.2m rev. · NOK 605,000 profit

HALLINGSKARVET SKISENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALLINGSKARVET SKISENTER AS

Who owns HALLINGSKARVET SKISENTER AS?

KNUT ANFINSET is the largest registered owner, with 100.0%.

What is the revenue of HALLINGSKARVET SKISENTER AS?

HALLINGSKARVET SKISENTER AS had revenue of NOK 5.2m in 2025.

Who is the general manager of HALLINGSKARVET SKISENTER AS?

Knut Anfinset is registered as general manager of HALLINGSKARVET SKISENTER AS.

Where is HALLINGSKARVET SKISENTER AS based?

HALLINGSKARVET SKISENTER AS has its business address in Hovet.

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.