BIZTRAC BETA
Uoppgitt

ETEV AS

Org. no. 989119427 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 160,000
Operating profit NOK −402,000
Equity NOK −398,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

ETEV AS is registered as a limited company in Oslo, Oslo with organisation number 989119427. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Primært kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagende, men salg av konsulenttjenester og utvikling og salg av produkter som naturlig faller sammen med dette, inngårt også i formålet. Dette innebærer at selskapet også kan delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 160,000 in revenue and NOK −402,000 in operating profit.

Key figures · 2024

Revenue
NOK 160,000
Operating profit
NOK −402,000
Equity
NOK −398,000

Financial health · 2024

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

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

Who owns ETEV AS?

EYSTEIN EMBERLAND
ETEV AS
NOK 160,000 rev. · NOK −402,000 profit

ETEV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ETEV AS

Who owns ETEV AS?

EYSTEIN EMBERLAND is the largest registered owner, with 100.0%.

What is the revenue of ETEV AS?

ETEV AS had revenue of NOK 160,000 in 2024.

Where is ETEV AS based?

ETEV 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 15.06.2026.

Report a problem

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