BIZTRAC BETA
Other content distribution activities

CATEZ AS

Org. no. 923060162 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Revenue 2023 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.
  • Nylig endring 2026-06-23 Under avvikling registrert 2026-06-23.

CATEZ AS is registered as a limited company in Kristiansand, Agder with organisation number 923060162. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen restaurant - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2023 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2023

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 54,000

Financial health · 2023

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

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

Who owns CATEZ AS?

DANIJEL ANDRIJEVIC
CATEZ AS
NOK 0 rev. · NOK 0 profit

CATEZ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CATEZ AS

Who owns CATEZ AS?

DANIJEL ANDRIJEVIC is the largest registered owner, with 100.0%.

What is the revenue of CATEZ AS?

CATEZ AS had revenue of NOK 0 in 2023.

Who is the general manager of CATEZ AS?

Danijel Andrijevic is registered as general manager of CATEZ AS.

Where is CATEZ AS based?

CATEZ AS has its business address in Kristiansand S.

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.