BIZTRAC BETA
Other captive investment companies

ESPEN PETTERSEN HOLDING AS

Org. no. 920914136 Limited company (AS) Grimstad Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 1.1m
Incorporated 2018
Share capital NOK 30,000

Signals

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

ESPEN PETTERSEN HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 920914136. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i selskaper og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 1.1m
Est. value
NOK 974,000

Financial health · 2025

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

Who owns ESPEN PETTERSEN HOLDING AS?

ESPEN PETTERSEN
ESPEN PETTERSEN HOLDING AS
NOK 0 rev. · NOK −4,000 profit

ESPEN PETTERSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESPEN PETTERSEN HOLDING AS own?

ESPEN PETTERSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESPEN PETTERSEN HOLDING AS

Who owns ESPEN PETTERSEN HOLDING AS?

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

What is the revenue of ESPEN PETTERSEN HOLDING AS?

ESPEN PETTERSEN HOLDING AS had revenue of NOK 0 in 2025.

Where is ESPEN PETTERSEN HOLDING AS based?

ESPEN PETTERSEN HOLDING AS has its business address in Fevik.

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.