Biotech entity
acquisition is the sole category represented across all 1 tracked stories. Of the tracked stories, 1 of 1 also mention Scantox, the most common co-covered peer. We currently track 1 Biotech story that mention DuplexSeq, all published on February 26, 2026.
Last mentioned: Feb 26, 2026
Entity pulse
Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.
acquisition is the sole category represented across all 1 tracked stories. Of the tracked stories, 1 of 1 also mention Scantox, the most common co-covered peer. We currently track 1 Biotech story that mention DuplexSeq, all published on February 26, 2026. Each carries 2 original sources on average.
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 18 Biotech 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 DuplexSeq. Shared-story counts are live from our verified record — not editorial picks.
Integration Phase
Transfer of DuplexSeq equipment and IP to Scantox facilities and staff training.
Acquisition Announced
Scantox officially announces the purchase of TwinStrand's nonclinical genomics safety business.
Full Commercial Launch
Scantox expected to offer full-scale DuplexSeq services as part of its standard safety assessment packages.
Scantox has acquired the DuplexSeq™ nonclinical genomics safety business from TwinStrand Biosciences, integrating ultra-sensitive sequencing technology into its pre-clinical service suite. This strategic move positions Scantox as a leader in high-resolution genetic toxicology, offering pharmaceutical clients unprecedented accuracy in identifying mutagenic risks.
DuplexSeq 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.
