Finance entity

Lip-Bu Tan

Person

Of the tracked stories, 1 of 2 also mention Advanced Micro Devices, the most common co-covered peer. The 38-day window averages about 0.4 stories each week. They are less corroborated than the beat average, carrying 2 original sources each against 3.3 for the same window.

Last mentioned: Jul 30, 2026

Entity pulse

Recent coverage · Lip-Bu Tan

2 stories
6.5 avg impact
50% positive
0% negative

Coverage balance Positive coverage leads. Positive coverage exceeds negative coverage by 50 percentage points.

  • 50% positive
  • 50% neutral

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 Lip-Bu Tan

Of the tracked stories, 1 of 2 also mention Advanced Micro Devices, the most common co-covered peer. The 38-day window averages about 0.4 stories each week. They are less corroborated than the beat average, carrying 2 original sources each against 3.3 for the same window. The 6.5 average consequence score is above the beat benchmark of 6.4 in the same window. Coverage clusters in earnings, which accounts for 1 of those 2, with the remainder spread across 1 other category. This profile follows 2 Finance stories mentioning Lip-Bu Tan across the period from June 18, 2026 to July 25, 2026.

Stories tracked
2
Per week
0.4
Sources per story
2

Computed from the 2 stories linked to this entity, with beat comparisons drawn from all 582 Finance 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 Lip-Bu Tan. Shared-story counts are live from our verified record — not editorial picks.

Stories mentioning Lip-Bu Tan 2

Lip-Bu Tan is linked from 2 stories 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.