Channel
@rugpull_moon
On this record: Growth · Engagement · Posts · Citations · Cite this entry
9,666subscribers
-923 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003207767838 |
|---|---|
| Type | Channel |
| Username | @rugpull_moon |
| Created | Between 1 October 2025 and 31 December 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/rugpull_moon |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 14:25 | 9,666 | +55 |
| 27 Aug 2026, 15:53 | 9,611 | +101 |
| 24 Aug 2026, 06:16 | 9,510 | +125 |
| 20 Aug 2026, 16:37 | 9,385 | -1,048 |
| 19 Aug 2026, 16:55 | 10,433 | +3,367 |
| 16 Aug 2026, 18:56 | 7,066 | -39 |
| 13 Aug 2026, 13:27 | 7,105 | -198 |
| 10 Aug 2026, 22:06 | 7,303 | -3,229 |
| 10 Aug 2026, 00:31 | 10,532 | -41 |
| 9 Aug 2026, 00:51 | 10,573 | -10 |
| 7 Aug 2026, 22:01 | 10,583 | -6 |
| 7 Aug 2026, 18:31 | 10,589 | no change |
| 7 Aug 2026, 18:26 | 10,589 | first reading |
146 posts held, back to 6 August 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 29 pagesof Telegram’s post history, 20 posts per page.
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 29 August 2026 |
|---|---|
| Posts held | 146 (6 August 2026 – 29 August 2026) |
| Views total | 141,087 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 05:42 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.
MAIN INFORMATION✅ 🚀How to start: Click here 🆓 Free access: Click Here 🏷 The price-list: Click here 👨💻How it works: Click here 🤖Tutorial bot: Click Here 💰Profit channel: Click Here 👥Feedback Channel: Click Here 🩸Amount to start: Click Here 🪙How to buy solana: Click Here ———————————————— Support @RugMoon_Support
OUTSTANDING FEEDBACK FROM OUR SUBSCRIBER⚡️ We strive to delight you with feedback every day so you can see that our bot is the perfect tool for earning, even if you have no experience! In the bot, you will receive a complete step-by-step guide and an additional channel with examples of tokens! Hurry to get free access for a week, all you need to do is buy 2-5 Solana and send a screenshot to our support so they can …
Video message, posted without a caption
🆕RUGPULL MOON 2.0 Hello everyone, dear subscribers! We have great news for you—today a major update happened in our project. Now you can create tokens not only in the bot, but also in a ready-made online panel! In the new version, you can use: ▪️AI token creation ▪️Automatic creation of social media ▪️Automatic wallet splitting ▪️Individual statistics for each client ▪️Auto-split between wallets and coins *Now th…
🤔HOW TO GET FREE WEEKLY ACCESS ❓ To begin, you can try a free one-week access, but you need a minimum of 3 SOL(~300$) in your wallet for this! This is necessary so that the bot can charge fees and create fake liquidity. There are no costs for creating the token; you can create it completely for free! The higher the amount in your wallet, the greater the liquidity of your token, which means higher profits! *To get…
OUTSTANDING FEEDBACK FROM OUR SUBSCRIBER⚡️ We strive to delight you with feedback every day so you can see that our bot is the perfect tool for earning, even if you have no experience! In the bot, you will receive a complete step-by-step guide and an additional channel with examples of tokens! Hurry to get free access for a week, all you need to do is buy 3-5 Solana and send a screenshot to our support so they can …
@rugmoon_support
RUGPULL IS IT LEGAL❓ A very common question from our subscribers! - YES, IT IS LEGAL AND SAFE ✔️ We only use official exchanges and wallets for our operations, and we also lock liquidity, which makes our coin trusted and official on DEX exchanges! Additionally, you can continue to develop your coin further if you have significant capital. We create the smart contract clean and without signatures, ensuring that eac…
Video message, posted without a caption
MAIN INFORMATION✅ 🚀How to start: Click here 🆓 Free access: Click Here 🏷 The price-list: Click here 👨💻How it works: Click here 🤖Tutorial bot: Click Here 💰Profit channel: Click Here 👥Feedback Channel: Click Here 🩸Amount to start: Click Here 🪙How to buy solana: Click Here ———————————————— Support @RugMoon_Support
A CLIENT EARNED MONEY ON THE FIRST DAY🤑 These are the results each of you can achieve. We strive to highlight you in almost every review! It's important that you become part of our community! Hurry up, because even if you have no experience, you can earn money on your first day. The bot provides you with complete step-by-step instructions and an additional channel with token examples! Support: @rugmoon_support
@rugmoon_support
Showing the 12 most recent of 146 posts we hold for @rugpull_moon. 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.
Citation-graph rank — 771,329 of 1,627,445entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Rugpull Moon” (@rugpull_moon), 9,666 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/rugpull_moon.
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.