X (Twitter) Thread Performance Calculator

Quick answer

The X (Twitter) thread performance calculator measures how far readers get through a thread. Completion rate equals views on the last post divided by views on the first post, times 100. Enter the view count of each post in order. The tool returns completion, the drop after post 1, the largest drop and total thread views.

Updated 2026-10-03Reviewed by Prof. Dr. Khalil Mudassar, PhD
Try
X post analytics
One number per post, first post first. Separate with spaces or new lines.
Your own figure from a past thread, for comparison.

Thread completion rate

--
Thread length--
Post 1 to post 2--
Average kept per step--
Largest drop--
Thread views--
Vs earlier thread--

Calculations run in your browser. Inputs are not sent to our servers; anything you Save stays in this browser only.

Saved results (0)

How to Use the X Thread Performance Calculator

The calculator needs one number per post: its view count. X shows a view count on most posts, next to the analytics icon.

  1. Open your thread on X and note the view count of each post, from the first post to the last.
  2. Type the counts into the box in thread order. Use spaces or new lines between them.
  3. Read the completion rate, the drop after post 1 and the per-post table under the result.
  4. Add the completion rate of an earlier thread to see the gap in percentage points.
ResultWhat it means
Thread completion rateViews on the last post as a percent of views on the first post.
Thread lengthThe number of view counts the tool read.
Post 1 to post 2The percent of first-post views that the second post kept, and the change.
Average kept per stepThe steady per-post rate that leads from the first count to the last count.
Largest dropThe pair of neighbouring posts with the biggest percent fall in views.
Thread viewsAll view counts added together, and the average per post.
Vs earlier threadThis completion rate minus the earlier rate you entered, in percentage points.

What Is Thread Performance on X?

Thread performance on X is how well a thread holds its views from the first post to the last post. X Help defines a thread as a series of connected posts from one person. Each post in the series has its own view count.

Three measures describe a thread:

  • Completion rate: last post views divided by first post views.
  • Drop-off: the percent change in views from one post to the next.
  • Total thread views: the sum of every post's view count.

X Help states that view counts show the total number of times a post has been viewed, and that not all views are unique. A completion rate is a ratio of two view counts. It is not a count of people who read every post.

This page measures a thread you have already posted. It gives no score and no forecast. To compare posts that carry a tag with posts that do not, use the hashtag reach calculator.

How Does the Thread Performance Calculator Work?

Formula: Completion rate = last post views / first post views x 100
Change from previous post = (views on post k / views on post k-1 - 1) x 100
Average kept per step = (last post views / first post views) ^ (1 / (posts - 1)) x 100
  1. The tool reads the view counts in the order you typed them.
  2. It divides each count by the first count. That gives the share of first-post views at each position.
  3. It divides each count by the count before it. That gives the change from post to post.
  4. It marks the most negative change as the largest drop.
  5. It takes the root of the completion ratio to find the average kept per step.
  6. It adds every count for total thread views.

The average kept per step is a geometric mean. A thread that keeps 85% at every step for 6 steps ends at 37.7% of its first-post views.

Thread Completion Rate Example

Example values only. A 7 post thread shows these view counts: 8,400, 5,100, 4,300, 3,900, 3,600, 3,300 and 3,150.

  • Completion rate = 3,150 / 8,400 x 100 = 37.5%.
  • Post 1 to post 2 = 5,100 / 8,400 = 60.7% kept, a change of -39.3%.
  • Post 2 to post 3 = 4,300 / 5,100 - 1 = -15.7%.
  • Post 6 to post 7 = 3,150 / 3,300 - 1 = -4.5%.
  • Largest drop = post 1 to post 2.
  • Average kept per step = 0.375 ^ (1 / 6) = 84.9%.
  • Thread views = 31,750, or 4,536 per post.

The thread loses most of its views at the first step. After post 2 the drops shrink to single digits. Against an earlier thread at 45%, this thread sits 7.5 points lower.

Factors That Change Thread Completion

How X Displays Threads

X Help says a thread with 2 or 3 posts generally appears on the timeline joined by a line. A thread with 4 or more posts is truncated, with a Show this thread option. Later posts then need a tap, which is one reason they collect fewer views.

Posts Seen on Their Own

Every post in a thread is a separate post. X Help notes that a Repost or Quote of one post from a thread carries a Show this thread prompt. A post shared this way gains views that the first post never had.

Thread Length

The same step rate gives a lower completion on a longer thread. At 85% per step, a 4 post thread completes at 61.4% and a 10 post thread at 23.2%.

Posts Added Later

X Help says the author can add posts from the thread detail page after posting. A post added a day later has had less time to collect views.

Time Since Posting

View counts keep moving. Read every count in one sitting so each post has the same age.

Completion Rate vs Average Kept per Step

Completion rate describes the whole thread, and the average kept per step describes one hop. The step rate lets you compare threads of different lengths. The table shows the completion that each step rate produces.

Kept per step4 posts7 posts10 posts
90%72.9%53.1%38.7%
85%61.4%37.7%23.2%
75%42.2%17.8%7.5%

A 7 post thread at 37.5% and a 4 post thread at 61.4% both hold about 85% per step. Judge them as equal on a per-step basis. For other percent sums, the percentage calculator covers them.

When to Use a Thread Performance Calculator

After Posting a Thread

Wait until views slow down, then read every count once. The table shows where readers left.

Comparing Two Threads

Enter the completion rate of the earlier thread in the optional field. The tool reports the gap in points. For the relative gap between two rates, use the percentage difference calculator.

Finding a Weak Post

The largest drop names the post where the biggest share of views fell away. Read that post and the one before it.

Reporting to a Client

Total thread views and views per post give two plain numbers for a report. Copy report adds the method line.

Common Thread Analytics Mistakes

1. Calling Views People

X Help says multiple views are counted when one person views a post more than once. A view count is not a reader count.

2. Adding Thread Views as Reach

Total thread views count the same reader once per post. A reader who finishes a 7 post thread adds 7 views.

3. Reading Counts at Different Times

A first post read on Monday and a last post read on Friday mix two ages. Read all counts together.

4. Typing Posts Out of Order

The tool treats the first number as post 1. A wrong order changes every result.

5. Comparing Threads of Different Lengths by Completion

A longer thread completes lower at the same step rate. Compare the average kept per step.

6. Treating One Thread as a Rule

One thread reflects one topic on one day. Measure several threads before changing how you write.

Accuracy and Limitations

The arithmetic is exact for the counts you enter. The limits come from what a view count is.

What it calculates accurately

  • Completion rate from the first and last counts.
  • The change in views between each pair of posts.
  • The largest drop and its position.
  • Total thread views and the average per post.

What it does not account for

  • Unique readers. X counts repeat views.
  • Views that reach a later post directly, through a Repost, Quote, search or shared link.
  • Engagements such as likes, replies and link clicks.
  • Why readers left. The numbers show where, not why.

X Help also states that embedded posts do not add to view counts and that the author's own views do count. No benchmark is built in, because X publishes no typical completion rate.

How We Calculate Thread Performance

Method
Completion rate = last count / first count x 100. Change = count / previous count - 1. Average kept per step = completion ratio ^ (1 / (posts - 1)).
Inputs used
The view count of each post in your own thread. Presets are example values.
Assumptions
Counts are typed in thread order and were read at the same time.
Verdict
Neutral without a comparison. Green or amber only against the earlier completion rate you enter. No built-in benchmark.
Rounding
Percentages to 1 decimal. Views to whole numbers.
Edge cases
Fewer than 2 counts gives no result. A first count of zero is rejected. A completion above 100% is flagged. A step from a zero count shows n/a.
Sources
X Help Center and X developer pages listed below, read on 2026-10-03.
Last reviewed
2026-10-03.

Frequently Asked Questions About X Thread Performance

What is a good thread completion rate on X?

X publishes no typical completion rate, so no official benchmark exists. Compare a thread with your own earlier threads. The optional field reports the gap in percentage points.

How do I find the views of each post in a thread?

Open the thread and read the number next to the analytics icon on each post. X Help says view counts appear on posts in the timeline and on the post details page.

Why does the second post have far fewer views than the first?

The first post appears alone in many timelines. X Help says threads with 4 or more posts are truncated with a Show this thread option, so later posts often need a tap.

Can a later post have more views than the first post?

Yes. Each post in a thread is a separate post. A later post gains extra views when someone Reposts, Quotes or links to it directly. The tool flags a completion above 100%.

Does thread completion rate count unique readers?

No. X Help states that not all views are unique. One person who views a post on web and then on a phone adds two views.

How many posts can a thread have?

The X Help page on threads, read on 2026-10-03, states no maximum number of posts. It notes that text over the character limit is highlighted in each post. The How to Post page gives that limit as 280 characters.

What does average kept per step mean?

It is the steady per-post rate that links the first count to the last count. A 7 post thread at 37.5% completion keeps an average of 84.9% per step.

Should I use views or impressions?

Use one metric for every post. X Help calls the public number a view count. The X developer documentation defines impressions as the count of times a post appeared on a screen, also not unique.

Does the calculator predict how my next thread will do?

No. It measures a thread that already has view counts. It contains no forecast, score or algorithm weight.

Is my data saved?

No. The maths runs in your browser and nothing is sent to us. Save keeps a result only in this browser.

Sources
  • How to create a thread on X (X Help Center, read 2026-10-03; thread definition, timeline display of 2-3 and 4 or more posts, adding posts later, Repost and Quote prompts).
  • View counts (X Help Center, read 2026-10-03; view count definition, repeat views, embedded posts, author views).
  • How to Post (X Help Center, read 2026-10-03; 280 character limit for a post).
  • X API metrics: fields and definitions (X developer documentation, read 2026-10-03; impressions defined as times a post appeared on a screen, not unique).

Related Calculators

Measuring more of your X account?

Explore all X (Twitter) calculators

Educational estimate only. Results are arithmetic on the figures you enter and do not predict how a future post will perform. X is the source of record for your post data. MultiCalculators is not affiliated with or endorsed by X Corp. X and Twitter are trademarks of X Corp. Spotted an error? Let us know.

Author

shakeel-Muzaffar
Founder & Editor-in-Chief at  ~ Web ~ More Posts

Shakeel Muzaffar is the Founder and Editor-in-Chief of MultiCalculators.com, bringing over 15 years of experience in digital publishing, product strategy, and online tool development. He leads the platform's editorial vision, ensuring every calculator meets strict standards for accuracy, usability, and real-world value. Shakeel personally oversees content quality, formula verification workflows, and the platform's commitment to publishing tools that are genuinely useful for students, professionals, and everyday users worldwide.