BIZTRAC BETA
Preventive health care activities

HADSEL VIVO AS

Org. no. 976890426 Limited company (AS) Hadsel Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 1.7m
Equity NOK 2.6m
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-04-13 Adresseendring registrert 2026-04-13.

HADSEL VIVO AS is registered as a limited company in Hadsel, Nordland with organisation number 976890426. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Drive manuell terapi, ultralydundersøkelser og i tillegg vil man drive test og treningslaboratorium, samt utleie av forretningseiendom og det som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 1.7m
Equity
NOK 2.6m
Est. value
NOK 7.7m

Financial health · 2025

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

Who owns HADSEL VIVO AS?

JOSTEIN KRISTEN ELLINGSEN
HADSEL VIVO AS
NOK 2.5m rev. · NOK 1.7m profit

HADSEL VIVO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HADSEL VIVO AS

Who owns HADSEL VIVO AS?

JOSTEIN KRISTEN ELLINGSEN is the largest registered owner, with 100.0%.

What is the revenue of HADSEL VIVO AS?

HADSEL VIVO AS had revenue of NOK 2.5m in 2025.

Who is the general manager of HADSEL VIVO AS?

Jostein Kristen Ellingsen is registered as general manager of HADSEL VIVO AS.

Where is HADSEL VIVO AS based?

HADSEL VIVO AS has its business address in Melbu.

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.