BIZTRAC BETA
Retail sale of watches and jewellery

UCCASIO AS

Org. no. 928229092 Limited company (AS) Ullensaker Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK −27,000
Equity NOK −109,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

UCCASIO AS is registered as a limited company in Ullensaker, Akershus with organisation number 928229092. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av smykker over nett, og all virksomhet som naturlig står i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK −27,000
Equity
NOK −109,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns UCCASIO AS?

PERKASH SINGH
UCCASIO AS
NOK 5,000 rev. · NOK −27,000 profit

UCCASIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UCCASIO AS

Who owns UCCASIO AS?

PERKASH SINGH is the largest registered owner, with 100.0%.

What is the revenue of UCCASIO AS?

UCCASIO AS had revenue of NOK 5,000 in 2025.

Who is the general manager of UCCASIO AS?

Perkash Singh is registered as general manager of UCCASIO AS.

Where is UCCASIO AS based?

UCCASIO AS has its business address in Gardermoen.

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.