BIZTRAC BETA
Retail sale of other food

EIDSVOLL HELSEKOST SUNDET AS

Org. no. 924317302 Limited company (AS) Eidsvoll Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 8,000
Equity NOK 393,000
Incorporated 2019
Share capital NOK 126,000

EIDSVOLL HELSEKOST SUNDET AS is registered as a limited company in Eidsvoll, Akershus with organisation number 924317302. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2019. Registered share capital is NOK 126,000, divided into 126 shares. The company's stated purpose is: “Butikkhandel med helsekost og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 8,000
Equity
NOK 393,000
Est. value
NOK 229,000

Financial health · 2025

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

Who owns EIDSVOLL HELSEKOST SUNDET AS?

THOMAS MIKAEL ANDREJ OLSSON
EIDSVOLL HELSEKOST SUNDET AS
NOK 1.8m rev. · NOK 8,000 profit

EIDSVOLL HELSEKOST SUNDET AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about EIDSVOLL HELSEKOST SUNDET AS

Who owns EIDSVOLL HELSEKOST SUNDET AS?

THOMAS MIKAEL ANDREJ OLSSON is the largest registered owner, with 43.7%.

What is the revenue of EIDSVOLL HELSEKOST SUNDET AS?

EIDSVOLL HELSEKOST SUNDET AS had revenue of NOK 1.8m in 2025.

Who is the general manager of EIDSVOLL HELSEKOST SUNDET AS?

Thomas Mikael Andrej Olsson is registered as general manager of EIDSVOLL HELSEKOST SUNDET AS.

Where is EIDSVOLL HELSEKOST SUNDET AS based?

EIDSVOLL HELSEKOST SUNDET AS has its business address in Eidsvoll.

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.