SEC reporting owner

WEBB MAYNARD G JR SEC insider disclosures

Explore WEBB MAYNARD G JR's reporting-owner identity, issuer relationships, purchases, sales and SEC filing receipts.

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

Reporting owner CIK
0001209189
Issuers
7
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

WEBB MAYNARD G JR: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-07-18
Trade date
2026-07-15
Issuer ticker
APP
Code
A
Shares
41
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 0001209189-26-000009
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.

GARTNER INC0000749251ITNoYes
EBAY INC0001065088EBAYYesNo
HYPERION SOLUTIONS CORP0001001113HYSLNoYes
Salesforce, Inc.0001108524CRMNoYes
YAHOO INC0001011006YHOONoYes
VISA INC.0001403161VNoYes
AppLovin Corp0001751008APPNoYes

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-07-182026-07-15APPA41Not reported
2026-07-092026-07-06APPS262Not reported
2026-07-092026-07-06APPS1,140Not reported
2026-07-092026-07-06APPS412Not reported
2026-07-092026-07-06APPS120Not reported
2026-07-092026-07-06APPS138Not reported
2026-07-092026-07-06APPS240Not reported
2026-07-092026-07-06APPS182Not reported
2026-07-092026-07-06APPS202Not reported
2026-07-092026-07-06APPS380Not reported
2026-06-062026-06-05APPS164Not reported
2026-06-062026-06-05APPS320Not reported
2026-06-062026-06-05APPS22Not reported
2026-06-062026-06-05APPS560Not reported
2026-06-062026-06-05APPS210Not reported
2026-06-062026-06-05APPS240Not reported
2026-06-062026-06-05APPS1,160Not reported
2026-06-062026-06-05APPS400Not reported
2026-06-062026-06-03APPA525Not reported
2026-04-182026-04-15APPA37Not reported
2026-02-032026-02-01CRMA1,766Not reported
2026-01-292026-01-27VA861Not reported
2026-01-172026-01-15APPA28Not reported
2025-10-182025-10-15APPA29Not reported
2025-06-072025-06-04APPA720Not reported
2025-04-122025-04-09APPA1,818Not reported
2025-02-042025-02-01CRMA1,097Not reported
2025-01-302025-01-28VA777Not 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.