BIZTRAC BETA
Residential care activities for persons living with or having a diagnosis of intellectual disability

EOS UTVIKLING AS

Org. no. 990844488 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 28.4m
Operating profit NOK 1.8m
Equity NOK 3.1m
Incorporated 2007
Employees 41
Share capital NOK 100,000

EOS UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 990844488. The business is classified under residential care activities for persons living with or having a diagnosis of intellectual disability (NACE 87.202). The company was incorporated in 2007 and has 41 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Avlastning, behandling og konsulentvirksomhet innen helse- og sosialsektoren.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.4m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 28.4m
Operating profit
NOK 1.8m
Equity
NOK 3.1m
Est. value
NOK 5.8m

Financial health · 2024

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.5%
Satisfactory
Equity as a share of total capital

Who owns EOS UTVIKLING AS?

ARNE CHRISTIAN ØYGARD
EOS UTVIKLING AS
NOK 28.4m rev. · NOK 1.8m profit

EOS UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EOS UTVIKLING AS

Who owns EOS UTVIKLING AS?

ARNE CHRISTIAN ØYGARD is the largest registered owner, with 50.0%.

What is the revenue of EOS UTVIKLING AS?

EOS UTVIKLING AS had revenue of NOK 28.4m in 2024.

Who is the general manager of EOS UTVIKLING AS?

Arne Christian Øygard is registered as general manager of EOS UTVIKLING AS.

Where is EOS UTVIKLING AS based?

EOS UTVIKLING 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.