BIZTRAC BETA
Computer consultancy and computer facilities management activities

EXCITO HQ AS

Org. no. 827387142 Limited company (AS) Tønsberg Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 859,000
Incorporated 2021
Share capital NOK 40,000

Signals

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

EXCITO HQ AS is registered as a limited company in Tønsberg, Vestfold with organisation number 827387142. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2021. Registered share capital is NOK 40,000, divided into 4000 shares. The company's stated purpose is: “Eie, forvalte, kjøpe og selge aksjer og eller andre verdipapirer, samt delta i utvikling av prosjekter, og det som faller naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 859,000
Est. value
NOK 13.7m

Financial health · 2025

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

Who owns EXCITO HQ AS?

HÅKON SAMNØY AS
EXCITO HQ AS
NOK 0 rev. · NOK −18,000 profit

EXCITO HQ AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EXCITO HQ AS own?

EXCITO HQ AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EXCITO HQ AS

Who owns EXCITO HQ AS?

HÅKON SAMNØY AS is the largest registered owner, with 79.1%.

What is the revenue of EXCITO HQ AS?

EXCITO HQ AS had revenue of NOK 0 in 2025.

Where is EXCITO HQ AS based?

EXCITO HQ AS has its business address in Barkåker.

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.