BIZTRAC BETA
Other captive investment companies

JARGON AS

Org. no. 919298030 Limited company (AS) Lillestrøm Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK −55,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

JARGON AS is registered as a limited company in Lillestrøm, Akershus with organisation number 919298030. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Direkte og/eller indirekte å kjøpe, eie og selge aksjer, obligasjoner og andre finansielle instrumenter og alt som er beslektet eller står i forbindelse med dette. Videre skal selskapets virksomhet kunne være -å eie - helt eller delvis - eller delta i selskaper eller næringsforetak som driver annen virksomhet, også gjennom å levere rådgivningstjenester.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK −55,000

Financial health · 2024

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-100.6%
Weak
Equity as a share of total capital

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

Who owns JARGON AS?

Jakob Egenæss Eide
JARGON AS
· NOK −14,000 profit

JARGON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JARGON AS

Who owns JARGON AS?

Jakob Egenæss Eide is the largest registered owner, with 100.0%.

Who is the general manager of JARGON AS?

Jakob Egenæss Eide is registered as general manager of JARGON AS.

Where is JARGON AS based?

JARGON AS has its business address in Leirsund.

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.