SEC reporting owner

Houston Andrew SEC insider disclosures

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

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

Reporting owner CIK
0001734563
Issuers
2
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Houston Andrew: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-10-05
Trade date
2026-10-01
Issuer ticker
DBX
Code
S
Shares
354,300
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 0001734563-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.

DROPBOX, INC.0001467623DBXYesYes
Meta Platforms, Inc.0001326801FB, METANoYes

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-01DBXS354,300Not reported
2026-09-142026-09-10DBXS59,368Not reported
2026-09-142026-09-10DBXS324,432Not reported
2026-06-182026-06-15METAA612Not reported
2026-05-212026-05-18DBXS30,332Not reported
2026-05-192026-05-14DBXS37,498Not reported
2026-04-042026-04-01DBXS111,166Not reported
2026-03-052026-03-02DBXS109,498Not reported
2026-02-052026-02-02DBXS164,502Not reported
2026-01-142026-01-12DBXS23,818Not reported
2026-01-142026-01-09DBXS36,182Not reported
2026-01-072026-01-02DBXS13,305Not reported
2026-01-072026-01-02DBXS79,363Not reported
2025-12-062025-12-03DBXS9,167Not reported
2025-12-042025-12-01DBXS92,000Not reported
2025-11-192025-11-14DBXS101,167Not reported
2025-10-042025-10-01DBXS3,551Not reported
2025-10-042025-10-01DBXS97,616Not reported
2025-09-112025-09-08DBXS45,835Not reported
2025-09-052025-09-02DBXS92,000Not reported
2025-08-192025-08-14DBXS92,000Not reported
2025-07-042025-07-01DBXS92,000Not reported
2025-06-192025-06-16METAA600Not reported
2025-06-142025-06-11DBXS135,000Not reported
2025-06-142025-06-11DBXS184,000Not reported
2025-01-242025-01-21DBXS80,499Not reported
2025-01-092025-01-06DBXS29,917Not reported
2025-01-072025-01-03DBXS4,257Not reported
2025-01-072025-01-02DBXS500,323Not reported
2024-12-142024-12-11DBXS137,499Not reported
2024-12-052024-12-02DBXS132,000Not reported
2024-11-262024-11-22DBXS4,940Not reported
2024-11-262024-11-21DBXS147,085Not reported
2024-11-192024-11-15DBXS13,444Not reported
2024-11-192024-11-14DBXS624,533Not 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.