SEC reporting owner

Parang Touraj SEC insider disclosures

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

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

Reporting owner CIK
0001983441
Issuers
1
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Parang Touraj: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-10-06
Trade date
2026-10-02
Issuer ticker
SERV
Code
A
Shares
241,252
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 0001983441-26-000018
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.

Serve Robotics Inc. /DE/0001832483SERVYesYes

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-10-062026-10-02SERVA241,252Not reported
2026-08-202026-08-18SERVS19,810Not reported
2026-08-202026-08-18SERVS18,183Not reported
2026-06-122026-06-10SERVS4,219Not reported
2026-05-092026-05-07SERVS3,888Not reported
2026-05-092026-05-06SERVS5,993Not reported
2026-04-102026-04-08SERVS3,861Not reported
2026-03-122026-03-10SERVS3,922Not reported
2026-02-132026-02-11SERVS3,558Not reported
2026-02-062026-02-04SERVS5,998Not reported
2026-01-102026-01-08SERVS4,008Not reported
2025-12-162025-12-12SERVS5,000Not reported
2025-12-162025-12-11SERVS6,300Not reported
2025-11-072025-11-06SERVS6,100Not reported
2025-11-062025-11-05SERVS9,500Not reported
2025-10-082025-10-07SERVS4,825Not reported
2025-09-092025-09-08SERVS53,690Not reported
2025-08-072025-08-05SERVS5,565Not reported
2025-07-242025-07-22SERVA264,022Not reported
2025-05-082025-05-07SERVS450Not reported
2025-04-102025-04-08SERVS445Not reported
2025-03-212025-03-19SERVS546Not reported
2025-03-012025-02-27SERVS796Not reported
2025-01-112025-01-07SERVS305Not reported
2024-12-212024-12-18SERVS248Not reported
2024-12-102024-12-09SERVS45,473Not reported
2024-12-102024-12-09SERVS4,527Not reported
2024-12-102024-12-06SERVS1,098Not reported
2024-12-102024-12-05SERVS815Not reported
2024-11-282024-11-25SERVS1,365Not reported
2024-11-232024-11-21SERVS105Not reported
2024-11-232024-11-21SERVS140Not 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.