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

SIMON MASHOLY AS

Org. no. 920193692 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 115.5m
Operating profit NOK 1.3m
Equity NOK 3.8m
Incorporated 2017
Employees 23
Share capital NOK 500,000

SIMON MASHOLY AS is registered as a limited company in Oslo, Oslo with organisation number 920193692. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2017 and has 23 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjenom 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 115.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 115.5m
Operating profit
NOK 1.3m
Equity
NOK 3.8m
Est. value
NOK 6.8m

Financial health · 2025

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

Who owns SIMON MASHOLY AS?

SIMON MASHOLY
SIMON MASHOLY AS
NOK 115.5m rev. · NOK 1.3m profit

SIMON MASHOLY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIMON MASHOLY AS

Who owns SIMON MASHOLY AS?

SIMON MASHOLY is the largest registered owner, with 100.0%.

What is the revenue of SIMON MASHOLY AS?

SIMON MASHOLY AS had revenue of NOK 115.5m in 2025.

Who is the general manager of SIMON MASHOLY AS?

Simon Masholy is registered as general manager of SIMON MASHOLY AS.

Where is SIMON MASHOLY AS based?

SIMON MASHOLY AS has its business address in Oslo.

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.