BIZTRAC BETA
Rental and operating of own or leased real estate

EIGIL HOLDING AS

Org. no. 989148818 Limited company (AS) Færder Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 96,000
Operating profit NOK −159,000
Equity NOK 21.0m
Incorporated 2005
Share capital NOK 100,000

Signals

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

EIGIL HOLDING AS is registered as a limited company in Færder, Vestfold with organisation number 989148818. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andeler i andre virksomheter, kjøp, salg og utleie av fast eiendom, samt konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 96,000 in revenue and NOK −159,000 in operating profit.

Key figures · 2025

Revenue
NOK 96,000
Operating profit
NOK −159,000
Equity
NOK 21.0m
Est. value
NOK 19.6m

Financial health · 2025

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

Who owns EIGIL HOLDING AS?

EIGIL NÆSS
EIGIL HOLDING AS
NOK 96,000 rev. · NOK −159,000 profit

EIGIL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIGIL HOLDING AS own?

EIGIL HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EIGIL HOLDING AS

Who owns EIGIL HOLDING AS?

EIGIL NÆSS is the largest registered owner, with 100.0%.

What is the revenue of EIGIL HOLDING AS?

EIGIL HOLDING AS had revenue of NOK 96,000 in 2025.

Where is EIGIL HOLDING AS based?

EIGIL HOLDING AS has its business address in Nøtterøy.

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.