BIZTRAC BETA
Uoppgitt

GJØRTZ INVEST AS

Org. no. 990305781 Limited company (AS) Ålesund Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −54,000
Equity NOK −2.1m
Incorporated 2006
Share capital NOK 3.1m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−54k kr).

GJØRTZ INVEST AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 990305781. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2006. Registered share capital is NOK 3.1m, divided into 3100 shares. The company's stated purpose is: “Kjøp, eie, utleie og drift av fast eiendom, investeringer og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −54,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −54,000
Equity
NOK −2.1m

Financial health · 2024

Liquidity
409.62
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-57.7%
Weak
Equity as a share of total capital

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

Who owns GJØRTZ INVEST AS?

CAMILLA GJØRTZ
GJØRTZ INVEST AS
NOK 0 rev. · NOK −54,000 profit

GJØRTZ INVEST AS has 5 registered shareholders:

All shareholders and roles →

Which companies does GJØRTZ INVEST AS own?

GJØRTZ INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about GJØRTZ INVEST AS

Who owns GJØRTZ INVEST AS?

CAMILLA GJØRTZ is the largest registered owner, with 33.2%.

What is the revenue of GJØRTZ INVEST AS?

GJØRTZ INVEST AS had revenue of NOK 0 in 2024.

Where is GJØRTZ INVEST AS based?

GJØRTZ INVEST AS has its business address in Ålesund.

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.