BIZTRAC BETA
Uoppgitt

ADIUNGO AS

Org. no. 998245478 Limited company (AS) Stavanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 5.6m
Incorporated 2012
Share capital NOK 137,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).
  • Nylig endring 2026-05-06 Aksjekapital registrert 2026-05-06.

ADIUNGO AS is registered as a limited company in Stavanger, Rogaland with organisation number 998245478. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2012. Registered share capital is NOK 137,000, divided into 1374 shares. The company's stated purpose is: “Selskapet skal være en SPV med formål å investere i Valide Invest II AS og co-investeringer i porteføljeselskaper i denne tilknytning.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 5.6m
Est. value
NOK 6.5m

Financial health · 2025

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

Who owns ADIUNGO AS?

SAAMAND AS
ADIUNGO AS
NOK 0 rev. · NOK −13,000 profit

ADIUNGO AS has 7 registered shareholders:

All shareholders and roles →

Which companies does ADIUNGO AS own?

ADIUNGO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ADIUNGO AS

Who owns ADIUNGO AS?

SAAMAND AS is the largest registered owner, with 16.7%.

What is the revenue of ADIUNGO AS?

ADIUNGO AS had revenue of NOK 0 in 2025.

Who is the general manager of ADIUNGO AS?

Lars Jansen Viste is registered as general manager of ADIUNGO AS.

Where is ADIUNGO AS based?

ADIUNGO AS has its business address in Stavanger.

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.