BIZTRAC BETA
Activities of agents involved in non-specialised wholesale

PRO VISJON AS

Org. no. 915820689 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK −290,000
Equity NOK 1.4m
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−290k kr).
  • Nylig endring 2026-06-09 Adresseendring registrert 2026-06-09.

PRO VISJON AS is registered as a limited company in Asker, Akershus with organisation number 915820689. The business is classified under activities of agents involved in non-specialised wholesale (NACE 46.190). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 3 shares. The company's stated purpose is: “Selskapets virksomhet er salgstjenester og agenturer, konsulenttjenester, kjøp og salg av varepartier, messevirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK −290,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK −290,000
Equity
NOK 1.4m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns PRO VISJON AS?

No shareholders are registered for PRO VISJON AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about PRO VISJON AS

What is the revenue of PRO VISJON AS?

PRO VISJON AS had revenue of NOK 2.5m in 2024.

Who is the general manager of PRO VISJON AS?

Svein Thore Fossheim is registered as general manager of PRO VISJON AS.

Where is PRO VISJON AS based?

PRO VISJON AS has its business address in Holmsbu.

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.