BIZTRAC BETA
Uoppgitt

EMANVI AS

Org. no. 936204384 Limited company (AS) Gloppen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-11.

EMANVI AS is registered as a limited company in Gloppen, Vestland with organisation number 936204384. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eige, forvalte og selje andelar i andre selskap, og dessutan å utøve aktivitetar som er komplementære til desse, inkluderte, men ikkje avgrensa til, finansiell rådgiving og forvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns EMANVI AS?

ØYSTEIN VALLESTAD
EMANVI AS
NOK 0 rev. · NOK −7,000 profit

EMANVI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EMANVI AS own?

EMANVI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EMANVI AS

Who owns EMANVI AS?

ØYSTEIN VALLESTAD is the largest registered owner, with 100.0%.

What is the revenue of EMANVI AS?

EMANVI AS had revenue of NOK 0 in 2025.

Where is EMANVI AS based?

EMANVI AS has its business address in Sandane.

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.