@NotAIChatBot was updated. Now it supports all multi model capabilities from Gemini API. The source code was also updated. Have fun and report if you got into any trouble.
π₯5

Channel
@wrench_labs
On this record: Topic Β· Growth Β· Engagement Β· Reactions Β· Posts Β· Polls Β· Cite this entry
560subscribers
-17 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
| Telegram ID | -1001619035600 |
|---|---|
| Type | Channel |
| Username | @wrench_labs |
| Created | Between 1 December 2021 and 7 March 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/wrench_labs |
Technology β a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channelβs own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a modelβs judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured β it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 21:36 | 560 | -5 |
| 27 Sept 2026, 18:36 | 565 | -8 |
| 14 Sept 2026, 23:18 | 573 | -3 |
| 8 Sept 2026, 06:56 | 576 | +2 |
| 14 Aug 2026, 23:08 | 574 | -4 |
| 8 Aug 2026, 05:17 | 578 | +1 |
| 7 Aug 2026, 10:18 | 577 | no change |
| 7 Aug 2026, 09:36 | 577 | first reading |
20 posts held, back to 7 March 2023 β 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 page of 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 31 May 2024. An engagement rate over an empty window would be a number about nothing.
257 reactions across 19 posts, in 14 distinct kinds. The most used accounts for 26.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| π | 69 | 26.8% | |
| β€ | 58 | 22.6% | |
| π₯ | 46 | 17.9% | |
| π’ | 31 | 12.1% | |
| π | 18 | 7.00% | |
| π | 10 | 3.89% | |
| π₯° | 9 | 3.50% | |
| β‘ | 6 | 2.33% | |
| π | 3 | 1.17% | |
| π | 2 | 0.778% | |
| π₯± | 2 | 0.778% | |
| π | 1 | 0.389% | |
| π | 1 | 0.389% | |
| π€ | 1 | 0.389% |
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 20 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 257 reactions 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 7 March 2023 to 31 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.
@NotAIChatBot was updated. Now it supports all multi model capabilities from Gemini API. The source code was also updated. Have fun and report if you got into any trouble.
π₯5
βοΈ File stream bot version 3.0.0 is out π What's new? - π€ Add support for allowed users - π Auto detect and use public IP - π₯ fix bot replying in groups - π New text formatting to links Please report bugs in the discussion chat or in the GitHub issues.
β€7π₯3π2β‘1π1π₯°1
βοΈ File stream bot [golang] version 3.0.0-beta1 is out π What's new? - β Heroku Support (β€οΈDeekshithSH) - π Added timeout while starting main bot - β¬οΈ Added stream and download buttons - π·Many bug fixes Please report bugs in the discussion chat or in the GitHub issues.
β€8π2π₯2
βοΈ File stream bot [golang] version 3.0.0-alpha2 is out π What's new? - π€ User session support Now it's easier than ever to add the bots to channel as admin automatically. - β‘οΈ Changed starting behavior Now you can use the command to start the bot. ./fsb run βοΈ String session generator New pyrogram session generator using QR code login was built into the binary. Run the command for more info ./fsb session -β¦
β€7π3π2π₯2π₯°1
Revive File Stream Bot?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
β€2π1π₯°1
and yeah @RapidStreamBot is also experiencing issues as I've noticed way too much traffic from China and India. We'll be working on improvements later this week
β€3β‘1
Server had issues, I never realised it was down till now. It's back online again. Feel free to post suggestions or bugs in the comments.
It's back online. π« Old conversation contexts were deleted due to some technical errors.
π’6β€3π₯°1
@NotAIChatBot is having some technical issues, it'll be fixed soon.
π4
New link generations for [@RapidStreamBot] are temporarily stopped due to technical difficulties. This issue will be fixed soon. All the existing links will work fine btw. Edit: Service restored π
β€1π1
Bugs, Feature requests & suggestions? Comment it down. π How to get accepted to group? After applying to join the group, check for any bot DMs. Follow the on screen instructions and you'll be in.
β€9π2π2π2
π₯ Announcement @RapidStreamBot is back (for now) βοΈ What's new? - π New downloads page with web player support [β€οΈ @AlkenDester] - π Added File report system - Added Customizable File Expiry options - π§ Check /settings command for more configurations. β² Sorry for the extended delay. Implementing a web player was not that easy just like we thought but we manage to pull it off thanks to our frontend dev. The bot mighβ¦
π₯13π4π1π€1
Showing the 12 most recent of 20 posts we hold for @wrench_labs. 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.
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.
Revive File Stream Bot?
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 7 March 2023 to 31 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.
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 7 October 2026 β this entry's latest reading, not the date you are reading this.
βπ§ wrench's π§ͺβ (@wrench_labs), 560 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/wrench_labs.
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.