biztrac. BETA
COMPANY REGISTER PROFILE
930578983 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

GJESDAL INVEST AS

Org. no. 930578983 Limited company (AS) Sunnfjord Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 747,000
Incorporated 2022
Share capital NOK 160,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

GJESDAL INVEST AS is registered as a limited company in Sunnfjord, Vestland with organisation number 930578983. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 160,000, divided into 160 shares. The company's stated purpose is: “Investere i og eie aksjer i andre selskaper, og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
▲ +51 %
Equity
NOK 747,000
▲ +53 %
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns GJESDAL INVEST AS?

GJESDAL INVEST AS
NOK 0 rev. · NOK −10,000 profit

GJESDAL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GJESDAL INVEST AS own?

GJESDAL INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GJESDAL INVEST AS

Who owns GJESDAL INVEST AS?

Trond Gjesdal is the largest registered owner, with 100.0%.

What is the revenue of GJESDAL INVEST AS?

GJESDAL INVEST AS had revenue of NOK 0 in 2025.

Where is GJESDAL INVEST AS based?

GJESDAL INVEST AS has its business address in Vassenden.

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.