Vadim Sergeevich Dobrov

Sanctioned
label.subject.scoring_flag.is_high_risk
Last update: 05/06/2026
Name: Vadim Sergeevich Dobrov
Birth: 1963-07-10
Nationality: RUS
Person type: label.person_type.P
Aliases: вадим сергеевич добров
Hide

Sanctions

table.sanction.head.program table.sanction.head.reason
[OFAC.RUSSIA-EO14024] - Russian Harmful Foreign Activities Sanctions Program RUSSIA-EO14024
[CAN.RUSSIA] - Measures against Russia
- (UK Sanctions List Ref):RUS1983. Financial sanctions imposed in addition to an asset freeze: Trust services. Date trust services sanctions imposed: 08/11/2023. (UK Statement of Reasons):Vadim Sergeevi
- Vadim Sergeevich DOBROV is an involved person within the meaning of the Russia (Sanctions) (EU Exit) Regulations 2019 on the following two grounds: DOBROV is or has been obtaining a benefit from or su

Adverse media

Charges

Relationships

Adverse info

Frequently Asked Questions

1. Does Vadim Sergeevich Dobrov have any sanctions?

Yes, Vadim Sergeevich Dobrov is sanctioned by:

2. Can I receive AML sanctions alerts on Vadim Sergeevich Dobrov?

Yes, Pibisi collects sanctions from multiple official AML lists and helps you monitor your customers, providers, or persons of interest.

3. Where does this information come from?

Pibisi's proprietary AML database gathers all of its information from public, official, online AML lists and institutional websites. These are the sources that contain information about Vadim Sergeevich Dobrov:

Name Info Source
Consolidated list of financial sanctions targets Sanctioned GBR-OFSI GBR
Government of Canada Sanctioned CAN
Specially Designated Nationals And Blocked Persons List (SDN) Sanctioned USA-OFAC USA
The information relating to this subject may be incomplete or deliberately obscured. Its use for the creation of user profiles is not permitted. To access the complete information and have an appropriate basis for legitimisation, it is necessary to accredit the status of an Obligated Subject in terms of Money Laundering Prevention and to contract unrestricted access to our database.
Tell us your case