BIZTRAC BETA
Manufacture of knitted and crocheted apparel

KAMI COLLECTION AS

Org. no. 822205852 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 41,000
Operating profit NOK −32,000
Equity NOK 155,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−32k kr).

KAMI COLLECTION AS is registered as a limited company in Stavanger, Rogaland with organisation number 822205852. The business is classified under manufacture of knitted and crocheted apparel (NACE 14.100). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Behagelige arbeidsklær som tar hensyn til utfordringer når det gjelder form og figur.”. The most recent filed accounts, for the 2025 financial year, show NOK 41,000 in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 41,000
Operating profit
NOK −32,000
Equity
NOK 155,000
Est. value
NOK 104,000

Financial health · 2025

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

Who owns KAMI COLLECTION AS?

KIRSTI MERETE STEINNES
KAMI COLLECTION AS
NOK 41,000 rev. · NOK −32,000 profit

KAMI COLLECTION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAMI COLLECTION AS

Who owns KAMI COLLECTION AS?

KIRSTI MERETE STEINNES is the largest registered owner, with 100.0%.

What is the revenue of KAMI COLLECTION AS?

KAMI COLLECTION AS had revenue of NOK 41,000 in 2025.

Who is the general manager of KAMI COLLECTION AS?

Kirsti Merete Steinnes is registered as general manager of KAMI COLLECTION AS.

Where is KAMI COLLECTION AS based?

KAMI COLLECTION AS has its business address in Stavanger.

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.