BIZTRAC BETA
Manufacture of imitation jewellery and related articles

ILDA CARE AS

Org. no. 923709037 Limited company (AS) Horten Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK −32,000
Incorporated 2019
Share capital NOK 43,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−32k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

ILDA CARE AS is registered as a limited company in Horten, Vestfold with organisation number 923709037. The business is classified under manufacture of imitation jewellery and related articles (NACE 32.130). The company was incorporated in 2019. Registered share capital is NOK 43,000, divided into 429 shares. The company's stated purpose is: “Utvikling, produksjon og salg av smykker med integrert informasjon om brukeren, samt tilhørende digitale plattformer og tjenester, og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK −32,000

Financial health · 2025

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-312.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ILDA CARE AS?

CAMILLA JOHANSEN VICTOR
ILDA CARE AS
NOK 0 rev. · NOK −26,000 profit

ILDA CARE AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about ILDA CARE AS

Who owns ILDA CARE AS?

CAMILLA JOHANSEN VICTOR is the largest registered owner, with 66.7%.

What is the revenue of ILDA CARE AS?

ILDA CARE AS had revenue of NOK 0 in 2025.

Where is ILDA CARE AS based?

ILDA CARE AS has its business address in Horten.

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.