BIZTRAC BETA
Uoppgitt

ERLPET HOLDING AS

Org. no. 932862948 Limited company (AS) Harstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK 9,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).
  • Nylig endring 2026-06-27 Adresseendring registrert 2026-06-27.

ERLPET HOLDING AS is registered as a limited company in Harstad, Troms with organisation number 932862948. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i andre selskaper. Selskapet kan delta i annen økonomisk virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 9,000
Est. value
NOK 11,000

Financial health · 2024

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

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

Who owns ERLPET HOLDING AS?

ERLING PETTERSEN
ERLPET HOLDING AS
NOK 0 rev. · NOK −12,000 profit

ERLPET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERLPET HOLDING AS own?

ERLPET HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ERLPET HOLDING AS

Who owns ERLPET HOLDING AS?

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

What is the revenue of ERLPET HOLDING AS?

ERLPET HOLDING AS had revenue of NOK 0 in 2024.

Where is ERLPET HOLDING AS based?

ERLPET HOLDING AS has its business address in Harstad.

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.