BIZTRAC BETA
Other unspecified social services without accommodation

ADCURO AS

Org. no. 929160878 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 995,000
Operating profit NOK 99,000
Equity NOK 166,000
Incorporated 2022
Share capital NOK 30,000

ADCURO AS is registered as a limited company in Oslo, Oslo with organisation number 929160878. The business is classified under other unspecified social services without accommodation (NACE 88.996). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Driver innenfor helse, omsorg, skole/alternativ læringsarena for enkeltelever, jobbtrening, dagsenter, øvingsboliger med botrening ovenfor mennesker med ulike bistandsbehov og utfordrende atferd, å utføre omsorgstjenester, vikartjenester, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 995,000 in revenue and NOK 99,000 in operating profit.

Key figures · 2024

Revenue
NOK 995,000
Operating profit
NOK 99,000
Equity
NOK 166,000
Est. value
NOK 585,000

Financial health · 2024

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

Who owns ADCURO AS?

SPERO AS
ADCURO AS
NOK 995,000 rev. · NOK 99,000 profit

ADCURO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADCURO AS

Who owns ADCURO AS?

SPERO AS is the largest registered owner, with 50.0%.

What is the revenue of ADCURO AS?

ADCURO AS had revenue of NOK 995,000 in 2024.

Who is the general manager of ADCURO AS?

Svein-Erik Myrbakken is registered as general manager of ADCURO AS.

Where is ADCURO AS based?

ADCURO 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.