SVP, Corporate Controller · Kezar Life Sciences, Inc. · Kezar Life Sciences, Inc. — Employee Stock Option (right to buy)
Side
D
Value
—
Shares
2,899
Price
—
Executed
May 11, 2026
Disclosed
May 11, 2026
Disclosure timeline0 days from execution to publication · legal deadline 2 business days
May 11 executedMay 11, 2026 disclosed
KZR · daily
Yahoo Finance chart API
◉This trade, on the day it was made▼Disclosure●Material company filing◯Other disclosed buy◯Other disclosed sellUnofficial public endpoint; daily OHLCV, split-adjusted. Replace with a licensed feed for production.
Disposition to issuer — administrative, little informational value
Relative size+1 / 25
No reported dollar value · new position
Filing timing0 / 15
Disclosed 0 business days after execution (deadline: 2)
Historical behavior+8 / 15
First recorded trade by this actor in this security
Frequency & clustering0 / 15
No clustered activity in the dataset
Market events0 / 10
No material company filing within 60 days after the trade
The Insider Score measures how far a disclosure deviates from normal filing patterns. A high score is a prompt for research, not evidence of illegal insider trading.
Kezar Life Sciences, Inc. — Employee Stock Option (right to buy)
Ticker
KZR
Shares
2,899
Price per share
$0
Execution date (reported)
May 11, 2026
Owned after transaction
0 shares
Days from execution to publication
0
What this establishes
Chiang Pichi Luo filed this Form 4 reporting a disposition to issuer of KZR on May 11, 2026. It became public on May 11, 2026. The filing establishes the reported transaction and the filer's stated role. It does not establish why the trade was made or what the filer knew.
Extraction
Method
Form 4 XML
Confidence
1.00
SVP, Corporate Controller
Chiang Pichi Luocik:0002064744
Issuer
Kezar Life Sciences, Inc.cik:0001645666
Revision history · 0
No field has changed since this record was first ingested.
Company events
No records
No material filings recorded for this issuer.
Source error
Price history for KZR is unavailable.
An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.
