BIZTRAC BETA
Wholesale of other household goods

ESHAJA HOLDING AS

Org. no. 926358049 Limited company (AS) Kristiansand Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 6,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

ESHAJA HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 926358049. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rådgivning og konsulentoppdrag, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 6,000
Est. value
NOK 7,000

Financial health · 2024

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

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

Who owns ESHAJA HOLDING AS?

ESPEN HASSELBERG JACOBSEN
ESHAJA HOLDING AS
NOK 0 rev. · NOK −6,000 profit

ESHAJA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESHAJA HOLDING AS own?

ESHAJA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESHAJA HOLDING AS

Who owns ESHAJA HOLDING AS?

ESPEN HASSELBERG JACOBSEN is the largest registered owner, with 100.0%.

What is the revenue of ESHAJA HOLDING AS?

ESHAJA HOLDING AS had revenue of NOK 0 in 2024.

Where is ESHAJA HOLDING AS based?

ESHAJA HOLDING AS has its business address in Kristiansand S.

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.