BIZTRAC BETA
Other software publishing

VSP AS

Org. no. 988676772 Limited company (AS) Ålesund Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 32.3m
Operating profit NOK 4.8m
Equity NOK 4.4m
Incorporated 2005
Employees 20
Share capital NOK 100,000

VSP AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 988676772. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2005 and has 20 registered employees. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Salg av sikkerhetsløsninger og andre produkter som naturlig faller sammen med dette samt salg av konsulenttjenester, generell varehandel og investering i eiendom og andre selskap. Herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 32.3m in revenue and NOK 4.8m in operating profit.

Key figures · 2024

Revenue
NOK 32.3m
Operating profit
NOK 4.8m
Equity
NOK 4.4m
Est. value
NOK 27.4m

Financial health · 2024

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.3%
Satisfactory
Equity as a share of total capital

Who owns VSP AS?

BOND HOLDING AS
VSP AS
NOK 32.3m rev. · NOK 4.8m profit

VSP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VSP AS

Who owns VSP AS?

BOND HOLDING AS is the largest registered owner, with 82.5%.

What is the revenue of VSP AS?

VSP AS had revenue of NOK 32.3m in 2024.

Who is the general manager of VSP AS?

Bernt Åsmund Indresøvde is registered as general manager of VSP AS.

Where is VSP AS based?

VSP AS has its business address in Ålesund.

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.