biztrac. BETA
COMPANY REGISTER PROFILE
936222218 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Manufacture of jewellery and related articles

KARDIMA AS

Org. no. 936222218 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 384,000
Operating profit NOK 26,000
Equity NOK 48,000
Incorporated 2025
Share capital NOK 30,000

KARDIMA AS is registered as a limited company in Oslo, Oslo with organisation number 936222218. The business is classified under manufacture of jewellery and related articles (NACE 32.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon, design, bearbeiding, innkjøp og salg av smykker laget av gull, sølv, diamanter og andre edelstener, samt annen virksomhet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 384,000 in revenue and NOK 26,000 in operating profit.

Key figures · 2025

Revenue
NOK 384,000
Operating profit
NOK 26,000
Equity
NOK 48,000
Est. value
NOK 126,000

Financial health · 2025

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
37.4%
Weak
Equity as a share of total capital

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

Who owns KARDIMA AS?

KARDIMA AS
NOK 384,000 rev. · NOK 26,000 profit

KARDIMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KARDIMA AS

Who owns KARDIMA AS?

Rafi-Ud-Din Khawaja is the largest registered owner, with 100.0%.

What is the revenue of KARDIMA AS?

KARDIMA AS had revenue of NOK 384,000 in 2025.

Who is the general manager of KARDIMA AS?

Rafi-Ud-Din Khawaja is registered as general manager of KARDIMA AS.

Where is KARDIMA AS based?

KARDIMA AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.