biztrac. BETA
COMPANY REGISTER PROFILE
997107802 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Activities in child welfare institutions

JANUS OMSORG AS

Org. no. 997107802 Limited company (AS) Asker Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 32.7m
Operating profit NOK 2.2m
Equity NOK 3.5m
Incorporated 2011
Employees 33
Share capital NOK 350,000

JANUS OMSORG AS is registered as a limited company in Asker, Akershus with organisation number 997107802. The business is classified under activities in child welfare institutions (NACE 87.991). The company was incorporated in 2011 and has 33 registered employees. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Tilby bo- og avlastningstjenester for barn og unge, samt barneverntjenester i og utenfor institusjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 32.7m in revenue and NOK 2.2m in operating profit.

Former names: OMSORGSPARTNER1 AS, OMSORGSPARTNER UNG AS

Key figures · 2025

Revenue
NOK 32.7m
▲ +24 %
Operating profit
NOK 2.2m
▲ +14 %
Equity
NOK 3.5m
▼ −14 %
Est. value
NOK 11.8m

Financial health · 2025

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
23.3%
Very good
Return on total assets
Solidity
34.2%
Good
Equity as a share of total capital

Who owns JANUS OMSORG AS?

JANUS OMSORG AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about JANUS OMSORG AS

Who owns JANUS OMSORG AS?

MAESER AS is the largest registered owner, with 20.0%.

What is the revenue of JANUS OMSORG AS?

JANUS OMSORG AS had revenue of NOK 32.7m in 2025.

Who is the general manager of JANUS OMSORG AS?

Reidun Bartnes Kveen is registered as general manager of JANUS OMSORG AS.

Where is JANUS OMSORG AS based?

JANUS OMSORG AS has its business address in Åros.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.