Cybersecurity entity

Craneware plc

Company CRW.L

All 1 tracked stories fall under one category: data-breach. Hackers is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. The tracked stories average 2 original sources each. Craneware plc appears in 1 tracked Cybersecurity story from July 20, 2026.

Last mentioned: Jul 20, 2026

Entity pulse

Recent coverage · Craneware plc

1 story
8 avg impact
0% positive
100% negative

Coverage balance Negative coverage leads. Negative coverage exceeds positive coverage by 100 percentage points.

  • 100% negative

Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.

What the coverage shows about Craneware plc

All 1 tracked stories fall under one category: data-breach. Hackers is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. The tracked stories average 2 original sources each. Craneware plc appears in 1 tracked Cybersecurity story from July 20, 2026.

Stories tracked
1
Sources per story
2

Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 7 Cybersecurity stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.

Coverage cohort

Appears alongside

Other entities that clear the same relevance threshold in stories also covering Craneware plc. Shared-story counts are live from our verified record — not editorial picks.

Key Data

ticker
CRW.L
name
Craneware plc
price
2175
change
-145
changePct
-6.25

Timeline

  1. Breach Disclosure

    Craneware files a statement with the London Stock Exchange revealing a cyberattack in which a 'significant volume' of data was exfiltrated, and that the hackers have been expelled.

Stories mentioning Craneware plc 1

Craneware plc 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.