BIZTRAC BETA
Computer consultancy and computer facilities management activities

XENIT HOLDING AS

Org. no. 932692937 Limited company (AS) Ullensaker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11
Equity NOK 1.2m
Incorporated 2023
Share capital NOK 30,000

Signals

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

XENIT HOLDING AS is registered as a limited company in Ullensaker, Akershus with organisation number 932692937. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer og investere i virksomheter av enhver art, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11
Equity
NOK 1.2m
Est. value
NOK 11.4m

Financial health · 2025

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

Who owns XENIT HOLDING AS?

ZAHIB AHMAD SIDIQ
XENIT HOLDING AS
NOK 0 rev. · NOK −11 profit

XENIT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does XENIT HOLDING AS own?

XENIT HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about XENIT HOLDING AS

Who owns XENIT HOLDING AS?

ZAHIB AHMAD SIDIQ is the largest registered owner, with 100.0%.

What is the revenue of XENIT HOLDING AS?

XENIT HOLDING AS had revenue of NOK 0 in 2025.

Where is XENIT HOLDING AS based?

XENIT HOLDING AS has its business address in Kløfta.

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.