BIZTRAC BETA
Supply and other sea transport offshore services

VISPRO AS

Org. no. 913222571 Limited company (AS) Dønna Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 28,000
Operating profit NOK −54,000
Equity NOK −501,000
Incorporated 2014
Share capital NOK 40,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−501k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−54k kr).

VISPRO AS is registered as a limited company in Dønna, Nordland with organisation number 913222571. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2014. Registered share capital is NOK 40,000, divided into 400 shares. The company's stated purpose is: “Maritime oppdrag og annen tilliggende virksomhet, samt investeringer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 28,000 in revenue and NOK −54,000 in operating profit.

Key figures · 2024

Revenue
NOK 28,000
Operating profit
NOK −54,000
Equity
NOK −501,000

Financial health · 2024

Liquidity
3.84
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-45.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VISPRO AS?

SKAGEMO MARITIME CONSULTANCY AS
VISPRO AS
NOK 28,000 rev. · NOK −54,000 profit

VISPRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VISPRO AS

Who owns VISPRO AS?

SKAGEMO MARITIME CONSULTANCY AS is the largest registered owner, with 50.0%.

What is the revenue of VISPRO AS?

VISPRO AS had revenue of NOK 28,000 in 2024.

Who is the general manager of VISPRO AS?

Jarl Åge Aaker is registered as general manager of VISPRO AS.

Where is VISPRO AS based?

VISPRO AS has its business address in Dønna.

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.