SEC reporting owner

Bhutani Amanpal Singh SEC insider disclosures

Explore Bhutani Amanpal Singh's reporting-owner identity, issuer relationships, purchases, sales and SEC filing receipts.

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

Reporting owner CIK
0001753365
Issuers
2
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Bhutani Amanpal Singh: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-10-05
Trade date
2026-10-01
Issuer ticker
GDDY
Code
S
Shares
4,500
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 0001609711-26-000111
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.

NEW YORK TIMES CO0000071691NYTNoYes
GoDaddy Inc.0001609711GDDYYesYes

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-01GDDYS4,500Not reported
2026-09-042026-09-02GDDYS8,194Not reported
2026-09-042026-09-01GDDYS4,500Not reported
2026-08-062026-08-03GDDYS4,500Not reported
2026-07-282026-07-23NYTA98Not reported
2026-06-052026-06-02GDDYS8,373Not reported
2026-04-252026-04-22NYTA2,277Not reported
2026-04-212026-04-16NYTA81Not reported
2026-03-062026-03-04GDDYS34,148Not reported
2026-03-062026-03-03GDDYS5,231Not reported
2026-03-062026-03-03GDDYA84,450Not reported
2026-03-062026-03-03GDDYA85,916Not reported
2026-01-222026-01-16NYTA71Not reported
2025-12-042025-12-02GDDYS6,932Not reported
2025-10-282025-10-23NYTA89Not reported
2025-09-132025-09-10GDDYS6,000Not reported
2025-09-062025-09-03GDDYS6,950Not reported
2025-08-062025-08-01GDDYS3,108Not reported
2025-08-062025-08-01GDDYS2,892Not reported
2025-07-292025-07-24NYTA97Not reported
2025-07-042025-07-02GDDYS300Not reported
2025-07-042025-07-02GDDYS3,850Not reported
2025-07-042025-07-02GDDYS1,850Not reported
2025-06-062025-06-03GDDYS6,932Not reported
2025-06-052025-06-02GDDYS3,000Not reported
2025-05-062025-05-01GDDYS3,000Not reported
2025-05-032025-04-30NYTA3,589Not reported
2025-04-222025-04-17NYTA91Not reported
2025-04-042025-04-01GDDYS3,000Not reported
2025-03-072025-03-05GDDYS58,702Not reported
2025-03-052025-03-03GDDYS3,000Not reported
2025-03-052025-03-01GDDYA129,318Not reported
2025-03-052025-02-28GDDYA49,178Not reported
2025-02-062025-02-03GDDYS3,000Not reported
2025-01-282025-01-23NYTA59Not reported
2025-01-072025-01-02GDDYS3,000Not reported
2024-12-052024-12-03GDDYS6,803Not reported
2024-12-052024-12-02GDDYS3,000Not reported
2024-11-062024-11-01GDDYS3,000Not reported
2024-10-292024-10-24NYTA58Not 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.