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

MARGARYAN AS

Org. no. 931369490 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 55.5m
Operating profit NOK 996,000
Equity NOK 1.0m
Incorporated 2023
Employees 10
Share capital NOK 500,000

MARGARYAN AS is registered as a limited company in Bergen, Vestland with organisation number 931369490. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023 and has 10 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 55.5m in revenue and NOK 996,000 in operating profit.

Key figures · 2025

Revenue
NOK 55.5m
Operating profit
NOK 996,000
Equity
NOK 1.0m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns MARGARYAN AS?

GURGEN MARGARYAN AS
MARGARYAN AS
NOK 55.5m rev. · NOK 996,000 profit

MARGARYAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARGARYAN AS

Who owns MARGARYAN AS?

GURGEN MARGARYAN AS is the largest registered owner, with 100.0%.

What is the revenue of MARGARYAN AS?

MARGARYAN AS had revenue of NOK 55.5m in 2025.

Who is the general manager of MARGARYAN AS?

Gurgen Margaryan is registered as general manager of MARGARYAN AS.

Where is MARGARYAN AS based?

MARGARYAN AS has its business address in Rådal.

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.