BIZTRAC BETA
Business and other management consultancy activities

ORGEVO AS

Org. no. 998610125 Limited company (AS) Tønsberg Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 90,000
Operating profit NOK −520,000
Equity NOK 626,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−520k kr).

ORGEVO AS is registered as a limited company in Tønsberg, Vestfold with organisation number 998610125. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester og kurs innenfor organisasjon, strategi og ledelse, investeringer i aksjer, deltagelse i andre selskaper og hva som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 90,000 in revenue and NOK −520,000 in operating profit.

Key figures · 2024

Revenue
NOK 90,000
Operating profit
NOK −520,000
Equity
NOK 626,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns ORGEVO AS?

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

Which companies does ORGEVO AS own?

ORGEVO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ORGEVO AS

What is the revenue of ORGEVO AS?

ORGEVO AS had revenue of NOK 90,000 in 2024.

Who is the general manager of ORGEVO AS?

Øyvind Stokkedal is registered as general manager of ORGEVO AS.

Where is ORGEVO AS based?

ORGEVO AS has its business address in Tolvsrød.

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.