BIZTRAC BETA
Retail sale of information and communication equipment

IT CARE AS

Org. no. 988835986 Limited company (AS) Åsnes Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK 791,000
Equity NOK 428,000
Incorporated 2005
Employees 8
Share capital NOK 750,000

IT CARE AS is registered as a limited company in Åsnes, Innlandet with organisation number 988835986. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2005 and has 8 registered employees. Registered share capital is NOK 750,000, divided into 750 shares. The company's stated purpose is: “Kjøp, salg og reparasjoner av datautstyr, rådgivning innen butikkdrift, kjøp og salg av forretninger og bedrifter, import og eksport av varepartier, engrossalg av butikkvarer, detaljsalg av butikkvarer, kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK 791,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.9m
Operating profit
NOK 791,000
Equity
NOK 428,000
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns IT CARE AS?

PER ÅGE MATHISEN BRÅTEN
IT CARE AS
NOK 12.9m rev. · NOK 791,000 profit

IT CARE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about IT CARE AS

Who owns IT CARE AS?

PER ÅGE MATHISEN BRÅTEN is the largest registered owner, with 53.3%.

What is the revenue of IT CARE AS?

IT CARE AS had revenue of NOK 12.9m in 2025.

Who is the general manager of IT CARE AS?

Per Åge Mathisen Bråten is registered as general manager of IT CARE AS.

Where is IT CARE AS based?

IT CARE AS has its business address in Flisa.

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.