biztrac. BETA
COMPANY REGISTER PROFILE
989213164 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

FJELLENDEN HOLDING AS

Org. no. 989213164 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 970,000
Incorporated 2005
Share capital NOK 66,000

Signals

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

FJELLENDEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 989213164. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 66,000, divided into 655 shares. The company's stated purpose is: “Selskapets virksomhet er investeringer i andre foretak og hva dermed er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
▲ +21 %
Equity
NOK 970,000
▲ +18 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
2.6%
Weak
Return on total assets
Solidity
17.6%
Satisfactory
Equity as a share of total capital

Who owns FJELLENDEN HOLDING AS?

FJELLENDEN HOLDING AS
NOK 0 rev. · NOK −1,000 profit

FJELLENDEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FJELLENDEN HOLDING AS own?

FJELLENDEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FJELLENDEN HOLDING AS

Who owns FJELLENDEN HOLDING AS?

Helge Vilhelmsen is the largest registered owner, with 100.0%.

What is the revenue of FJELLENDEN HOLDING AS?

FJELLENDEN HOLDING AS had revenue of NOK 0 in 2025.

Where is FJELLENDEN HOLDING AS based?

FJELLENDEN HOLDING AS has its business address in Oslo.

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.