BIZTRAC BETA
Other technical consultancy

HELGELAND V&M AS

Org. no. 993551856 Limited company (AS) Alstahaug Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK −273,000
Equity NOK −77,000
Incorporated 2008
Share capital NOK 700,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−77k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−273k kr).

HELGELAND V&M AS is registered as a limited company in Alstahaug, Nordland with organisation number 993551856. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2008. Registered share capital is NOK 700,000, divided into 1750 shares. The company's stated purpose is: “Petroleumsrelatert virksomhet, og deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK −273,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK −273,000
Equity
NOK −77,000

Financial health · 2024

Liquidity
0.92
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4.5%
Weak
Equity as a share of total capital

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

Who owns HELGELAND V&M AS?

OCEAN TECHNOLOGY AS
HELGELAND V&M AS
NOK 3.7m rev. · NOK −273,000 profit

HELGELAND V&M AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELGELAND V&M AS

Who owns HELGELAND V&M AS?

OCEAN TECHNOLOGY AS is the largest registered owner, with 90.1%.

What is the revenue of HELGELAND V&M AS?

HELGELAND V&M AS had revenue of NOK 3.7m in 2024.

Who is the general manager of HELGELAND V&M AS?

Jan Tore Bø is registered as general manager of HELGELAND V&M AS.

Where is HELGELAND V&M AS based?

HELGELAND V&M AS has its business address in Sandnessjø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.