BIZTRAC BETA
Business and other management consultancy activities

MYSCORE AS

Org. no. 823302762 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK −351,000
Equity NOK 1.3m
Incorporated 2019
Employees 5
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−351k kr).

MYSCORE AS is registered as a limited company in Oslo, Oslo with organisation number 823302762. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Selge tjenester og varer innen opplysningstjener - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK −351,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK −351,000
Equity
NOK 1.3m
Est. value
NOK 7.3m

Financial health · 2024

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

Who owns MYSCORE AS?

NABIL EL MAZARI
MYSCORE AS
NOK 6.3m rev. · NOK −351,000 profit

MYSCORE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MYSCORE AS

Who owns MYSCORE AS?

NABIL EL MAZARI is the largest registered owner, with 51.0%.

What is the revenue of MYSCORE AS?

MYSCORE AS had revenue of NOK 6.3m in 2024.

Who is the general manager of MYSCORE AS?

Nabil El Mazari is registered as general manager of MYSCORE AS.

Where is MYSCORE AS based?

MYSCORE 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.