BIZTRAC BETA
Uoppgitt

ELLEVILLE HOLDING AS

Org. no. 926688081 Limited company (AS) Porsanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK −7,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

ELLEVILLE HOLDING AS is registered as a limited company in Porsanger, Finnmark with organisation number 926688081. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK −7,000

Financial health · 2024

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

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

Who owns ELLEVILLE HOLDING AS?

Heli Marjaana Korhonen
ELLEVILLE HOLDING AS
NOK 0 rev. · NOK −12,000 profit

ELLEVILLE HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ELLEVILLE HOLDING AS own?

ELLEVILLE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ELLEVILLE HOLDING AS

Who owns ELLEVILLE HOLDING AS?

Heli Marjaana Korhonen is the largest registered owner, with 50.0%.

What is the revenue of ELLEVILLE HOLDING AS?

ELLEVILLE HOLDING AS had revenue of NOK 0 in 2024.

Where is ELLEVILLE HOLDING AS based?

ELLEVILLE HOLDING AS has its business address in Russenes.

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.