SEC reporting owner

Chu Maggie SEC insider disclosures

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

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

Reporting owner CIK
0001872974
Issuers
2
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Chu Maggie: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-09-08
Trade date
2026-09-03
Issuer ticker
LFUS
Code
A
Shares
5
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 0001872974-26-000021
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.

LITTELFUSE INC /DE0000889331LFUSYesNo
ITT INC.0000216228ITTNoYes

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-09-082026-09-03LFUSA5Not reported
2026-06-092026-06-04LFUSA6Not reported
2026-06-042026-05-21ITTA935Not reported
2026-05-272026-05-21ITTA909Not reported
2026-05-222026-05-20LFUSS63Not reported
2026-05-222026-05-20LFUSS2,408Not reported
2026-05-222026-05-20LFUSS8,926Not reported
2026-05-012026-04-30LFUSS282Not reported
2026-05-012026-04-28LFUSS498Not reported
2026-05-012026-04-28LFUSS317Not reported
2026-04-252026-04-22LFUSA1,084Not reported
2026-03-102026-03-05LFUSA6Not reported
2026-02-062026-02-04LFUSS2,061Not reported
2025-12-092025-12-05LFUSA7Not reported
2025-09-092025-09-05LFUSA7Not reported
2025-06-102025-06-05LFUSA8Not reported
2025-05-242025-05-21ITTA1,040Not reported
2025-04-292025-04-24LFUSA2,421Not reported
2025-01-282025-01-23LFUSA1,774Not 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.