biztrac. BETA
COMPANY REGISTER PROFILE
998121345 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

JGA INVEST AS

Org. no. 998121345 Limited company (AS) Vestby Incorporated 2012 Active
Revenue 2025 NOK 1.8m
Operating profit NOK 1.7m
Equity NOK 10.6m
Incorporated 2012
Share capital NOK 40,000

Signals

1 flags
  • Nylig endring 2026-07-07 Aksjekapital registrert 2026-07-07.

JGA INVEST AS is registered as a limited company in Vestby, Akershus with organisation number 998121345. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 40,000, divided into 1 shares. The company's stated purpose is: “Selskapets formål er å eie akjser og/eller andeler i PricewaterhouseCoopers, i tillegg til at selskapet kan inneha andre finansielle eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +0 %
Operating profit
NOK 1.7m
▼ −0 %
Equity
NOK 10.6m
▲ +21 %
Est. value
NOK 11.1m

Financial health · 2025

Liquidity
423.23
Very good
Current assets ÷ current liabilities
Profitability
18.9%
Very good
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns JGA INVEST AS?

JGA INVEST AS
NOK 1.8m rev. · NOK 1.7m profit

JGA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JGA INVEST AS own?

JGA INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JGA INVEST AS

Who owns JGA INVEST AS?

Jonas Gaudernack is the largest registered owner, with 100.0%.

What is the revenue of JGA INVEST AS?

JGA INVEST AS had revenue of NOK 1.8m in 2025.

Where is JGA INVEST AS based?

JGA INVEST AS has its business address in Son.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.