SEC reporting owner

Reddy Sundeep G. SEC insider disclosures

Explore Reddy Sundeep G.'s reporting-owner identity, issuer relationships, purchases, sales and SEC filing receipts.

As of 2026-10-07T00:29:11.873Z

Reporting owner CIK
0001747579
Issuers
2
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Reddy Sundeep G.: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2025-06-25
Trade date
2025-06-23
Issuer ticker
CRM
Code
S
Shares
196
Reported value
Not reported
What you should see

The displayed owner or issuer and source fields identify the receipt to verify; keep reporting and availability dates separate.

Step 2 of 3

Which issuer and transaction does this person appear in?

Match the reviewed owner identity, issuer and transaction code. Directory eligibility does not turn every filing into a strategy signal.

SEC accession 0001127602-25-018014
What you should see

Use the linked SEC receipts and company profiles to verify what became public and when.

Step 3 of 3

Browse insider directory

Use the linked SEC receipts and company profiles to verify what became public and when.

Browse insider directory
What you should see

Keep reporting dates and units beside the answer, and inspect its original citations.

Issuer relationships

A reporting-owner CIK identifies the filer across issuer relationships and name aliases. A filer may be an individual or an organization; the filing role is the relevant evidence.

MCKESSON CORP0000927653MCKYesNo
Salesforce, Inc.0001108524CRMYesNo

Recent SEC transactions

See the complete recent sec transactions

Code P identifies a purchase, S a sale and A an award. Awards and open-market purchases describe different events. Use the public availability date when deciding when a researcher could have known about the transaction.

2025-06-252025-06-23CRMS196Not reported
2025-06-252025-06-23CRMS65Not reported
2025-05-062025-05-02CRMS500Not reported
2025-04-252025-04-23CRMS1,112Not reported
2025-04-252025-04-23CRMS221Not reported
2025-04-252025-04-23CRMS192Not reported
2025-04-182025-04-16CRMS1,256Not reported
2025-04-112025-04-09CRMA2,772Not reported
2025-03-262025-03-24CRMS658Not reported
2025-03-262025-03-24CRMS402Not reported
2025-03-262025-03-24CRMS783Not reported
2025-03-262025-03-24CRMS66Not reported
2025-03-262025-03-22CRMA6,917Not reported
2025-03-182025-03-14CRMA2,453Not reported
2025-03-182025-03-14CRMA2,339Not reported
2025-02-052025-02-03CRMS500Not reported
2025-01-242025-01-23CRMS222Not reported
2025-01-242025-01-23CRMS214Not reported
2024-12-242024-12-23CRMS65Not reported
2024-11-052024-11-01CRMS500Not reported
2024-10-242024-10-23CRMS221Not reported
2024-10-242024-10-23CRMS192Not reported

Up to 50 transactions from the recent two-year owner window.

Source evidence and strategy eligibility

The transactions below come from filings; a historical tracker separately simulates following eligible events. Joint filers can report the same transaction, and an owner can have filings at multiple companies. Public availability, amendment lineage and verified coverage determine which events a historical tracker may use.

The current directory marks this owner's filing coverage verified.

Aurora · AI research assistant

Try this in Aurora

Edit the request, then open it in Aurora. You choose when to send it.