BIZTRAC BETA
Computer consultancy and computer facilities management activities

XANDO AS

Org. no. 922267073 Limited company (AS) Hamar Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 818,000
Incorporated 2019
Share capital NOK 40,000

Signals

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

XANDO AS is registered as a limited company in Hamar, Innlandet with organisation number 922267073. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Konsulent- og rådgivningsvirksomhet innen software, innovasjon og forretningsutvikling, og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet skal også kunne investere i eiendom.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK 818,000
Est. value
NOK 3.5m

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

KIM NEERGAARD SØRENSEN
XANDO AS
· NOK −16,000 profit

XANDO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does XANDO AS own?

XANDO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about XANDO AS

Who owns XANDO AS?

KIM NEERGAARD SØRENSEN is the largest registered owner, with 100.0%.

Who is the general manager of XANDO AS?

Kim Neergaard Sørensen is registered as general manager of XANDO AS.

Where is XANDO AS based?

XANDO AS has its business address in Hamar.

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.