biztrac. BETA
COMPANY REGISTER PROFILE
835909832 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of other new goods

CG COLLECTION AS

Org. no. 835909832 Limited company (AS) Skien Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 893,000
Operating profit NOK 18,000
Equity NOK 39,000
Incorporated 2025
Share capital NOK 30,000

CG COLLECTION AS is registered as a limited company in Skien, Telemark with organisation number 835909832. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Nettbutikk og streaming med salg av Pokémon, rettet mot samlere og hobbyentusiaster.”. The most recent filed accounts, for the 2025 financial year, show NOK 893,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 893,000
Operating profit
NOK 18,000
Equity
NOK 39,000
Est. value
NOK 90,000

Financial health · 2025

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
20.6%
Weak
Equity as a share of total capital

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

Who owns CG COLLECTION AS?

CG COLLECTION AS
NOK 893,000 rev. · NOK 18,000 profit

CG COLLECTION AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CG COLLECTION AS

Who owns CG COLLECTION AS?

Glenn Thomas Jensen is the largest registered owner, with 50.0%.

What is the revenue of CG COLLECTION AS?

CG COLLECTION AS had revenue of NOK 893,000 in 2025.

Who is the general manager of CG COLLECTION AS?

Christopher Kullvik Endresen is registered as general manager of CG COLLECTION AS.

Where is CG COLLECTION AS based?

CG COLLECTION AS has its business address in Skien.

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.