SEC reporting owner

Yandell Keith SEC insider disclosures

Explore Yandell Keith's reporting-owner identity, issuer relationships, purchases, sales and SEC filing receipts.

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

Reporting owner CIK
0001833552
Issuers
1
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Yandell Keith: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-10-05
Trade date
2026-10-01
Issuer ticker
DASH
Code
S
Shares
2,183
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 0001833552-26-000018
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.

DoorDash, Inc.0001792789DASHYesNo

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.

2026-10-052026-10-01DASHS2,183Not reported
2026-09-212026-09-17DASHS2,184Not reported
2026-08-252026-08-20DASHS7,962Not reported
2026-06-252026-06-22DASHA12,432Not reported
2026-06-252026-06-22DASHA37,296Not reported
2026-05-292026-05-26DASHS92Not reported
2026-05-292026-05-26DASHS108Not reported
2026-05-292026-05-26DASHS500Not reported
2026-05-292026-05-26DASHS1,200Not reported
2026-05-292026-05-26DASHS743Not reported
2026-05-232026-05-20DASHS4,227Not reported
2026-04-232026-04-20DASHA30,435Not reported
2026-02-282026-02-25DASHS80Not reported
2026-02-282026-02-25DASHS600Not reported
2026-02-282026-02-25DASHS1,258Not reported
2026-02-282026-02-25DASHS1,520Not reported
2026-02-282026-02-25DASHS200Not reported
2026-02-282026-02-25DASHS40Not reported
2026-02-282026-02-25DASHS160Not reported
2026-02-282026-02-25DASHS160Not reported
2026-02-252026-02-20DASHS4,928Not reported
2025-11-272025-11-25DASHS80Not reported
2025-11-272025-11-25DASHS861Not reported
2025-11-272025-11-25DASHS240Not reported
2025-11-272025-11-25DASHS760Not reported
2025-11-272025-11-25DASHS658Not reported
2025-11-272025-11-25DASHS320Not reported
2025-11-272025-11-25DASHS333Not reported
2025-11-272025-11-25DASHS440Not reported
2025-11-272025-11-25DASHS280Not reported
2025-11-252025-11-20DASHS4,880Not reported
2025-11-252025-11-20DASHS93Not reported
2025-09-052025-09-02DASHS6,999Not reported
2025-09-052025-09-02DASHS5,298Not reported
2025-09-052025-09-02DASHS3,000Not reported
2025-09-052025-09-02DASHS2,337Not reported
2025-09-052025-09-02DASHS400Not reported
2025-08-282025-08-25DASHS1,235Not reported
2025-08-282025-08-25DASHS2,265Not reported
2025-08-282025-08-25DASHS1,588Not reported
2025-08-282025-08-25DASHS200Not reported
2025-08-232025-08-20DASHS144Not reported
2025-08-232025-08-20DASHS4,880Not reported
2025-05-292025-05-23DASHS200Not reported
2025-05-292025-05-23DASHS2,010Not reported
2025-05-292025-05-23DASHS927Not reported
2025-05-292025-05-23DASHS773Not reported
2025-05-292025-05-23DASHS500Not reported
2025-05-292025-05-23DASHS300Not reported
2025-05-292025-05-23DASHS200Not 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.