BIZTRAC BETA
Rental and operating of own or leased real estate

EIDSFOSS INVEST AS

Org. no. 989185853 Limited company (AS) Tønsberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 265,000
Operating profit NOK −127,000
Equity NOK 11.5m
Incorporated 2005
Share capital NOK 100,000

Signals

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

EIDSFOSS INVEST AS is registered as a limited company in Tønsberg, Vestfold with organisation number 989185853. 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: “Eie og forvaltning av aksjer og andre verdipapirer samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 265,000 in revenue and NOK −127,000 in operating profit.

Key figures · 2025

Revenue
NOK 265,000
Operating profit
NOK −127,000
Equity
NOK 11.5m
Est. value
NOK 27.3m

Financial health · 2025

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

Who owns EIDSFOSS INVEST AS?

PÅL JEVANORD
EIDSFOSS INVEST AS
NOK 265,000 rev. · NOK −127,000 profit

EIDSFOSS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIDSFOSS INVEST AS own?

EIDSFOSS INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIDSFOSS INVEST AS

Who owns EIDSFOSS INVEST AS?

PÅL JEVANORD is the largest registered owner, with 100.0%.

What is the revenue of EIDSFOSS INVEST AS?

EIDSFOSS INVEST AS had revenue of NOK 265,000 in 2025.

Where is EIDSFOSS INVEST AS based?

EIDSFOSS INVEST AS has its business address in Tønsberg.

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.