Healthcare entity
market-trends is the sole category represented across all 1 tracked stories. AMT-130 is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. Each carries 2 original sources on average. We currently track 1 Healthcare story that mention AMT-191, all published on March 3, 2026.
Last mentioned: Aug 5, 2026
Entity pulse
Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.
market-trends is the sole category represented across all 1 tracked stories. AMT-130 is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. Each carries 2 original sources on average. We currently track 1 Healthcare story that mention AMT-191, all published on March 3, 2026.
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 4 Healthcare stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Other entities that clear the same relevance threshold in stories also covering AMT-191. Shared-story counts are live from our verified record — not editorial picks.
Type B FDA Meeting Target
Planned follow-up to define Phase III and regulatory path for AMT-130.
AMT-260 Data Readout
Expected clinical data from Phase I/IIa epilepsy study in H1 2026.
Type A FDA Meeting
Discussed AMT-130 approval pathway; alignment not yet reached.
Fiscal Year End
Closed 2025 with $622.5 million in liquidity.
uniQure reported a strong cash position of $622.5 million, extending its operational runway into 2029. While the company continues to seek regulatory alignment with the FDA for its Huntington’s disease candidate AMT-130, it is advancing clinical trials for epilepsy and Fabry disease with key data readouts expected in 2026.
Source: Benzinga · Globenewswire_fr
AMT-191 is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.
