BIZTRAC BETA
Wholesale of clothing and footwear

CAPRI COLLECTION NORGE AS

Org. no. 998703921 Limited company (AS) Elverum Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 281,000
Operating profit NOK 105,000
Equity NOK 228,000
Incorporated 2012
Share capital NOK 30,000

CAPRI COLLECTION NORGE AS is registered as a limited company in Elverum, Innlandet with organisation number 998703921. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av klær, sko og accessoirer som grossist og i butikk, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 281,000 in revenue and NOK 105,000 in operating profit.

Key figures · 2025

Revenue
NOK 281,000
Operating profit
NOK 105,000
Equity
NOK 228,000
Est. value
NOK 490,000

Financial health · 2025

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

Who owns CAPRI COLLECTION NORGE AS?

HÖGFELDT INVEST AB
CAPRI COLLECTION NORGE AS
NOK 281,000 rev. · NOK 105,000 profit

CAPRI COLLECTION NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CAPRI COLLECTION NORGE AS

Who owns CAPRI COLLECTION NORGE AS?

HÖGFELDT INVEST AB is the largest registered owner, with 100.0%.

What is the revenue of CAPRI COLLECTION NORGE AS?

CAPRI COLLECTION NORGE AS had revenue of NOK 281,000 in 2025.

Who is the general manager of CAPRI COLLECTION NORGE AS?

Bo Ulf Högfeldt is registered as general manager of CAPRI COLLECTION NORGE AS.

Where is CAPRI COLLECTION NORGE AS based?

CAPRI COLLECTION NORGE AS has its business address in Elverum.

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.