BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

AREMARK SENTER AS

Org. no. 913283783 Limited company (AS) Aremark Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 23.1m
Operating profit NOK 380,000
Equity NOK 1.4m
Incorporated 2014
Employees 12
Share capital NOK 30,000

AREMARK SENTER AS is registered as a limited company in Aremark, Østfold with organisation number 913283783. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2014 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Butikkhandel med dagligvarer, import og eksport av matvarer og nonfood, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.1m in revenue and NOK 380,000 in operating profit.

Key figures · 2024

Revenue
NOK 23.1m
Operating profit
NOK 380,000
Equity
NOK 1.4m
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.5%
Good
Equity as a share of total capital

Who owns AREMARK SENTER AS?

MLL AS
AREMARK SENTER AS
NOK 23.1m rev. · NOK 380,000 profit

AREMARK SENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AREMARK SENTER AS

Who owns AREMARK SENTER AS?

MLL AS is the largest registered owner, with 100.0%.

What is the revenue of AREMARK SENTER AS?

AREMARK SENTER AS had revenue of NOK 23.1m in 2024.

Who is the general manager of AREMARK SENTER AS?

Bjørn Vidar Lihagen is registered as general manager of AREMARK SENTER AS.

Where is AREMARK SENTER AS based?

AREMARK SENTER AS has its business address in Aremark.

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.