BIZTRAC BETA
Practical assistance in the home

METTES OMSORG AS

Org. no. 921667116 Limited company (AS) Namsos Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 521,000
Operating profit NOK 48,000
Equity NOK 153,000
Incorporated 2018
Share capital NOK 30,000

METTES OMSORG AS is registered as a limited company in Namsos, Trøndelag with organisation number 921667116. The business is classified under practical assistance in the home (NACE 88.101). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Helsetjenester, hjemmehjelp, rengjøring og ledsagelse og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 521,000 in revenue and NOK 48,000 in operating profit.

Key figures · 2025

Revenue
NOK 521,000
Operating profit
NOK 48,000
Equity
NOK 153,000
Est. value
NOK 341,000

Financial health · 2025

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

Who owns METTES OMSORG AS?

METTE RYGH MYREN
METTES OMSORG AS
NOK 521,000 rev. · NOK 48,000 profit

METTES OMSORG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about METTES OMSORG AS

Who owns METTES OMSORG AS?

METTE RYGH MYREN is the largest registered owner, with 100.0%.

What is the revenue of METTES OMSORG AS?

METTES OMSORG AS had revenue of NOK 521,000 in 2025.

Who is the general manager of METTES OMSORG AS?

Mette Rygh Myren is registered as general manager of METTES OMSORG AS.

Where is METTES OMSORG AS based?

METTES OMSORG AS has its business address in Bangsund.

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.