BIZTRAC BETA
Uoppgitt

UPPERCUT HOLDING AS

Org. no. 829497662 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 607,000
Equity NOK 502,000
Incorporated 2022
Share capital NOK 30,000

UPPERCUT HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 829497662. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 607,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 607,000
Equity
NOK 502,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns UPPERCUT HOLDING AS?

DANIEL ALEKSANDER CZEKAJLO
UPPERCUT HOLDING AS
NOK 1.1m rev. · NOK 607,000 profit

UPPERCUT HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does UPPERCUT HOLDING AS own?

UPPERCUT HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about UPPERCUT HOLDING AS

Who owns UPPERCUT HOLDING AS?

DANIEL ALEKSANDER CZEKAJLO is the largest registered owner, with 50.0%.

What is the revenue of UPPERCUT HOLDING AS?

UPPERCUT HOLDING AS had revenue of NOK 1.1m in 2024.

Where is UPPERCUT HOLDING AS based?

UPPERCUT HOLDING 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.