BIZTRAC BETA
Nursing care activities in nursing homes

FOLLO OMSORGSSERVICE AS

Org. no. 988037680 Limited company (AS) Ås Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 608,000
Operating profit NOK 254,000
Equity NOK 7.5m
Incorporated 2005
Share capital NOK 100,000

FOLLO OMSORGSSERVICE AS is registered as a limited company in Ås, Akershus with organisation number 988037680. The business is classified under nursing care activities in nursing homes (NACE 87.102). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og salg av omsorgsplasser og annen virksomhet som står i forbindelse dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 608,000 in revenue and NOK 254,000 in operating profit.

Key figures · 2024

Revenue
NOK 608,000
Operating profit
NOK 254,000
Equity
NOK 7.5m
Est. value
NOK 5.5m

Financial health · 2024

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

Who owns FOLLO OMSORGSSERVICE AS?

TORGRIM TOLLAG TOLLAKSEN RØISELAND
FOLLO OMSORGSSERVICE AS
NOK 608,000 rev. · NOK 254,000 profit

FOLLO OMSORGSSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOLLO OMSORGSSERVICE AS

Who owns FOLLO OMSORGSSERVICE AS?

TORGRIM TOLLAG TOLLAKSEN RØISELAND is the largest registered owner, with 100.0%.

What is the revenue of FOLLO OMSORGSSERVICE AS?

FOLLO OMSORGSSERVICE AS had revenue of NOK 608,000 in 2024.

Who is the general manager of FOLLO OMSORGSSERVICE AS?

Torgrim Tollag Tollaksen Røiseland is registered as general manager of FOLLO OMSORGSSERVICE AS.

Where is FOLLO OMSORGSSERVICE AS based?

FOLLO OMSORGSSERVICE AS has its business address in Ås.

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.