Rugging memecoins changed my life. Get started here @airugsolbot

Channel
RugsolAI
@rugsolgroup
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
16,032subscribers
-5,184 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002493609586 |
|---|---|
| Type | Channel |
| Username | @rugsolgroup |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/rugsolgroup |
Topic
Crypto & trading — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 10:18 | 16,032 | +36 |
| 3 Nov 2026, 12:05 | 15,996 | +70 |
| 2 Nov 2026, 15:06 | 15,926 | +94 |
| 1 Nov 2026, 11:40 | 15,832 | +42 |
| 31 Oct 2026, 12:44 | 15,790 | +42 |
| 30 Oct 2026, 15:28 | 15,748 | +41 |
| 29 Oct 2026, 13:49 | 15,707 | +34 |
| 28 Oct 2026, 11:11 | 15,673 | +21 |
| 27 Oct 2026, 13:37 | 15,652 | +75 |
| 26 Oct 2026, 11:08 | 15,577 | +82 |
| 25 Oct 2026, 12:46 | 15,495 | +40 |
| 24 Oct 2026, 13:28 | 15,455 | +29 |
| 23 Oct 2026, 16:28 | 15,426 | +45 |
| 22 Oct 2026, 15:06 | 15,381 | +34 |
| 21 Oct 2026, 11:57 | 15,347 | +46 |
| 20 Oct 2026, 09:17 | 15,301 | +51 |
| 19 Oct 2026, 12:49 | 15,250 | +75 |
| 18 Oct 2026, 14:31 | 15,175 | +6 |
| 17 Oct 2026, 17:27 | 15,169 | -6 |
| 16 Oct 2026, 16:00 | 15,175 | first reading |
Engagement
43 posts held, back to 3 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 60 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 19.7%
- avg views ÷ 16,032 subscribers
- Avg views / post
- 3,150
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 43 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.
| Window | Rolling 30 days · latest post in window 3 November 2026 |
|---|---|
| Posts held | 43 (3 July 2026 – 3 November 2026) |
| Views total | 63,050 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 05:29 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
- Video runtime
- 1m 15s
- Average length
- 15s
Measured directly from 5 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
Telegram’s own ‘edited’ marker: 2 of 20 posts held from the last 30 days (10.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Solana is at $92 right now. How much more of a discount do you need? Get started with 1 solana @airugsolbot
Rugging coins is just too easy nowadays🤣 Dm @rugsoladmin for info
Solana is about to skyrocket during the bullrun, stay broke or start rugging and farm some solana😴 -> @airugsolbot <- For questions dm @rugsoladmin
Here is a very simple showcase of the bot! @airugsolbot For any more in depth questions please dm @rugsoladmin
fomo cat · $Fomo Cat 💰 Invested: 19.48 SOL ($2,262) 📈 Sold: 84.85 SOL ($9,851) 🤑 Profit: 65.37 SOL · x4.36 ($7,589) Pump.fun · GMGN · DexScreener · Solscan 🤖 @airugsolbot
You keep getting rugged? Why not BECOME the rugger. @airugsolbot start here
Make sure you watch the tutorial video aswel! Its pinned in this channel. For any further questions you can dm me @rugsoladmin
Rugging memecoins is too easy with @airugsolbot
Still broke as fuck? Just start rugging coins with @airugsolbot For any questions dm @rugsoladmin
Will it ever be enough? I dont think so. @airugsolbot to get started For questions dm me @rugsoladmin
“But i dont know how to start rugging my own coins” Just use @airugsolbot 😂 For questions dm me @rugsoladmin
Showing the 12 most recent of 43 posts we hold for @rugsolgroup. 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.
Posts recorded as deleted after publishing
We recorded 3 posts on @rugsolgroup as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 2 September 2026
- Most recent seen missing
- 4 November 2026
- Median time before seen missing
- 51 days
- Seen missing in the last 30 days
- 1
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@rugsolgroup named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 3 September 2026 – 3 September 2026
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“RugsolAI” (@rugsolgroup), 16,032 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/rugsolgroup.
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.