Read one actual disclosure before using it
Scroll sideways to compare all columns. Select a heading to sort.
| 2026-07-15 | 2026-07-13 | LRCX | S | 18,282 | Not reported |
No matching rows. Clear the filter to see all records.
First displayed source row from Recent SEC transactions. The full bounded history and coverage notes remain below.
The displayed observation date is 2026-07-13 and its public availability date is 2026-07-15. Subtracting those calendar dates gives 2 days of disclosure lag. Historical public research can use the record from the availability date, rather than backdating knowledge to the observation date. The calendar-day difference does not assert an intraday publication time.
This row is code S: a sale. A purchase-following rule excludes this sale even if the reported dollar amount is large.
Open the linked original receipts to verify the row, then inspect a second record before drawing a pattern. This public filing observation supplies source evidence, not a completed copy-trading return.
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.
Scroll sideways to compare all columns. Select a heading to sort.
| LSI CORP | 0000703360 | LSI | Yes | Yes |
| LAM RESEARCH CORP | 0000707549 | LRCX | No | Yes |
| iRhythm Holdings, Inc. | 0001388658 | IRTC | No | Yes |
| TE Connectivity plc | 0001385157 | TEL | No | Yes |
| ADVANCED MICRO DEVICES INC | 0000002488 | AMD | No | Yes |
No matching rows. Clear the filter to see all records.
Recent SEC transactions
Inspect all 28 displayed rows: 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.
Scroll sideways to compare all columns. Select a heading to sort.
| 2026-07-15 | 2026-07-13 | LRCX | S | 18,282 | Not reported |
| 2026-05-30 | 2026-05-27 | IRTC | A | 1,573 | Not reported |
| 2026-05-16 | 2026-05-13 | AMD | A | 872 | Not reported |
| 2026-05-13 | 2026-05-11 | IRTC | S | 290 | Not reported |
| 2026-05-13 | 2026-05-11 | IRTC | S | 1,147 | Not reported |
| 2026-05-13 | 2026-05-11 | IRTC | S | 2,293 | Not reported |
| 2026-05-13 | 2026-05-11 | IRTC | S | 642 | Not reported |
| 2026-05-13 | 2026-05-11 | IRTC | S | 940 | Not reported |
| 2026-05-13 | 2026-05-11 | IRTC | P | 5,312 | Not reported |
| 2026-02-25 | 2026-02-23 | IRTC | S | 1,637 | Not reported |
| 2026-02-25 | 2026-02-23 | IRTC | S | 572 | Not reported |
| 2026-02-25 | 2026-02-23 | IRTC | S | 1,725 | Not reported |
| 2026-02-25 | 2026-02-23 | IRTC | S | 1,378 | Not reported |
| 2025-11-15 | 2025-11-13 | TEL | A | 838 | Not reported |
| 2025-11-13 | 2025-11-10 | IRTC | S | 89 | Not reported |
| 2025-11-13 | 2025-11-10 | IRTC | S | 637 | Not reported |
| 2025-11-13 | 2025-11-10 | IRTC | S | 1,300 | Not reported |
| 2025-11-13 | 2025-11-10 | IRTC | S | 1,585 | Not reported |
| 2025-11-13 | 2025-11-10 | IRTC | S | 222 | Not reported |
| 2025-11-13 | 2025-11-10 | IRTC | S | 1,479 | Not reported |
| 2025-11-11 | 2025-11-07 | LRCX | A | 1,635 | Not reported |
| 2025-08-13 | 2025-08-11 | IRTC | S | 2,129 | Not reported |
| 2025-08-13 | 2025-08-11 | IRTC | S | 3,183 | Not reported |
| 2025-05-30 | 2025-05-28 | IRTC | A | 1,358 | Not reported |
| 2025-05-17 | 2025-05-14 | AMD | A | 2,613 | Not reported |
| 2024-11-16 | 2024-11-14 | TEL | A | 1,327 | Not reported |
| 2024-11-13 | 2024-11-08 | LRCX | A | 2,950 | Not reported |
| 2024-11-06 | 2024-11-04 | IRTC | P | 6,664 | Not reported |
No matching rows. Clear the filter to see all records.
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.