SEC reporting owner

Abraham Euan SEC insider disclosures

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

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

Reporting owner CIK
0001983554
Issuers
1
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Abraham Euan: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-03-12
Trade date
2026-03-10
Issuer ticker
SERV
Code
S
Shares
1,390
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 0001983554-26-000008
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.

Serve Robotics Inc. /DE/0001832483SERVYesNo

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-03-122026-03-10SERVS1,390Not reported
2026-02-132026-02-11SERVS1,375Not reported
2026-02-062026-02-04SERVS3,284Not reported
2026-01-102026-01-08SERVS1,171Not reported
2025-12-162025-12-11SERVS1,917Not reported
2025-11-072025-11-06SERVS1,840Not reported
2025-11-062025-11-05SERVS3,915Not reported
2025-10-182025-10-15SERVS25,000Not reported
2025-10-082025-10-07SERVS1,480Not reported
2025-09-232025-09-19SERVS25,000Not reported
2025-09-192025-09-18SERVS8,433Not reported
2025-09-092025-09-08SERVS12,603Not reported
2025-08-072025-08-05SERVS2,130Not reported
2025-07-242025-07-22SERVA126,330Not reported
2025-05-082025-05-07SERVS315Not reported
2025-04-102025-04-08SERVS308Not reported
2025-03-212025-03-19SERVS380Not reported
2025-03-012025-02-27SERVS660Not reported
2025-02-212025-02-18SERVS25,000Not reported
2025-01-112025-01-07SERVS260Not reported
2025-01-032024-12-30SERVS40Not reported
2024-12-212024-12-18SERVS205Not reported
2024-12-102024-12-05SERVS235Not reported
2024-12-032024-11-27SERVS869Not reported
2024-11-282024-11-25SERVS731Not reported
2024-11-212024-11-18SERVS75,000Not 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.