BIZTRAC BETA
Wholesale of other machinery and equipment

GEDIGEN HOLDING AS

Org. no. 913716523 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −14,000
Equity NOK 12.0m
Incorporated 2014
Share capital NOK 30,000

Signals

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

GEDIGEN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 913716523. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og eiendom og alt som er naturlig forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 12.0m
Est. value
NOK 9.9m

Financial health · 2024

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

Who owns GEDIGEN HOLDING AS?

PÅL FREGSTAD
GEDIGEN HOLDING AS
NOK 0 rev. · NOK −14,000 profit

GEDIGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GEDIGEN HOLDING AS own?

GEDIGEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

GEDIGEN HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about GEDIGEN HOLDING AS

Who owns GEDIGEN HOLDING AS?

PÅL FREGSTAD is the largest registered owner, with 100.0%.

What is the revenue of GEDIGEN HOLDING AS?

GEDIGEN HOLDING AS had revenue of NOK 0 in 2024.

Where is GEDIGEN HOLDING AS based?

GEDIGEN HOLDING AS has its business address in Bergen.

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.