AI entity

C Vijayakumar

Person

Of the tracked stories, 1 of 2 also mention AI agents, the most common co-covered peer. Across a 116-day span, the pace is roughly 0.1 stories per week. They are better corroborated than the beat average, carrying 5 original sources each against 2.7 for the same window.

Last mentioned: Jul 27, 2026

Entity pulse

Recent coverage · C Vijayakumar

2 stories
7.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 C Vijayakumar

Of the tracked stories, 1 of 2 also mention AI agents, the most common co-covered peer. Across a 116-day span, the pace is roughly 0.1 stories per week. They are better corroborated than the beat average, carrying 5 original sources each against 2.7 for the same window. The 7.5 average consequence score is above the beat benchmark of 6.7 in the same window. Coverage clusters in ai-models, which accounts for 1 of those 2, with the remainder spread across 1 other category. C Vijayakumar appears in 2 tracked AI stories published from February 21, 2026 through June 16, 2026.

Stories tracked
2
Per week
0.1
Sources per story
5

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

Stories mentioning C Vijayakumar 2

C Vijayakumar 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.