BIZTRAC BETA
Manufacture of other fabricated metal products n.e.c.

VEPRO AS

Org. no. 959463484 Limited company (AS) Vefsn Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 7.4m
Operating profit NOK 180,000
Equity NOK 5.5m
Incorporated 1990
Employees 7
Share capital NOK 120,000

VEPRO AS is registered as a limited company in Vefsn, Nordland with organisation number 959463484. The business is classified under manufacture of other fabricated metal products n.e.c. (NACE 25.990). The company was incorporated in 1990 and has 7 registered employees. Registered share capital is NOK 120,000, divided into 600 shares. The company's stated purpose is: “Produksjon og salg av ventilasjonsutstyr og andre produkter, samt hva hermed står i forbindelse, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.4m in revenue and NOK 180,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.4m
Operating profit
NOK 180,000
Equity
NOK 5.5m
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns VEPRO AS?

PÅL EIRIK ARNTZEN
VEPRO AS
NOK 7.4m rev. · NOK 180,000 profit

VEPRO AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VEPRO AS own?

VEPRO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VEPRO AS

Who owns VEPRO AS?

PÅL EIRIK ARNTZEN is the largest registered owner, with 56.5%.

What is the revenue of VEPRO AS?

VEPRO AS had revenue of NOK 7.4m in 2025.

Who is the general manager of VEPRO AS?

Pål Eirik Arntzen is registered as general manager of VEPRO AS.

Where is VEPRO AS based?

VEPRO AS has its business address in Mosjøen.

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.