biztrac. BETA
COMPANY REGISTER PROFILE
930165778 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

CLAWBACK AI AS

Org. no. 930165778 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 263
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CLAWBACK AI AS is registered as a limited company in Oslo, Oslo with organisation number 930165778. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie og forvalte eiendeler i AI løsninger og eierselskap AI relaterte.”.

Former names: ACQUIRED AS

Key figures · 2025

Operating profit
NOK −12,000
▼ −130 %
Equity
NOK 263
▼ −98 %
Est. value
NOK 477

Financial health · 2025

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 CLAWBACK AI AS?

CLAWBACK AI AS
· NOK −12,000 profit

CLAWBACK AI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CLAWBACK AI AS

Who owns CLAWBACK AI AS?

CLAWBACK AS is the largest registered owner, with 100.0%.

Who is the general manager of CLAWBACK AI AS?

Enrique Fernando Araujo Artigas is registered as general manager of CLAWBACK AI AS.

Where is CLAWBACK AI AS based?

CLAWBACK AI 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 03.10.2026.

Report a problem

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