BIZTRAC BETA
Intermediation service activities for specialised retail sale

ARNTSEN HELSEIFOKUS AS

Org. no. 931689398 Limited company (AS) Horten Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 749,000
Operating profit NOK 306,000
Equity NOK 599,000
Incorporated 2023
Share capital NOK 30,000

ARNTSEN HELSEIFOKUS AS is registered as a limited company in Horten, Vestfold with organisation number 931689398. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Direktesalg av helsekostprodukter og informasjonsformidling om helse.”. The most recent filed accounts, for the 2025 financial year, show NOK 749,000 in revenue and NOK 306,000 in operating profit.

Key figures · 2025

Revenue
NOK 749,000
Operating profit
NOK 306,000
Equity
NOK 599,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns ARNTSEN HELSEIFOKUS AS?

MALIN SANDHÅLAND ARNTSEN
ARNTSEN HELSEIFOKUS AS
NOK 749,000 rev. · NOK 306,000 profit

ARNTSEN HELSEIFOKUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARNTSEN HELSEIFOKUS AS

Who owns ARNTSEN HELSEIFOKUS AS?

MALIN SANDHÅLAND ARNTSEN is the largest registered owner, with 100.0%.

What is the revenue of ARNTSEN HELSEIFOKUS AS?

ARNTSEN HELSEIFOKUS AS had revenue of NOK 749,000 in 2025.

Who is the general manager of ARNTSEN HELSEIFOKUS AS?

Malin Sandhåland Arntsen is registered as general manager of ARNTSEN HELSEIFOKUS AS.

Where is ARNTSEN HELSEIFOKUS AS based?

ARNTSEN HELSEIFOKUS AS has its business address in Horten.

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.