BIZTRAC BETA
Uoppgitt

SILJE FJELDSTAD AS

Org. no. 925406775 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK −24,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−24k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

SILJE FJELDSTAD AS is registered as a limited company in Oslo, Oslo with organisation number 925406775. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Investering i andre selskaper, samt annen virksomhet som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK −24,000

Financial health · 2025

Liquidity
2.99
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4.8%
Weak
Equity as a share of total capital

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

Who owns SILJE FJELDSTAD AS?

SILJE FJELDSTAD
SILJE FJELDSTAD AS
NOK 0 rev. · NOK −15,000 profit

SILJE FJELDSTAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SILJE FJELDSTAD AS own?

SILJE FJELDSTAD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SILJE FJELDSTAD AS

Who owns SILJE FJELDSTAD AS?

SILJE FJELDSTAD is the largest registered owner, with 100.0%.

What is the revenue of SILJE FJELDSTAD AS?

SILJE FJELDSTAD AS had revenue of NOK 0 in 2025.

Where is SILJE FJELDSTAD AS based?

SILJE FJELDSTAD 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 15.06.2026.

Report a problem

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