BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

JH VANG AS

Org. no. 914231167 Limited company (AS) Hemnes Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 554,000
Operating profit NOK 101,000
Equity NOK 86,000
Incorporated 2014
Share capital NOK 50,000

JH VANG AS is registered as a limited company in Hemnes, Nordland with organisation number 914231167. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2014. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Yte konsulentbistand knyttet til natur- og miljøforvaltning, registrering og dokumentasjon, bygg og anlegg, tømrerfag, vaktmestertjenester, risiko- og sårbarhetsanalyse, sikkerhet og beredskapsarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 554,000 in revenue and NOK 101,000 in operating profit.

Key figures · 2025

Revenue
NOK 554,000
Operating profit
NOK 101,000
Equity
NOK 86,000
Est. value
NOK 493,000

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.7%
Weak
Equity as a share of total capital

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

Who owns JH VANG AS?

METTE VAREM
JH VANG AS
NOK 554,000 rev. · NOK 101,000 profit

JH VANG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JH VANG AS

Who owns JH VANG AS?

METTE VAREM is the largest registered owner, with 50.0%.

What is the revenue of JH VANG AS?

JH VANG AS had revenue of NOK 554,000 in 2025.

Who is the general manager of JH VANG AS?

John Helge Vang is registered as general manager of JH VANG AS.

Where is JH VANG AS based?

JH VANG AS has its business address in Korgen.

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.