BIZTRAC BETA
Uoppgitt

FJELL INVESTERING AS

Org. no. 936736300 Limited company (AS) Øygarden Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-27.

FJELL INVESTERING AS is registered as a limited company in Øygarden, Vestland with organisation number 936736300. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og forvalte aksjer, andeler og andre investeringer i selskaper, samt å drive investeringsvirksomhet, administrasjonstjenester og rådgivning. Selskapet kan også foreta investeringer i fast eiendom, verdipapirer og andre finansielle instrumenter, samt annen virksomhet som står i naturlig sammenheng med dette. Virksomheten kan drives selv eller gjennom deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2025

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

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

Who owns FJELL INVESTERING AS?

STINE NORDEIDE FJELL
FJELL INVESTERING AS
· NOK 0 profit

FJELL INVESTERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJELL INVESTERING AS

Who owns FJELL INVESTERING AS?

STINE NORDEIDE FJELL is the largest registered owner, with 50.0%.

Who is the general manager of FJELL INVESTERING AS?

Stine Nordeide Fjell is registered as general manager of FJELL INVESTERING AS.

Where is FJELL INVESTERING AS based?

FJELL INVESTERING AS has its business address in Kolltveit.

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.