X returns a maximum of 3,200 of your most recent posts, and your reposts are counted inside that number rather than beside it.
That ceiling, not your patience, decides how much of your repost history is still reachable. Almost nobody checks it before they start scrolling.
To see all my retweets on Twitter, load your post history into a filterable table and set the post-type filter to reposts. Circleboom retrieves your X posts through official API access, labels every entry a post, repost or reply, and lets you rank the result by any engagement column.
→ see all my retweets on Twitter
The reach section further down decides whether your oldest reposts are still findable at all.
How to see all my retweets on Twitter, step by step
Circleboom loads your reachable X history into one table and marks what class each entry belongs to. Six moves, and the fourth one is the only one that does real work.
Connect the account and load the post table
- Log in to Circleboom Twitter and pick the handle whose repost history you want to read.
- Move to X Post Planner in the left-hand menu. The post analytics table sits there, alongside the composer and the scheduling queue.
- Let the table finish loading. Circleboom prints one row per accessible entry, with impressions, likes, reposts, quotes, bookmarks, replies and the creation date sitting beside each row.
Filter to reposts, then rank what is left
- Set the post-type filter to reposts. The filter panel treats original posts, reposts and replies as separate classes, so one selection strips out everything you wrote yourself.
- Sort by whichever column matches your question. Ranking by date rebuilds the chronology. Ranking by impressions puts the amplifications that actually traveled at the top.
- Act on a row without leaving the table. Open the original on X, queue the entry for a reshare, or write the filtered set out as a file you keep.
That sequence holds because each step narrows the problem the one before it created.
The login earns sanctioned access, the table converts an infinite scroll into countable rows, the post-type filter removes the majority you were not looking for, and the sort turns what remains into a ranking rather than a pile.
Quick recap:
- Connect the account.
- Move to X Post Planner.
- Let the post table load.
- Filter post type down to reposts.
- Sort, then act or export.
Why X never hands you a list of your own reposts
Your reposts are scattered through your profile timeline, mixed in with everything else you ever published.
X marks each one with the repost icon and the reposting account's name, which is enough to recognize a repost you happen to scroll past. It is useless for gathering them. There is no profile tab that collects them, no running counter, and no way to ask the interface for reposts only.
The workarounds people reach for do not close the gap either. Searching your own handle does not reliably return the posts you reposted, because the text belongs to somebody else's account rather than yours.
The counting problem hiding under the scroll
So the native answer is scrolling, and scrolling carries a counting problem underneath it.
You cannot total something you can only view a screenful at a time. That is why most people's estimate of their own repost count is badly low, and why the estimate is usually the thing that stops them starting.
If your question is narrower than the whole history, find my retweets from a specific account covers the single-handle version of this search.
A loaded table answers the counting question first and the reading question second. The page that lets you see all my retweets on Twitter reports the count in its header before you have read a single row.
Screen recording: the post table this guide sorts, with the engagement columns live beside each row.
https://www.youtube.com/watch?v=NxruclL0uCg
How far back can you actually see your reposts on X?
Your reposts share one retrieval budget with everything else you have posted.
X's own user Posts timeline documentation caps that endpoint at 3,200 of your most recent posts.
The same page lists replies and reposts among the things you can filter out, rather than as things sitting outside the window. They are inside it by default.
That changes the arithmetic in a way almost every article on this query skips.
The 3,200 is not 3,200 pieces of your own writing with your reposts stacked on top. It is 3,200 entries total, in whatever mix of the three types your account happens to produce.
An account where 60% of the output is reposts spends about 1,900 of those slots on other people's content.
Why the window closes faster on a repost-heavy account
Run that forward and the real effect is calendar depth. Two accounts that write the same number of original posts a day reach very different dates. The one that also reposts heavily burns through the same 3,200 slots far faster, so its window closes on a much more recent morning.
Which is also why a heavy reposter's oldest reposts tend to be the ones already out of reach, rather than the ones buried deepest in the scroll.
Anything older than the window needs X's own data download instead of a live view, and that is a different job with a different waiting period. Keeping a copy while the entries are still reachable is the cheaper move, and download my tweets walks through what that copy actually contains.
The number to write down before you do anything else
Load the table, filter to reposts, and note two figures: the repost count and the date on the oldest row.
Those two numbers tell you what kind of job you are looking at. A few hundred reposts reaching back three years is a browsing exercise. Two thousand reposts reaching back seven months means the window is moving fast, and the record is worth saving now rather than later.
Nobody can give you that pair of numbers except your own account, and neither one is visible from the profile.
What a filtered repost list gives you that scrolling cannot
A ranked list turns your repost history into something you can make decisions from.
The same table that isolates reposts carries the metrics alongside them, so one set of rows answers several questions depending on which column you rank by. Date rebuilds the chronology. Impressions show which of your boosts traveled. Likes and replies show which ones your own audience actually engaged with.
Circleboom reads all of it over a sanctioned connection instead of a script running inside your browser.
The company is listed on X's Enterprise customer directory, so a long read of your own history arrives as an authorized request instead of something the platform has to interpret.
Three things become possible the moment the list exists:
- Auditing the ratio of your own writing to other people's, which is the thing a profile visitor forms an impression from.
- Finding the repost you half-remember without knowing its date or the handle behind it.
- Taking a copy of the record before the window rolls it out of reach.
Pull every repost on your X account into the table and the third one stops being urgent, because the file exists.
The CSV column that makes the ratio countable
The paid Export Tweets route writes the same rows to CSV with a TweetType column that labels each entry a tweet, retweet or reply. That single column is what makes the ratio countable in a spreadsheet instead of guessable from a scroll.
The file end of that workflow has its own quirks.
Export all tweets to Excel or CSV covers what actually lands in the download.
One thing to expect before you open it: the engagement figures are captured at the instant of retrieval, so the file is a reading of one day rather than a live one.
Acting on a repost from inside the table
Finding an old repost and removing it are two different decisions, and the second one is rarely the useful one.
The analytics table treats every row as actionable, so the entries you find can be sent somewhere rather than deleted. Four routes exist from a single row:
- Open the original on X to read it in context before you decide anything.
- Add the entry to the reshare queue so it goes out again in a fresh distribution window.
- Put it on a recurring cycle through the Auto Repost panel.
- Push it into a future X Post Planner slot, or open an AI rewrite of the text as a draft.
Two constraints are worth knowing before you queue anything. A reshare or a scheduled slot must land at least a quarter of an hour ahead, and the account link must still be valid by the time it fires.
An AI rewrite counts as a draft rather than a post, so it sits in the composer until you send it.
The useful reading of an old repost is usually "why did this travel", not "why did I press the button".
That is the difference a list makes. One entry looks like a lapse in judgment. Two hundred entries sorted by impressions look like a pattern you can use.
What the repost record tells you about your account
Your repost list is a dated log of everything you once thought worth passing on.
Read as a set rather than as individual entries, it shows:
- the topics you kept boosting
- the accounts you promoted more than you noticed
- the stretches where you published almost nothing of your own
That last pattern is the one people find most uncomfortable, and it is invisible until the rows sit in one table.
There is a performance reading available too.
Reposts land in the same table as your originals, so the engagement analytics view compares what you boosted against what you wrote using identical metric columns. A repost that outperformed six of your own posts is worth knowing about, and so is the opposite.
If the goal is commercial rather than tidy, the same rows feed a valuation exercise. Measure and monetize tweet value works from post-level performance in the same way.
None of this requires you to remove a single entry. Seeing the record and editing the record are separate decisions, and most accounts only ever need the first one.
Begin with the count
You do not need a plan, a data download, or a free afternoon to find out what your repost history looks like.
Connect the account, filter the table to reposts, and read the count in the header. That number is the whole decision. If it is small, you are finished in one sitting. If it is large, you now know to take a copy before the window moves past the oldest rows.
Start with the count rather than the cleanup, because the count is the part you cannot recover later. Reposts you can still reach today are reachable on your schedule. Reposts that have slipped past the window are gone from the live view whether or not you ever decide what to do with them.
→ the full list of your Twitter reposts
Questions about the reposts you cannot reach
Can I see reposts I made years ago?
Only if they still sit inside the most recent 3,200 entries on the account. That window covers posts, reposts and replies together, so a busy account reaches back months rather than years. Anything older needs X's own data download rather than a live view of the account.
Does reading my repost list change anything on my profile?
No. Loading, filtering, sorting and exporting are all read operations, and nothing leaves your timeline unless you deliberately choose an action that removes it. The list is a view of the account, not a change to it.
Why do some rows show no impression figure?
Impression data is not available for every post. Some entries predate the Circleboom connection on the account, and others sit outside X's own analytics retention. Either case can return a row with no impression count, and where impressions are missing the engagement rate for that row cannot be worked out.
