Channel
@isrugapp
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
793subscribers
-9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001749393939 |
|---|---|
| Type | Channel |
| Username | @isrugapp |
| Created | Between 1 December 2021 and 1 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/isrugapp |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 03:44 | 793 | -4 |
| 16 Aug 2026, 13:45 | 797 | -4 |
| 7 Aug 2026, 21:14 | 801 | -1 |
| 7 Aug 2026, 04:32 | 802 | first reading |
17 posts held, back to 1 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 pageof 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 17 posts for this entry, the most recent from 10 March 2024. An engagement rate over an empty window would be a number about nothing.
108 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 47.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 51 | 47.2% | |
| 🔥 | 29 | 26.9% | |
| ❤ | 22 | 20.4% | |
| 👏 | 4 | 3.70% | |
| 👎 | 1 | 0.926% | |
| 😁 | 1 | 0.926% |
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 15 of the 17 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 108reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 1 March 2023 to 10 March 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.
As the isRug team, we have not received any funding or made a significant profit. Therefore, we have decided to discontinue development. We had a wonderful educational experience and we are still committed to contributing to the safety of the crypto ecosystem. We are excited to announce that we have now released the isRug API codes publicly. We would like to express our gratitude towards everyone who supported us th…
❤15👍1👎1
Base network is integrated into isRug telegram bot. We will update the frontend soon
👍11🔥3
isRug Honeypot Checker pinned «Hey everyone 👋 We haven't been able to devote much time lately, we are working hard to build great tools for crypto community. We have added new rockstar level members to our team and we are starting to progress in a more professional structure. In the near…»
Hey everyone 👋 We haven't been able to devote much time lately, we are working hard to build great tools for crypto community. We have added new rockstar level members to our team and we are starting to progress in a more professional structure. In the near future, we will release many debug updates, more stable and scalable telegram bot (Before that use the Website) and more chain integrations. After that, isRug …
🔥7👍5❤2
We have added OpenAI GPT support to isRug bot. It is currently in beta and we are still testing it but in the close future it will be much more better ✍️ Also, from now on, the isRug bot will only be available via isRug Chat.
👍5
We decided to open the Arbitrum new pairs and new contract channels to everyone. Enjoy 🥳 https://t.me/isrugArbNewPairs https://t.me/isrugArbNewTokens
🔥6
We will launch a beta version of one of a kind honeypot checker soon (You will be amazed😎). In the first place, manual scan will be deactive, but it will analyze and share the latest listed tokens on Arbitrum Network. After the beta you will be able to scan tokens for free.
👍6🔥3
isRug will be in maintenance and it will take about 3-4~ hours. There will be no access to the website or bot for the arbitrum network. ✅ The Arbitrum node will be reinstalled. 📣 Our service will not be interrupted if anyone can provide temporary arbitrum rpc during this maintenance period -> @dexlegiondev
👍5❤1
We provide a private RPC endpoint for arbitrum airdrop claim process. Only last 25 people will be taken in. Stress tests are already done and It responds to 4000 requests per second in an average of 77 ms. It's blazing fast ⚡️ and many users have given positive feedback already. Contact @dexlegiondev for more info.
All new features have been added to the website. You can now access detailed information about the token owner on the website 1️⃣
👍2
We have added realtime price chart to the bot audits 📈 Many new features and improvements will be released rapidly in the close future. Stay ✅
👍2
We have updated the isrug.app website 🔥 @isrugapp @isrugchat Holders data will be added to BSC network soon.
🔥2
Showing the 12 most recent of 17 posts we hold for @isrugapp. 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 — 495,808 of 1,621,120entries 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“isRug Honeypot Checker” (@isrugapp), 793 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/isrugapp.
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.