BIZTRAC BETA
Work training and permanently adapted work

INNOVI AS

Org. no. 864780482 Limited company (AS) Indre Østfold Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 36.4m
Operating profit NOK 762,000
Equity NOK 16.6m
Incorporated 1992
Employees 26
Share capital NOK 189,000

INNOVI AS is registered as a limited company in Indre Østfold, Østfold with organisation number 864780482. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 1992 and has 26 registered employees. Registered share capital is NOK 189,000, divided into 189 shares. The company's stated purpose is: “Innovi skal arbeide for å forhindre frafall fra arbeidsliv og skole/utdanning ved å tilby meningsfulle og utviklende arenaer som legger til rette for personlig vekst. Virksomheten skal gjennom veiledning og kvalifisering bidra til at alle får styrket mulighetene til å utnytte sitt arbeidspotensial, gjennom en stabil arbeidstilknytning lokalt og regionalt.”. The most recent filed accounts, for the 2024 financial year, show NOK 36.4m in revenue and NOK 762,000 in operating profit.

Key figures · 2024

Revenue
NOK 36.4m
Operating profit
NOK 762,000
Equity
NOK 16.6m
Est. value
NOK 16.0m

Financial health · 2024

Liquidity
3.25
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
72.8%
Very good
Equity as a share of total capital

Who owns INNOVI AS?

No shareholders are registered for INNOVI AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about INNOVI AS

What is the revenue of INNOVI AS?

INNOVI AS had revenue of NOK 36.4m in 2024.

Who is the general manager of INNOVI AS?

Jens Mellquist is registered as general manager of INNOVI AS.

Where is INNOVI AS based?

INNOVI AS has its business address in Trøgstad.

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.