BIZTRAC BETA
Hotels and similar accommodation

GOLSFJELLET EIENDOM AS

Org. no. 994251449 Limited company (AS) Gol Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 777,000
Operating profit NOK 360,000
Equity NOK 2.9m
Incorporated 2009
Share capital NOK 100,000

GOLSFJELLET EIENDOM AS is registered as a limited company in Gol, Buskerud with organisation number 994251449. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom, investering, samt deltagelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 777,000 in revenue and NOK 360,000 in operating profit.

Key figures · 2024

Revenue
NOK 777,000
Operating profit
NOK 360,000
Equity
NOK 2.9m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns GOLSFJELLET EIENDOM AS?

KNUT ARNE SVANG
GOLSFJELLET EIENDOM AS
NOK 777,000 rev. · NOK 360,000 profit

GOLSFJELLET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GOLSFJELLET EIENDOM AS own?

GOLSFJELLET EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

GOLSFJELLET EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about GOLSFJELLET EIENDOM AS

Who owns GOLSFJELLET EIENDOM AS?

KNUT ARNE SVANG is the largest registered owner, with 100.0%.

What is the revenue of GOLSFJELLET EIENDOM AS?

GOLSFJELLET EIENDOM AS had revenue of NOK 777,000 in 2024.

Where is GOLSFJELLET EIENDOM AS based?

GOLSFJELLET EIENDOM 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.