biztrac. BETA
COMPANY REGISTER PROFILE
936057853 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Operation of sports facilities

FJELLGÅRDEN DRIFT AS

Org. no. 936057853 Limited company (AS) Hemsedal Incorporated 2025 Active
Revenue 2025 NOK 410,000
Operating profit NOK −418,000
Equity NOK −395,000
Incorporated 2025
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−395k kr).

FJELLGÅRDEN DRIFT AS is registered as a limited company in Hemsedal, Buskerud with organisation number 936057853. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2025 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å drifte skisenter, salg av varer, drift av kafé.”. The most recent filed accounts, for the 2025 financial year, show NOK 410,000 in revenue and NOK −418,000 in operating profit.

Former names: AFAS 180825-12 AS

Key figures · 2025

Revenue
NOK 410,000
Operating profit
NOK −418,000
Equity
NOK −395,000

Financial health · 2025

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

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

Who owns FJELLGÅRDEN DRIFT AS?

FJELLGÅRDEN DRIFT AS
NOK 410,000 rev. · NOK −418,000 profit

FJELLGÅRDEN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJELLGÅRDEN DRIFT AS

Who owns FJELLGÅRDEN DRIFT AS?

Jørgen Hjemdal Heje is the largest registered owner, with 100.0%.

What is the revenue of FJELLGÅRDEN DRIFT AS?

FJELLGÅRDEN DRIFT AS had revenue of NOK 410,000 in 2025.

Where is FJELLGÅRDEN DRIFT AS based?

FJELLGÅRDEN DRIFT 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 03.10.2026.

Report a problem

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