BIZTRAC BETA
Rental and operating of own or leased real estate

ESKEDAL HOLDING AS

Org. no. 923829946 Limited company (AS) Tønsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −15,000
Equity NOK 661,000
Incorporated 2019
Share capital NOK 59,000

Signals

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

ESKEDAL HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 923829946. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 59,000, divided into 198 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, kjøp, salg og utleie av fast eiendom, samt hva som herav står i naturlig forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 661,000
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns ESKEDAL HOLDING AS?

ANDERS ESKEDAL
ESKEDAL HOLDING AS
NOK 0 rev. · NOK −15,000 profit

ESKEDAL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESKEDAL HOLDING AS own?

ESKEDAL HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ESKEDAL HOLDING AS

Who owns ESKEDAL HOLDING AS?

ANDERS ESKEDAL is the largest registered owner, with 100.0%.

What is the revenue of ESKEDAL HOLDING AS?

ESKEDAL HOLDING AS had revenue of NOK 0 in 2024.

Where is ESKEDAL HOLDING AS based?

ESKEDAL HOLDING AS has its business address in Sem.

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.