BIZTRAC BETA
Uoppgitt

ERLING EGGE HOLDING AS

Org. no. 932578379 Limited company (AS) Gloppen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 8.5m
Incorporated 2023
Share capital NOK 30,000

Signals

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

ERLING EGGE HOLDING AS is registered as a limited company in Gloppen, Vestland with organisation number 932578379. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 8.5m
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns ERLING EGGE HOLDING AS?

ERLING EGGE
ERLING EGGE HOLDING AS
NOK 0 rev. · NOK −16,000 profit

ERLING EGGE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERLING EGGE HOLDING AS

Who owns ERLING EGGE HOLDING AS?

ERLING EGGE is the largest registered owner, with 100.0%.

What is the revenue of ERLING EGGE HOLDING AS?

ERLING EGGE HOLDING AS had revenue of NOK 0 in 2025.

Where is ERLING EGGE HOLDING AS based?

ERLING EGGE HOLDING AS has its business address in Byrkjelo.

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.