BIZTRAC BETA
Uoppgitt

FJELLRYPESTEGGEN AS

Org. no. 989218751 Limited company (AS) Tromsø Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 98,000
Operating profit NOK −371,000
Equity NOK 9.5m
Incorporated 2005
Share capital NOK 100,000

Signals

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

FJELLRYPESTEGGEN AS is registered as a limited company in Tromsø, Troms with organisation number 989218751. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er investering i andre selskaper, samt hva derved står i sammenheng. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 98,000 in revenue and NOK −371,000 in operating profit.

Key figures · 2024

Revenue
NOK 98,000
Operating profit
NOK −371,000
Equity
NOK 9.5m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns FJELLRYPESTEGGEN AS?

STÅLE FRISVOLD
FJELLRYPESTEGGEN AS
NOK 98,000 rev. · NOK −371,000 profit

FJELLRYPESTEGGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FJELLRYPESTEGGEN AS own?

FJELLRYPESTEGGEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FJELLRYPESTEGGEN AS

Who owns FJELLRYPESTEGGEN AS?

STÅLE FRISVOLD is the largest registered owner, with 100.0%.

What is the revenue of FJELLRYPESTEGGEN AS?

FJELLRYPESTEGGEN AS had revenue of NOK 98,000 in 2024.

Where is FJELLRYPESTEGGEN AS based?

FJELLRYPESTEGGEN AS has its business address in Tromsø.

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.