BIZTRAC BETA
Other captive investment companies

JG INVESTMENTS AS

Org. no. 916367899 Limited company (AS) Orkland Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −57,000
Equity NOK 9.2m
Incorporated 2015
Share capital NOK 60,000

Signals

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

JG INVESTMENTS AS is registered as a limited company in Orkland, Trøndelag with organisation number 916367899. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Investering i fast eiendom og aksjer, handel, garantistillelse, forretningsutvikling, deltagelse i andre selskaper og hva dermed står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −57,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −57,000
Equity
NOK 9.2m
Est. value
NOK 8.4m

Financial health · 2024

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

Who owns JG INVESTMENTS AS?

JANNE GJØNNES KAMBESTAD
JG INVESTMENTS AS
NOK 0 rev. · NOK −57,000 profit

JG INVESTMENTS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JG INVESTMENTS AS own?

JG INVESTMENTS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about JG INVESTMENTS AS

Who owns JG INVESTMENTS AS?

JANNE GJØNNES KAMBESTAD is the largest registered owner, with 100.0%.

What is the revenue of JG INVESTMENTS AS?

JG INVESTMENTS AS had revenue of NOK 0 in 2024.

Where is JG INVESTMENTS AS based?

JG INVESTMENTS AS has its business address in Orkanger.

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.