redditscanner.ai
back to writing

What Does a 'Growing' Reddit Thread Label Actually Mean?

A source-level explanation of RedditScanner's thread trend labels, with the difference between score movement and actual comment growth.

RedditScanner team
·October 16, 2026·2 min read

A thread can gain comments and still lose its "growing" label. In RedditScanner, that label compares two opportunity scores, not two comment counts. The distinction matters if you're deciding whether to spend time on a reply.

I checked the scoring and scan implementation on October 14, 2026. This is an explanation of the current code, not a claim about how accurately it predicts engagement on live Reddit. Accounts are closed while the next version is built, so use this as a way to question any similar trend label, not as an invitation to sign up.

A score is not a conversation counter

The scoring guide describes a mix of thread age, comments, votes, community size, question-shaped titles, and keyword position. Age reduces the score as time passes. Comments get their full contribution only within a middle range; a crowded thread can score lower than it did earlier. More comments therefore need not mean a higher opportunity score.

For a saved monitor, the scan route stores a snapshot of the score, votes, and comment count when a thread first appears. On a later scan, it compares the new score with the previous snapshot's score. A change greater than 10% gets "growing"; a drop greater than 10% gets "declining"; anything between those bounds gets "peaking." With no previous snapshot it gets "new." These are code thresholds, not measured probabilities of a reply being seen.

Consider an illustrative score of 60. If the next scan scores 67, the change is about 11.7%, so the label is "growing." A move to 66 is exactly 10%, so the label is "peaking." Neither example says how many people commented. And "peaking" does not mean the thread reached its lifetime high: the current function uses only the immediately previous score.

Check the underlying thread before acting

The implementation also calculates an "engagement velocity" by dividing the thread's total comments by hours since the scanner first saw it. It does not calculate new comments between scans. A thread that already had many comments when discovered can look fast by that measure. The first observation is assigned velocity zero.

Open the actual thread and read its latest replies, not just the label. Ask whether the original question remains unanswered, whether the discussion has moved on, and whether the community allows your kind of reply. Reddit's sitewide rules say to respect individual community rules. If you have no useful answer, a high score or a "growing" badge is not a reason to post.

For a serious timing decision, record comment counts at two actual observation times and compare the difference. That gives you observed new comments per interval. It still won't tell you whether your reply will be welcomed.

keep reading

Take the next question with you.

Accounts are closed while we build the next version. The field notes stay available in the meantime.