biztrac. BETA
COMPANY REGISTER PROFILE
935935938 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

JØRGEN GAMST HOLDING AS

Org. no. 935935938 Limited company (AS) Tromsø Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK −2,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2k kr).

JØRGEN GAMST HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 935935938. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper samt investering.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK −2,000

Financial health · 2025

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

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

Who owns JØRGEN GAMST HOLDING AS?

JØRGEN GAMST HOLDING AS
NOK 0 rev. · NOK −2,000 profit

JØRGEN GAMST HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JØRGEN GAMST HOLDING AS

Who owns JØRGEN GAMST HOLDING AS?

Jørgen Gamst is the largest registered owner, with 100.0%.

What is the revenue of JØRGEN GAMST HOLDING AS?

JØRGEN GAMST HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of JØRGEN GAMST HOLDING AS?

Jørgen Gamst is registered as general manager of JØRGEN GAMST HOLDING AS.

Where is JØRGEN GAMST HOLDING AS based?

JØRGEN GAMST HOLDING AS has its business address in Kvaløya.

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.