biztrac. BETA
COMPANY REGISTER PROFILE
993992194 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

CHOLI COLLECTION AS

Org. no. 993992194 Limited company (AS) Bærum Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK 533,000
Equity NOK 2.8m
Incorporated 2009
Employees 6
Share capital NOK 550,000

CHOLI COLLECTION AS is registered as a limited company in Bærum, Akershus with organisation number 993992194. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2009 and has 6 registered employees. Registered share capital is NOK 550,000, divided into 100 shares. The company's stated purpose is: “Import og salg av manufaktur og accessories/produkter som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 533,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
▲ +13 %
Operating profit
NOK 533,000
▲ +321 %
Equity
NOK 2.8m
▲ +18 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
2.71
Very good
Current assets ÷ current liabilities
Profitability
13.2%
Good
Return on total assets
Solidity
63.4%
Very good
Equity as a share of total capital

Who owns CHOLI COLLECTION AS?

CHOLI COLLECTION AS
NOK 9.4m rev. · NOK 533,000 profit

CHOLI COLLECTION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHOLI COLLECTION AS

Who owns CHOLI COLLECTION AS?

Toril Opsal Thorp is the largest registered owner, with 100.0%.

What is the revenue of CHOLI COLLECTION AS?

CHOLI COLLECTION AS had revenue of NOK 9.4m in 2025.

Who is the general manager of CHOLI COLLECTION AS?

Toril Opsal Thorp is registered as general manager of CHOLI COLLECTION AS.

Where is CHOLI COLLECTION AS based?

CHOLI COLLECTION AS has its business address in Hosle.

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.