BIZTRAC BETA
Uoppgitt

FJELLROSA HOLDING AS

Org. no. 935483417 Limited company (AS) Vinje Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −608
Equity NOK 150,000
Incorporated 2025
Share capital NOK 160,000

Signals

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

FJELLROSA HOLDING AS is registered as a limited company in Vinje, Telemark with organisation number 935483417. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 160,000, divided into 160 shares. The company's stated purpose is: “Investering i aksjer og det som hører sammen med slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −608 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −608
Equity
NOK 150,000
Est. value
NOK 176,000

Financial health · 2025

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

Who owns FJELLROSA HOLDING AS?

ARVE USTAD
FJELLROSA HOLDING AS
NOK 0 rev. · NOK −608 profit

FJELLROSA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FJELLROSA HOLDING AS own?

FJELLROSA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FJELLROSA HOLDING AS

Who owns FJELLROSA HOLDING AS?

ARVE USTAD is the largest registered owner, with 100.0%.

What is the revenue of FJELLROSA HOLDING AS?

FJELLROSA HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of FJELLROSA HOLDING AS?

Arve Ustad is registered as general manager of FJELLROSA HOLDING AS.

Where is FJELLROSA HOLDING AS based?

FJELLROSA HOLDING AS has its business address in Rauland.

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.