BIZTRAC BETA
Other technical consultancy

EYVI AS

Org. no. 922541531 Limited company (AS) Tønsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 777.7m
Operating profit NOK 23.4m
Equity NOK 120.8m
Incorporated 2019
Employees 70
Share capital NOK 1.0m

EYVI AS is registered as a limited company in Tønsberg, Vestfold with organisation number 922541531. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019 and has 70 registered employees. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Utvikle, designe og bygge prosessanlegg innen landbasert akvakultur både nasjonalt og internasjonalt. Videre tilknyttede produkter samt yte andre tjenester forbundet med prosjektering, installasjon og drift av slike anlegg.”. The most recent filed accounts, for the 2024 financial year, show NOK 777.7m in revenue and NOK 23.4m in operating profit.

Key figures · 2024

Revenue
NOK 777.7m
Operating profit
NOK 23.4m
Equity
NOK 120.8m
Est. value
NOK 167.8m

Financial health · 2024

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.4%
Good
Equity as a share of total capital

Who owns EYVI AS?

EYVI HOLDING AS
EYVI AS
NOK 777.7m rev. · NOK 23.4m profit

EYVI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EYVI AS own?

EYVI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EYVI AS

Who owns EYVI AS?

EYVI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of EYVI AS?

EYVI AS had revenue of NOK 777.7m in 2024.

Who is the general manager of EYVI AS?

Torgeir Vreim is registered as general manager of EYVI AS.

Where is EYVI AS based?

EYVI AS has its business address in Tønsberg.

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.