BIZTRAC BETA
Other unspecified social services without accommodation

TRO OMSORG AS

Org. no. 924850418 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK 1.7m
Equity NOK 6.0m
Incorporated 2020
Employees 10
Share capital NOK 30,000

TRO OMSORG AS is registered as a limited company in Asker, Akershus with organisation number 924850418. The business is classified under other unspecified social services without accommodation (NACE 88.996). The company was incorporated in 2020 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby bo- og omsorgstjenester til kommuner, bydeler, fylkeskommuner, spesialisttjenester eller privatpersoner samt det som naturlig står i forbindelse med dette, herunder deltagelse i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK 1.7m
Equity
NOK 6.0m
Est. value
NOK 10.5m

Financial health · 2024

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

Who owns TRO OMSORG AS?

F.O HOLDING AS
TRO OMSORG AS
NOK 6.3m rev. · NOK 1.7m profit

TRO OMSORG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRO OMSORG AS

Who owns TRO OMSORG AS?

F.O HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TRO OMSORG AS?

TRO OMSORG AS had revenue of NOK 6.3m in 2024.

Who is the general manager of TRO OMSORG AS?

Frank Opperud is registered as general manager of TRO OMSORG AS.

Where is TRO OMSORG AS based?

TRO OMSORG AS has its business address in Vettre.

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.