biztrac. BETA
COMPANY REGISTER PROFILE
936105785 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Intermediation service activities for business support service activities n.e.c.

CYBRET AI AS

Org. no. 936105785 Limited company (AS) Vennesla Incorporated 2025 Active
Operating profit NOK −614,000
Equity NOK −456,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−456k kr).

CYBRET AI AS is registered as a limited company in Vennesla, Agder with organisation number 936105785. The business is classified under intermediation service activities for business support service activities n.e.c. (NACE 82.400). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1200000 shares. The company's stated purpose is: “Å utvikle, eie, forvalte, kommersialisere immaterielle rettigheter knyttet til programvare, systemer, kunstig intelligens og tilhørende digital infrastruktur og tjenester, og det som står i naturlig forbindelse med dette.”.

Former names: NFH 250834 AS

Key figures · 2025

Operating profit
NOK −614,000
Equity
NOK −456,000

Financial health · 2025

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

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

Who owns CYBRET AI AS?

CYBRET AI AS
· NOK −614,000 profit

CYBRET AI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CYBRET AI AS

Who owns CYBRET AI AS?

SECUREAI HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of CYBRET AI AS?

Adrian De Gendt is registered as general manager of CYBRET AI AS.

Where is CYBRET AI AS based?

CYBRET AI AS has its business address in Hægeland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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