biztrac. BETA
COMPANY REGISTER PROFILE
986471650 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Work training and permanently adapted work

HAG VEKST AS

Org. no. 986471650 Limited company (AS) Grane Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 562,000
Equity NOK 13.2m
Incorporated 2004
Employees 5
Share capital NOK 135,000

HAG VEKST AS is registered as a limited company in Grane, Nordland with organisation number 986471650. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 2004 and has 5 registered employees. Registered share capital is NOK 135,000, divided into 135 shares. The company's stated purpose is: “Salg av tjenester innen utprøvingsarbeid av yrkeshemmede, produksjon og salg av brensel og trevareprodukter, samt annen virksomhet som naturlig faller inn under disse felt.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 562,000 in operating profit.

Former names: GRANE BEDRIFTSSERVICE AS

Key figures · 2025

Revenue
NOK 5.5m
▲ +6 %
Operating profit
NOK 562,000
▼ −3 %
Equity
NOK 13.2m
▲ +5 %
Est. value
NOK 10.7m

Financial health · 2025

Liquidity
13.87
Very good
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
75.8%
Very good
Equity as a share of total capital

Who owns HAG VEKST AS?

No shareholders are registered for HAG VEKST AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HAG VEKST AS

What is the revenue of HAG VEKST AS?

HAG VEKST AS had revenue of NOK 5.5m in 2025.

Who is the general manager of HAG VEKST AS?

Åge Bernt Stabbforsmo is registered as general manager of HAG VEKST AS.

Where is HAG VEKST AS based?

HAG VEKST AS has its business address in Trofors.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.