biztrac. BETA
COMPANY REGISTER PROFILE
913034945 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other non-specialised retail sale

VITALIV AS

Org. no. 913034945 Limited company (AS) Gjøvik Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 33.0m
Operating profit NOK 1.6m
Equity NOK 8.3m
Incorporated 2013
Share capital NOK 59,000

VITALIV AS is registered as a limited company in Gjøvik, Innlandet with organisation number 913034945. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2013. Registered share capital is NOK 59,000, divided into 1962 shares. The company's stated purpose is: “Selge helsekostprodukter og naturlegemidler, samt annen virksomhet som faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.0m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 33.0m
▲ +33 %
Operating profit
NOK 1.6m
▼ −33 %
Equity
NOK 8.3m
▲ +8 %
Est. value
NOK 9.2m

Financial health · 2025

Liquidity
2.67
Very good
Current assets ÷ current liabilities
Profitability
16.7%
Very good
Return on total assets
Solidity
64.9%
Very good
Equity as a share of total capital

Who owns VITALIV AS?

ALEXEY GOLOVKIN RU
DANIEL DMITRII BERG VASILEV IL
VITALIV AS
NOK 33.0m rev. · NOK 1.6m profit

VITALIV AS has 3 registered shareholders:

  • ADI INVEST AS 51.0%
  • ALEXEY GOLOVKIN 24.5%
  • DANIEL DMITRII BERG VASILEV 24.5%
All shareholders and roles →

Frequently asked questions about VITALIV AS

Who owns VITALIV AS?

ADI INVEST AS is the largest registered owner, with 51.0%.

What is the revenue of VITALIV AS?

VITALIV AS had revenue of NOK 33.0m in 2025.

Who is the general manager of VITALIV AS?

Adis Arifagic is registered as general manager of VITALIV AS.

Where is VITALIV AS based?

VITALIV AS has its business address in Hunndalen.

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.