biztrac. BETA
COMPANY REGISTER PROFILE
834172992 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Motion picture, video and television programme post-production activities

ENIB INVEST AS

Org. no. 834172992 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK −173,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−173k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

ENIB INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 834172992. The business is classified under motion picture, video and television programme post-production activities (NACE 59.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering og konsulentvirksomhet innen film og TV.”.

Key figures · 2025

Operating profit
NOK −10,000
Equity
NOK −173,000
▼ −813 %

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
-4.0%
Weak
Equity as a share of total capital

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

Who owns ENIB INVEST AS?

ENIB INVEST AS
· NOK −10,000 profit

ENIB INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ENIB INVEST AS own?

ENIB INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENIB INVEST AS

Who owns ENIB INVEST AS?

Espen Nordahl is the largest registered owner, with 100.0%.

Who is the general manager of ENIB INVEST AS?

Espen Nordahl is registered as general manager of ENIB INVEST AS.

Where is ENIB INVEST AS based?

ENIB INVEST AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.