BIZTRAC BETA
Computer programming activities

XAMPRO AS

Org. no. 921020856 Limited company (AS) Nordkapp Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 8,000
Incorporated 2018
Share capital NOK 30,000

XAMPRO AS is registered as a limited company in Nordkapp, Finnmark with organisation number 921020856. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Egen utvikling av programvare basert på Xamarin og Net Core for alle plattformer støttet av Xamarin. I tillegg salg av konsulent tjenester innen utvikling av mobile mobile løsninger basert på Xamarin, herunder både server og klient og annet som naturlig faller sammen med dette. ”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 8,000
Est. value
NOK 15,000

Financial health · 2024

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 XAMPRO AS?

STEIN VIDAR KARLSEN
XAMPRO AS
NOK 0 rev. · NOK 0 profit

XAMPRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about XAMPRO AS

Who owns XAMPRO AS?

STEIN VIDAR KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of XAMPRO AS?

XAMPRO AS had revenue of NOK 0 in 2024.

Who is the general manager of XAMPRO AS?

Stein Vidar Karlsen is registered as general manager of XAMPRO AS.

Where is XAMPRO AS based?

XAMPRO AS has its business address in Honningsvåg.

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.