BIZTRAC BETA
Retail sale of sports equipment

FJELLKOMPANIET AS

Org. no. 925151629 Limited company (AS) Rollag Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 8.6m
Operating profit NOK −143,000
Equity NOK 783,000
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−143k kr).

FJELLKOMPANIET AS is registered as a limited company in Rollag, Buskerud with organisation number 925151629. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Butikkhandel med sportsutstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.6m in revenue and NOK −143,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.6m
Operating profit
NOK −143,000
Equity
NOK 783,000
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.3%
Good
Equity as a share of total capital

Who owns FJELLKOMPANIET AS?

OLE JOHAN MORKEN
FJELLKOMPANIET AS
NOK 8.6m rev. · NOK −143,000 profit

FJELLKOMPANIET AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FJELLKOMPANIET AS own?

FJELLKOMPANIET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FJELLKOMPANIET AS

Who owns FJELLKOMPANIET AS?

OLE JOHAN MORKEN is the largest registered owner, with 70.0%.

What is the revenue of FJELLKOMPANIET AS?

FJELLKOMPANIET AS had revenue of NOK 8.6m in 2024.

Who is the general manager of FJELLKOMPANIET AS?

Ole Johan Morken is registered as general manager of FJELLKOMPANIET AS.

Where is FJELLKOMPANIET AS based?

FJELLKOMPANIET AS has its business address in Veggli.

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.