BIZTRAC BETA
Operation of sports facilities

GOL SKISENTER AS

Org. no. 924753145 Limited company (AS) Gol Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −6.5m
Equity NOK −15.9m
Incorporated 2020
Employees 11
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−15,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6,5 mill kr).

GOL SKISENTER AS is registered as a limited company in Gol, Buskerud with organisation number 924753145. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2020 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Skiheisdrift. Turisme.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −6.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −6.5m
Equity
NOK −15.9m

Financial health · 2024

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

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

Who owns GOL SKISENTER AS?

SKAGAHØGDI AS
GOL SKISENTER AS
NOK 2.0m rev. · NOK −6.5m profit

GOL SKISENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GOL SKISENTER AS

Who owns GOL SKISENTER AS?

SKAGAHØGDI AS is the largest registered owner, with 100.0%.

What is the revenue of GOL SKISENTER AS?

GOL SKISENTER AS had revenue of NOK 2.0m in 2024.

Who is the general manager of GOL SKISENTER AS?

Erik Tvindesæter is registered as general manager of GOL SKISENTER AS.

Where is GOL SKISENTER AS based?

GOL SKISENTER AS has its business address in Gol.

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.