Telegram RegisterThe public register of Telegram

Channel

Rug Pull Bot - rugpullbot.com

@letmerug

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Cite this entry

136,710subscribers

-7,381 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002435401670
TypeChannel
Username@letmerug
DescriptionRugPullBot is a crypto bot for creating and managing deceptive tokens on Solana and BSC chains effortlessly. Profits: https://t.me/letmeprofit Bot: @Therugpullbot Admin: @theonlyrugger
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/letmerug

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 68% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

106,000 average views per post against 136,710 subscribers — an engagement rate of 77.9%. Across the 1,008 registered channels in the same cohort — 100,025–316,023 subscribers, posting mainly in English — the middle half sit between 1.23% and 9.59%, with a median of 4.15%.

What this was computed from
Window30 days (13 July 2026 12 August 2026)
Posts measured8 of 8 published in the window (0 exact, 8 rounded by Telegram)
Views totalled851,970
Mature posts only77.9% over 8 posts read at least 24h after publication
Subscribers136,710 measured 12 August 2026
Cohortb100000:eng · 1,008 channels · p10 0.27% · p25 1.23% · p50 4.15% · p75 9.59% · p90 18.0%
Position in cohort99.801th percentile · 18.8× the cohort median
Uncertainty±0.068% of the figure, from Telegram’s rounding
Post languageEnglish · 100.0%of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

136,710144,091140,400.57 August 2026 — 144,091 subscribers8 August 2026 — 143,773 subscribers9 August 2026 — 143,524 subscribers10 August 2026 — 143,251 subscribers11 August 2026 — 136,884 subscribers12 August 2026 — 136,710 subscribers7 August 202612 August 2026
6 measurements spanning 5 days, net -7,381. 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 135,603–145,198 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:03136,710-174
11 Aug 2026, 11:16136,884-6,367
10 Aug 2026, 09:53143,251-273
9 Aug 2026, 11:31143,524-249
8 Aug 2026, 10:01143,773-318
7 Aug 2026, 14:45144,091first reading

Engagement

20 posts held, back to 25 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
77.9%
avg views ÷ 136,710 subscribers
Avg views / post
106,000
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held20 (25 May 202610 August 2026)
Views total851,970
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 18:14 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
115
Videos
19
Links
103

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
36s
Average length
18s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

10 Aug 2026, 21:10 UTC≈3,870 viewsread 12 August 2026
Photo

We have been receiving a lot, and I mean A LOT of requests of people asking to be able to use the "Withdraw using Coordinated rug on BSC " and we promise we are working hard to have that feature added ASAP, for now use code "BSC" for a quick 20% of your next purchase as a thank you for your understanding and support ❤️

1 Aug 2026, 17:08 UTC≈79,500 viewsread 12 August 2026

Have you joined our discord yet? Our discord now hosts the PNL/Rug cards on the #profits channel! discord.gg/rugpullbot Our team will NEVER DM YOU! Be careful!

25 Jul 2026, 02:14 UTC≈131,000 viewsread 12 August 2026

DEV LOG: Update was released successfully. RUG PULL BOT IS NOW AN APP. What's new: Rug Pull Bot is no longer just a website. It installs straight to your phone's home screen — iPhone and Android — with its own icon and its own window. No browser bars, no address bar eating a fifth of your screen, nothing to download from an app store, no update to wait on. Same account, same data, same everything, just an app. How to

17 Jul 2026, 16:41 UTC≈176,000 viewsread 12 August 2026

DEV LOG: Update was released successfully. OUR BIGGEST UPDATE YET TO DATE. What's new: Rug Pull Bot is no longer Solana-only. BNB Chain (BSC) went from nothing to full feature-parity with Solana in one week. Everywhere you used to see SOL, you now pick your chain. - Create a BSC wallet, or import one from a mnemonic or a raw private key. - Portfolio is chain-aware: filter SOL / BSC / ALL, each with its own chain logo

14 Jul 2026, 02:47 UTC≈165,000 viewsread 12 August 2026

https://gmgn.ai/bsc/token/0x8b3f960477e931c2df520fdee8b56a04641ce634

14 Jul 2026, 02:44 UTC≈22,000 viewsread 12 August 2026
Photo

ALL using AI mode on chinese market enabled; funds used in total was around 60 BNB

11 Jul 2026, 04:04 UTC≈151,000 viewsread 12 August 2026
Photo

I don't know if you have noticed, but for those who haven't: Something is cooking 👨‍🍳👀

9 Jul 2026, 13:52 UTC≈138,000 viewsread 12 August 2026

DEV LOG: Update was released successfully. What's new: - Rug Watcher & Wallet Watcher are now LIVE (on every plan) - Two of the most-requested tools just landed on your dashboard — and we're not locking them behind Premium Boosted. If you're on any paid plan, they're yours right now. - Rug Watcher — get warned before the dump Paste a coin's contract and we watch it in real time. Instead of telling you a coin rugged a

8 Jul 2026, 22:50 UTC≈112,000 viewsread 12 August 2026

📢 To all customers: you've just received a notification on the website to leave a review! If you haven't yet — or dismissed it — here's the link: https://forums.rugpullbot.com/reviews Leave a review on how the bot went and you're entered into a giveaway with a 500 SOL prize pool! 🎉 ⏳ You have until Thu 2026-07-16 00:00 GMT+4 to submit your review.

8 Jul 2026, 22:08 UTC≈108,000 viewsread 12 August 2026

DEV LOG: Update was released successfully. What's new: 🚀 New drop — status.rugpullbot.com is live. Powered by Atlassian Statuspage, so you can check uptime, ongoing incidents, and scheduled maintenance without having to ask. If something's acting up, that's the first place to look before pinging us.

Showing the 12 most recent of 20 posts we hold for @letmerug. 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.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Rug Pull Bot - rugpullbot.com” (@letmerug), 136,710 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/letmerug.

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.