BIZTRAC BETA
Uoppgitt

CHUCK INVEST AS

Org. no. 932744112 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK −14,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−14k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

CHUCK INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 932744112. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, selskaper, selskapsandeler og fast eiendom samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK −14,000

Financial health · 2025

Liquidity
2.14
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.8%
Weak
Equity as a share of total capital

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

Who owns CHUCK INVEST AS?

ALEXANDER OLESHCHUK
CHUCK INVEST AS
NOK 0 rev. · NOK −6,000 profit

CHUCK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CHUCK INVEST AS own?

CHUCK INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about CHUCK INVEST AS

Who owns CHUCK INVEST AS?

ALEXANDER OLESHCHUK is the largest registered owner, with 100.0%.

What is the revenue of CHUCK INVEST AS?

CHUCK INVEST AS had revenue of NOK 0 in 2025.

Where is CHUCK INVEST AS based?

CHUCK INVEST 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 15.06.2026.

Report a problem

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