BIZTRAC BETA
Uoppgitt

CECTI HOLDING AS

Org. no. 929967569 Limited company (AS) Øvre Eiker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −41,000
Equity NOK 345,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−41k kr).

CECTI HOLDING AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 929967569. 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 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 2025 financial year, show NOK 0 in revenue and NOK −41,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −41,000
Equity
NOK 345,000
Est. value
NOK 405,000

Financial health · 2025

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

Who owns CECTI HOLDING AS?

EIVIND BRENDEN
CECTI HOLDING AS
NOK 0 rev. · NOK −41,000 profit

CECTI HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CECTI HOLDING AS own?

CECTI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CECTI HOLDING AS

Who owns CECTI HOLDING AS?

EIVIND BRENDEN is the largest registered owner, with 60.0%.

What is the revenue of CECTI HOLDING AS?

CECTI HOLDING AS had revenue of NOK 0 in 2025.

Where is CECTI HOLDING AS based?

CECTI HOLDING AS has its business address in Vestfossen.

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.