BIZTRAC BETA
Computer consultancy and computer facilities management activities

EMVILD AS

Org. no. 830260722 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 25,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).
  • Nylig endring 2026-07-23 Adresseendring registrert 2026-07-23.

EMVILD AS is registered as a limited company in Bergen, Vestland with organisation number 830260722. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen teknologi - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK 25,000
Est. value
NOK 46,000

Financial health · 2024

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

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

Who owns EMVILD AS?

INGVILD ELISE ROKNE STENSLAND
EMVILD AS
· NOK −5,000 profit

EMVILD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EMVILD AS own?

EMVILD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EMVILD AS

Who owns EMVILD AS?

INGVILD ELISE ROKNE STENSLAND is the largest registered owner, with 100.0%.

Who is the general manager of EMVILD AS?

Ingvild Elise Rokne Stensland is registered as general manager of EMVILD AS.

Where is EMVILD AS based?

EMVILD AS has its business address in Bergen.

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.