BIZTRAC BETA
Computer programming activities

PRO VERK AS

Org. no. 920814921 Limited company (AS) Evje Og Hornnes Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −434,000
Equity NOK −444,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−444k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−434k kr).

PRO VERK AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 920814921. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikle og selge dataverktøy for bygge- og anleggsbransjen, herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −434,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −434,000
Equity
NOK −444,000

Financial health · 2024

Liquidity
0.82
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-105.4%
Weak
Equity as a share of total capital

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

Who owns PRO VERK AS?

ERIK SØRENSEN AS
PRO VERK AS
NOK 1.8m rev. · NOK −434,000 profit

PRO VERK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRO VERK AS

Who owns PRO VERK AS?

ERIK SØRENSEN AS is the largest registered owner, with 50.0%.

What is the revenue of PRO VERK AS?

PRO VERK AS had revenue of NOK 1.8m in 2025.

Who is the general manager of PRO VERK AS?

Runar Gautestad is registered as general manager of PRO VERK AS.

Where is PRO VERK AS based?

PRO VERK AS has its business address in Evje.

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.