BIZTRAC BETA
Development of building projects

GOLF HEMSEDAL AS

Org. no. 971129530 Limited company (AS) Hemsedal Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −210,000
Equity NOK 3.8m
Incorporated 1994
Share capital NOK 4.9m

Signals

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

GOLF HEMSEDAL AS is registered as a limited company in Hemsedal, Buskerud with organisation number 971129530. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1994. Registered share capital is NOK 4.9m, divided into 49230 shares. The company's stated purpose is: “Å utvikle og drive golfbane med tilhørende aktiviteter. Under formålet faller også utvikling og salg av fritidsleiligheter til golfinteresserte.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −210,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK −210,000
Equity
NOK 3.8m
Est. value
NOK 5.7m

Financial health · 2025

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

Who owns GOLF HEMSEDAL AS?

SKAARET HOLDING AS
GOLF HEMSEDAL AS
NOK 2.0m rev. · NOK −210,000 profit

GOLF HEMSEDAL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GOLF HEMSEDAL AS

Who owns GOLF HEMSEDAL AS?

SKAARET HOLDING AS is the largest registered owner, with 76.4%.

What is the revenue of GOLF HEMSEDAL AS?

GOLF HEMSEDAL AS had revenue of NOK 2.0m in 2025.

Where is GOLF HEMSEDAL AS based?

GOLF HEMSEDAL AS has its business address in Hemsedal.

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.