BIZTRAC BETA
COMPANY REGISTER PROFILE
989170597 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

STOREFJELL BOOKING AS

Org. no. 989170597 Limited company (AS) Gol Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −652,000
Equity NOK 14.3m
Incorporated 2005
Share capital NOK 936,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−652k kr).

STOREFJELL BOOKING AS is registered as a limited company in Gol, Buskerud with organisation number 989170597. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 936,000, divided into 4680 shares. The company's stated purpose is: “Investeringer i andre selskaper, deltakelse i eiendomsutvikling samt dertil hørende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −652,000 in operating profit.

Former names: GULLKNAPP AS, GOLSFJELLET BOOKING AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −652,000
▲ +16 %
Equity
NOK 14.3m
▲ +41 %
Est. value
NOK 22.8m

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
32.8%
Very good
Return on total assets
Solidity
97.1%
Very good
Equity as a share of total capital

Who owns STOREFJELL BOOKING AS?

STOREFJELL BOOKING AS
NOK 0 rev. · NOK −652,000 profit

STOREFJELL BOOKING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOREFJELL BOOKING AS

Who owns STOREFJELL BOOKING AS?

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

What is the revenue of STOREFJELL BOOKING AS?

STOREFJELL BOOKING AS had revenue of NOK 0 in 2025.

Where is STOREFJELL BOOKING AS based?

STOREFJELL BOOKING 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 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.