SIC Relationship Intelligence
Ownership, Politics & Transport Graph
Trace companies, beneficial ownership claims, directors, politicians, vessels, aircraft and source-verified movement records. Every edge retains its dataset and confidence.
Graph focus
Koļesņikovs Sergejs
Relationships, source records & discovery leads
All 10 relationships in the connected, loaded graph sample are shown below, not the complete network. 2 touch this record directly; 8 describe further network context, not direct relationships to this subject. Includes unconfirmed leads, labelled separately. Read each row from subject to counterpart. Accounting consolidation is not a claim of equity ownership. A relationship does not transfer sanctions status or establish wrongdoing.
- Direct rows
- 2
- Source-attributed rows
- 5
- Unconfirmed leads
- 5
- Named source datasets
- 4
Sources represented: lv_ur_beneficial_owners · lv_ur_members · lv_ur_name_candidates · lv_ur_officers. Counts describe this displayed sample, not all records or all possible chains.
| Subject | Relationship | Counterpart | Dates & evidence |
|---|---|---|---|
| Koļesņikovs Sergejs | Possible identity match — distinct recordsDirect to this recordDiscovery lead — unconfirmed | Kolesnikovs Sergejs — possible shared identity | Current status not supplied
|
| Koļesņikovs Sergejs | Director ofDirect to this recordSource-attributed relationship | SIA "VKM STORAGE" | Current status not supplied
|
| Koļesņikovs Sergejs | Possible identity match — distinct recordsFurther network contextDiscovery lead — unconfirmed | Kolesnikovs Sergejs — possible shared identity | Current status not supplied
|
| Koļesņikovs Sergejs | Possible identity match — distinct recordsFurther network contextDiscovery lead — unconfirmed | Kolesnikovs Sergejs — possible shared identity | Current status not supplied
|
| Koļesņikovs Sergejs | Possible identity match — distinct recordsFurther network contextDiscovery lead — unconfirmed | Kolesnikovs Sergejs — possible shared identity | Current status not supplied
|
| Kolesnikovs Sergejs | Possible identity match — distinct recordsFurther network contextDiscovery lead — unconfirmed | Kolesnikovs Sergejs — possible shared identity | Current status not supplied
|
| Vadims Harunžijs | Reported beneficial owner ofFurther network contextSource-attributed relationship | SIA "VKM STORAGE" | Current status not supplied
|
| Vladimirs Šapovals | Reported beneficial owner ofFurther network contextSource-attributed relationship | SIA "VKM STORAGE" | Current status not supplied
|
| Harunžijs Vadims | Member ofFurther network contextSource-attributed relationship | SIA "VKM STORAGE" | Current status not suppliedFrom: 2026-05-19
|
| SIA "Elektrodarbi" | Member ofFurther network contextSource-attributed relationship | SIA "VKM STORAGE" | Current status not suppliedFrom: 2026-05-19
|
Network intelligence10 loaded links · 5 discovery candidates
Relationship signals
Broad discovery graph with explicit confidence tiers. Candidate links never create a sanctions status.
1. Discover
Start broad; dashed lines are possible links, not established facts.
Start broad; dashed lines are possible links, not established facts.
2. Inspect
Select a line to see its confidence and matching reasons.
Select a line to see its confidence and matching reasons.
3. Tighten
Optionally narrow to source-attributed relationships.
Optionally narrow to source-attributed relationships.
Loaded entities
11
11 visible
Loaded links
10
2 direct
Source datasets
4
in this network
Discovery candidates
5
explicitly marked, not discarded
Politician / PEPOfficial sanctions recordAircraftVesselMovement recordsOfficial travel filingPolitical committeeFARA disclosurePossible link
Movement records identify an aircraft or vessel, not its passengers. Ownership and control links require verification against the cited official record before use.
Evidence corridors
Paths to source-list records
Bounded search of the server graph, up to four hops and 48 steps per frontier entity. Source-attributed mode. A route never transfers an official status by proximity.
No route returned within this bounded four-hop search. This does not establish that no connection exists. Try broad discovery to include weaker leads.