BIZTRAC BETA
Coating of metals

VELO GALVANISK ANLEGG AS

Org. no. 965604979 Limited company (AS) Trondheim Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 15.4m
Operating profit NOK 2.3m
Equity NOK 7.4m
Incorporated 1992
Employees 6
Share capital NOK 350,000

VELO GALVANISK ANLEGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 965604979. The business is classified under coating of metals (NACE 25.510). The company was incorporated in 1992 and has 6 registered employees. Registered share capital is NOK 350,000. The company's stated purpose is: “Drive produksjon herunder deltakelse med kapital i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.4m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 15.4m
Operating profit
NOK 2.3m
Equity
NOK 7.4m
Est. value
NOK 11.7m

Financial health · 2025

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

Who owns VELO GALVANISK ANLEGG AS?

VELO HOLDING AS
VELO GALVANISK ANLEGG AS
NOK 15.4m rev. · NOK 2.3m profit

VELO GALVANISK ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VELO GALVANISK ANLEGG AS er morselskap for 1 datterselskap:

Frequently asked questions about VELO GALVANISK ANLEGG AS

Who owns VELO GALVANISK ANLEGG AS?

VELO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VELO GALVANISK ANLEGG AS?

VELO GALVANISK ANLEGG AS had revenue of NOK 15.4m in 2025.

Who is the general manager of VELO GALVANISK ANLEGG AS?

Ove Reitan Becker is registered as general manager of VELO GALVANISK ANLEGG AS.

Where is VELO GALVANISK ANLEGG AS based?

VELO GALVANISK ANLEGG AS has its business address in Trondheim.

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.