BIZTRAC BETA
Rental and operating of own or leased real estate

ENI INVEST AS

Org. no. 990193584 Limited company (AS) Tønsberg Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 220,000
Operating profit NOK −77,000
Equity NOK −713,000
Incorporated 2006
Share capital NOK 2.7m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−713k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−77k kr).

ENI INVEST AS is registered as a limited company in Tønsberg, Vestfold with organisation number 990193584. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 2.7m, divided into 2655000 shares. The company's stated purpose is: “Investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 220,000 in revenue and NOK −77,000 in operating profit.

Key figures · 2024

Revenue
NOK 220,000
Operating profit
NOK −77,000
Equity
NOK −713,000

Financial health · 2024

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

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

Who owns ENI INVEST AS?

ERIK NILSEN
ENI INVEST AS
NOK 220,000 rev. · NOK −77,000 profit

ENI INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ENI INVEST AS own?

ENI INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENI INVEST AS

Who owns ENI INVEST AS?

ERIK NILSEN is the largest registered owner, with 50.0%.

What is the revenue of ENI INVEST AS?

ENI INVEST AS had revenue of NOK 220,000 in 2024.

Where is ENI INVEST AS based?

ENI 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.