BIZTRAC BETA
Computer consultancy and computer facilities management activities

NATIVE X AS

Org. no. 932691086 Limited company (AS) Holmestrand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 276,000
Operating profit NOK 22,000
Equity NOK 1,000
Incorporated 2023
Share capital NOK 30,000

NATIVE X AS is registered as a limited company in Holmestrand, Vestfold with organisation number 932691086. 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: “Skal selge varer og tjenester innen IT, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 276,000 in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 276,000
Operating profit
NOK 22,000
Equity
NOK 1,000
Est. value
NOK 132,000

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 NATIVE X AS?

ELIE MUTULA NZIGO
NATIVE X AS
NOK 276,000 rev. · NOK 22,000 profit

NATIVE X AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NATIVE X AS

Who owns NATIVE X AS?

ELIE MUTULA NZIGO is the largest registered owner, with 50.0%.

What is the revenue of NATIVE X AS?

NATIVE X AS had revenue of NOK 276,000 in 2025.

Who is the general manager of NATIVE X AS?

Byamungu Kabiraba is registered as general manager of NATIVE X AS.

Where is NATIVE X AS based?

NATIVE X AS has its business address in Holmestrand.

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.