Institution record
RoboForex
- Source score
- 6.9
- Source exposures
- 0
- Comments
- 0
Licence records
Licences within our coverage (decentralised trading protocols, nft marketplaces and web3 execution venues) are listed first. Check each one on the regulator's own register.
| Regulator | Licence no. | Status | Licensed entity | Date | |
|---|---|---|---|---|---|
In our coverage Cyprus Securities and Exchange Commission | 191/13 | Regulated | Robomarkets Ltd | 2013-01-30 | |
In our coverage National Bank of the Republic of Belarus | 193179482 | Regulated | RoboMarkets | 2019-04-08 | |
In our coverage Polish Financial Supervision Authority | Not supplied | Regulated | Robomarkets Ltd | 2013-10-15 | |
In our coverage Financial Services Commission | 000138/333 | Regulated | RoboForex | — |
Peer source record comparison
Compare imported fields for RoboForex and other records in our decentralised trading protocols, nft marketplaces and web3 execution venues dataset. These are not independent audit findings.
| Institution | Primary regulators | Regulated / total | Risk classification | Source score | Source exposures |
|---|---|---|---|---|---|
| RoboForex (this record) | CYSECNBRBKNF+1 | 4 / 4 | Risk level not supplied | 6.9 | 0 |
CYSECFinancial Services Authority SeychellesBVIFSC+2 | 3 / 5 | Risk level not supplied | 5.0 | 0 | |
Financial Services Authority SeychellesCYSECFinancial Conduct Authority+1 | 3 / 4 | Risk level not supplied | 8.0 | 0 | |
FSCACYSECASIC | 3 / 3 | Risk level not supplied | 5.0 | 0 | |
Financial Services Authority SeychellesCYSECFinancial Conduct Authority | 2 / 3 | Risk level not supplied | 5.0 | 0 | |
Financial Services Authority SeychellesCYSEC | 2 / 2 | Risk level not supplied | 6.0 | 0 |
RoboForex: institutional due diligence FAQ
Key supervisory, licensing, and counterparty verification questions generated from the dataset.
What is RoboForex's regulatory licence status and supervisory authorisation?
The imported dataset contains 4 licence entries associated with RoboForex (legal entity reference: RoboForex); 4 are labelled "regulated" and 4 are labelled regulated or registered: CYSEC (Cyprus Securities and Exchange Commission) — licence 191/13, status: regulated; NBRB (National Bank of the Republic of Belarus) — licence 193179482, status: regulated; KNF (Polish Financial Supervision Authority) — licence Not supplied, status: regulated; Financial Services Commission — licence 000138/333, status: regulated. These fields are not independent confirmation of current authorisation. Check the exact contracting entity and registration number on the official CYSEC, NBRB, KNF public register.
Which of RoboForex's jurisdictions and licences fall within this site's regulatory coverage?
This directory focuses on decentralised trading protocols, nft marketplaces and web3 execution venues. 4 of RoboForex's 4 licence records fall directly within this jurisdictional mandate: CYSEC (licence 191/13, regulated, entity: Robomarkets Ltd); NBRB (licence 193179482, regulated, entity: RoboMarkets); KNF (licence Not supplied, regulated, entity: Robomarkets Ltd); Financial Services Commission (licence 000138/333, regulated, entity: RoboForex). Always confirm whether client money segregation and statutory investor compensation schemes apply to the specific subsidiary onboarding your account.
What is RoboForex's institutional risk classification, enforcement exposure, and score profile?
RoboForex carries a "risk level not supplied" classification in the source dataset, alongside composite 5-dimension ratings out of 10 (overall: 6.9, risk & licensing: 3.0, brand: 7.9, market influence: 5.0, user reputation: 0.0). The imported source lists 0 exposure entries. Because these figures reflect imported source fields rather than primary audit findings, compliance teams should review primary enforcement bulletins directly.
What operational due diligence steps apply to RoboForex's platforms, entity structure, and complaints?
Before allocating capital or executing trades with RoboForex, institutional and retail allocators should: (1) confirm the domain (not supplied in source) against regulator-approved domains to guard against clone firms; (2) verify whether any of the 0 source exposure entries or 0 user comments involve withdrawal restrictions or scope violations; and (3) confirm the dispute-resolution ombudsman tied to CYSEC.