SEC reporting owner

HALEY TIMOTHY M SEC insider disclosures

Explore HALEY TIMOTHY M's reporting-owner identity, issuer relationships, purchases, sales and SEC filing receipts.

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

Reporting owner CIK
0001201583
Issuers
4
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

HALEY TIMOTHY M: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-07-23
Trade date
2026-07-20
Issuer ticker
TDUP
Code
A
Shares
2,491
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 0001628280-26-049190
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.

Scroll sideways to compare all columns. Select a heading to sort.

NETFLIX INC0001065280NFLXNoYes
2U, Inc.0001459417TWOUNoYes
ZUORA INC0001423774ZUONoYes
ThredUp Inc.0001484778TDUPNoYes

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.

Scroll sideways to compare all columns. Select a heading to sort.

2026-07-232026-07-20TDUPA2,491Not reported
2026-05-222026-05-20TDUPA37,265Not reported
2026-04-252026-04-22TDUPA3,836Not reported
2026-02-282026-02-25TDUPA2,432Not reported
2025-06-042025-06-02NFLXA51Not reported
2025-05-232025-05-21TDUPA43,814Not reported
2025-05-032025-05-01NFLXA55Not reported
2025-04-032025-04-01NFLXA67Not reported
2025-03-052025-03-03NFLXA64Not reported
2025-02-052025-02-03NFLXA64Not reported
2025-01-042025-01-02NFLXA71Not reported
2024-12-042024-12-02NFLXA69Not reported
2024-11-132024-11-11NFLXS647Not reported
2024-11-072024-11-05NFLXS100Not reported
2024-11-072024-11-05NFLXS498Not reported
2024-11-072024-11-05NFLXS970Not reported
2024-11-072024-11-05NFLXS1,066Not reported
2024-11-072024-11-05NFLXS7,920Not reported
2024-11-072024-11-05NFLXS536Not reported
2024-11-052024-11-01NFLXA83Not 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.