BIZTRAC BETA
Repair and maintenance of machinery

FJELLBEKK INVEST AS

Org. no. 926835203 Limited company (AS) Stad Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK 333,000
Incorporated 2021
Share capital NOK 295,000

Signals

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

FJELLBEKK INVEST AS is registered as a limited company in Stad, Vestland with organisation number 926835203. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2021. Registered share capital is NOK 295,000, divided into 295000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −10,000
Equity
NOK 333,000
Est. value
NOK 391,000

Financial health · 2024

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

Who owns FJELLBEKK INVEST AS?

JOHNNY SAKARIAS ELVEBAKKE
FJELLBEKK INVEST AS
· NOK −10,000 profit

FJELLBEKK INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does FJELLBEKK INVEST AS own?

FJELLBEKK INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FJELLBEKK INVEST AS

Who owns FJELLBEKK INVEST AS?

JOHNNY SAKARIAS ELVEBAKKE is the largest registered owner, with 49.2%.

Who is the general manager of FJELLBEKK INVEST AS?

Johnny Sakarias Elvebakke is registered as general manager of FJELLBEKK INVEST AS.

Where is FJELLBEKK INVEST AS based?

FJELLBEKK INVEST AS has its business address in Kjølsdalen.

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.