BIZTRAC BETA
Other captive investment companies

JEGERBERGET AS

Org. no. 915866352 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK 372,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).
  • Nylig endring 2026-07-08 Adresseendring registrert 2026-07-08.

JEGERBERGET AS is registered as a limited company in Oslo, Oslo with organisation number 915866352. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investere i aksjer, eiendom, obligasjoner, bankinnskudd og andre finansielle instrumenter i norske kroner eller utenlandsk valuta.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 372,000
Est. value
NOK 306,000

Financial health · 2024

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.9%
Good
Equity as a share of total capital

Who owns JEGERBERGET AS?

ROBERT FJELLI
JEGERBERGET AS
NOK 0 rev. · NOK −5,000 profit

JEGERBERGET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JEGERBERGET AS own?

JEGERBERGET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JEGERBERGET AS

Who owns JEGERBERGET AS?

ROBERT FJELLI is the largest registered owner, with 100.0%.

What is the revenue of JEGERBERGET AS?

JEGERBERGET AS had revenue of NOK 0 in 2024.

Where is JEGERBERGET AS based?

JEGERBERGET 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.