BIZTRAC BETA
Coating of metals

NOT VARMFORZINKING AS

Org. no. 988475076 Limited company (AS) Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 55.9m
Operating profit NOK 6.6m
Equity NOK 11.5m
Incorporated 2005
Employees 30
Share capital NOK 840,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NOT VARMFORZINKING AS is registered as a limited company in Hå, Rogaland with organisation number 988475076. The business is classified under coating of metals (NACE 25.510). The company was incorporated in 2005 and has 30 registered employees. Registered share capital is NOK 840,000, divided into 1000 shares. The company's stated purpose is: “Varmeforzinking av stål.”. The most recent filed accounts, for the 2024 financial year, show NOK 55.9m in revenue and NOK 6.6m in operating profit.

Key figures · 2024

Revenue
NOK 55.9m
Operating profit
NOK 6.6m
Equity
NOK 11.5m
Est. value
NOK 29.7m

Financial health · 2024

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.5%
Good
Equity as a share of total capital

Who owns NOT VARMFORZINKING AS?

NORSK OVERFLATE TEKNIKK AS
NOT VARMFORZINKING AS
NOK 55.9m rev. · NOK 6.6m profit

NOT VARMFORZINKING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOT VARMFORZINKING AS

Who owns NOT VARMFORZINKING AS?

NORSK OVERFLATE TEKNIKK AS is the largest registered owner, with 100.0%.

What is the revenue of NOT VARMFORZINKING AS?

NOT VARMFORZINKING AS had revenue of NOK 55.9m in 2024.

Who is the general manager of NOT VARMFORZINKING AS?

Geir-Ove Salte is registered as general manager of NOT VARMFORZINKING AS.

Where is NOT VARMFORZINKING AS based?

NOT VARMFORZINKING AS has its business address in Nærbø.

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.