5 measurements spanning 21 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 159–160 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
28 Aug 2026, 23:45
159
-1
22 Aug 2026, 13:33
160
+1
15 Aug 2026, 14:04
159
-1
8 Aug 2026, 17:16
160
no change
7 Aug 2026, 12:31
160
first reading
Engagement
20 posts held, back to 14 May 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 20 May 2024. An engagement rate over an empty window would be a number about nothing.
Reaction mix
18 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 61.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
11
61.1%
🔥
4
22.2%
👏
3
16.7%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 6 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 18reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 May 2024 to 20 May 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Hello everyone
We have identified the issue and what was causing the problem was the fact that dolphin was periodically rolling out an update to the built-in chrome browser over the last week which was mismatched with the automatic updates from Chrome on our end
Because it was rolled up periodically, this is what has caused issues for the majority of our users
How to fix:
- Restart dolphin
- In dolphin press heal…
Can everyone who’s facing issues with the bot not doing drops try uninstalling chrome and dolphin and deleting all instances of Tweet Riser, then reinstalling everything to see if that works to fix the issue. It’s something to do with a tool called chrome driver which needs to be forced to update
Everyone, when booting the software please be patient as it can take some time to boot all profiles. If you have set it up correctly you will have no issues.
Showing the 12 most recent of 20 posts we hold for @tweetriser. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Are you having issues with Tweet Riser, if so what do you think the problem is? (do not answer if you are not on the latest version, posted above)
Profiles launch but no drops30%
Runs for some time then stops20%
Likes and RTs but no DM10%
No issues40%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 14 May 2024 to 20 May 2024. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 28 August 2026 — this
entry's latest reading, not the date you are reading this.
“Tweet Riser AVAILABLE NOW” (@tweetriser), 159 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/tweetriser.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.