RushTrush chanell pinned «DEV: Token Information Name: Blue Sky Symbol:BSK Total supply: 1,000,000,000,000 Burn : 500,000,000,000 Marketing,dev: 50,000,000,000 Liquidity: 450,000,000,000 Contract: https://bscscan.com/token/0xd3d30a58ee646cc407601136ae2cdb6398969b8f 50%Token…»

Channel
RushTrush chanell
@RushTrushoficiall
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
14subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001335835074 |
|---|---|
| Type | Channel |
| Username | @RushTrushoficiall |
| Created | Between 1 March 2018 and 22 March 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/RushTrushoficiall |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 00:46 | 14 | no change |
| 6 Aug 2026, 22:51 | 14 | first reading |
Engagement
19 posts held, back to 22 March 2021 — 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 19 posts for this entry, the most recent from 26 April 2021. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 14
- Links
- 22
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.
Recent posts
DEV: Token Information Name: Blue Sky Symbol:BSK Total supply: 1,000,000,000,000 Burn : 500,000,000,000 Marketing,dev: 50,000,000,000 Liquidity: 450,000,000,000 Contract: https://bscscan.com/token/0xd3d30a58ee646cc407601136ae2cdb6398969b8f 50%Token burn: https://bscscan.com/tx/0xe2a90e6885846973e1241961d2e190c08e7fb20b921c412da4cb15e7052e7800 Contact: https://bscscan.com/token/0xd3d30a58ee646cc407601136a…
RushTrush chanell pinned «MOON DOVE: 🚀 FAIR LAUNCH 🚀 (MND) LP 100% BURN Token Information: Name: MOON DOVE Symbol: MND Supply: 100,000,000 Burn: 50,000,000 Liquidity: 45,000,000 Tim: 5,000,000 Contact: https://bscscan.com/address/0x7BD999A2CF7FB0125b5aB9C11Cd24678b27A4C54…»
MOON DOVE: 🚀 FAIR LAUNCH 🚀 (MND) LP 100% BURN Token Information: Name: MOON DOVE Symbol: MND Supply: 100,000,000 Burn: 50,000,000 Liquidity: 45,000,000 Tim: 5,000,000 Contact: https://bscscan.com/address/0x7BD999A2CF7FB0125b5aB9C11Cd24678b27A4C54 TG: @moondovee 50%Token burn: https://bscscan.com/tx/0xb97ec7107cfbc9afb62fade62462a13b553f54223ac6070950a7ddfd547ffa30 100% LP burn: https://bscscan.com/tx…
RushTrush chanell pinned «⚔️NINJA SWORD⚔️ NINJA SWORD Is A Community Based Project To collect NINJA Among the talented and intelligent NINJA developments. NINJA is a character who is very talented and also smart in battle. Just Hold the NSD In Your Wallet And You'll Get A Lot More.…»
⚔️NINJA SWORD⚔️ NINJA SWORD Is A Community Based Project To collect NINJA Among the talented and intelligent NINJA developments. NINJA is a character who is very talented and also smart in battle. Just Hold the NSD In Your Wallet And You'll Get A Lot More. In every transaction, the protocol automatically distributes prizes to holders Buy presale In Dxsale : https://dxsale.app/app/pages/defipresale?saleID=1042&chain…
RushTrush chanell pinned «Welcome to K.O! 🔰 K.O Token is a DeFi Token that is driven by the community and launched fairly. It combines three simple functions that occur during each trade: Reflections, LP Acquisition, and BURN. ----------------------------------------------------…»
Welcome to K.O! 🔰 K.O Token is a DeFi Token that is driven by the community and launched fairly. It combines three simple functions that occur during each trade: Reflections, LP Acquisition, and BURN. ----------------------------------------------------------- TOKENOMICS 💯 Total Supply: 1,000,000,000 Presale: 500,000,000 PancakeSwap: 400,000,000 Burn: 100,000,000 There is no marketing and for the owners all remai…
RushTrush chanell pinned a photo
🎉🎉🎉🎉🎉
RushTrush chanell pinned «❇️ROADMAP❇️ ✅Project Launch ✅Deploy SmartContrac ✅Telegram community ✅Token is registered on PancakeSwap and the presale is running ❎Website created ❎Add Logos on (Bscscan, Trustwallet, Safepal, Pancakeswap, etc.) ❎ List of Tokens on CoinmarketCap and CoinGecko…»
❇️ROADMAP❇️ ✅Project Launch ✅Deploy SmartContrac ✅Telegram community ✅Token is registered on PancakeSwap and the presale is running ❎Website created ❎Add Logos on (Bscscan, Trustwallet, Safepal, Pancakeswap, etc.) ❎ List of Tokens on CoinmarketCap and CoinGecko ❎ List of Tokens in Big Markets (Hotbit, Kucoin, etc.) ❎ Partnership ❎More .. Telegram: @dragonflowchanell @dragonflowchat _____ ❇️Detai …
Showing the 12 most recent of 19 posts we hold for @RushTrushoficiall. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 7
- 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
- 7
- vacant every time we have ever looked
@RushTrushoficiall named 7 handles 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 3 posts, 12 August 2026 – 12 August 2026
named in 3 posts, 12 August 2026 – 12 August 2026
named in 2 posts, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“RushTrush chanell” (@RushTrushoficiall), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/RushTrushoficiall.
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.