Telegram RegisterThe public register of Telegram

Channel

RIP Candle

@R1PCOIN

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

556subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003775514004
TypeChannel
Username@R1PCOIN
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/R1PCOIN

Growth

556557556.57 Aug 2026, 03:03 — 557 subscribers7 Aug 2026, 03:15 — 557 subscribers7 Aug 2026, 19:55 — 556 subscribers7 Aug 2026, 03:037 Aug 2026, 19:55
3 measurements taken within a single day, net -1. 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 556–557 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 19:55556-1
7 Aug 2026, 03:15557no change
7 Aug 2026, 03:03557first reading

Engagement

20 posts held, back to 30 July 2026the 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.

ERR · 30 days
22.5%
avg views ÷ 556 subscribers
Avg views / post
125
17 posts measured
Reaction rate
8.75%
reactions ÷ views · ER floor
Posts in window
20
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. It is computed over the 16 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (30 July 20265 August 2026)
Views total2,128
Reactions total172
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:15 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.

Reaction mix

172 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 49.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥8549.4%
5431.4%
🏆1911.0%
👏84.65%
63.49%

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 16 of the 20 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 172reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 30 July 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

5 Aug 2026, 17:03 UTC57 views9 reactionsread 7 August 2026
Photo

✅PARTNERSHIP IS NOW LIVE Today marks the first step in building the shared ecosystem of RIP Candle × Hunter Network. 🕯😎The RIP/HUNT trading pool is now officially live. ⚡An initial liquidity of 1,000,000 AXM (equivalent value) has already been added to the pool. ⚡ With a trading fee of just 1%, swapping RIP ↔ HUNT is more efficient than in standard pools. This pool lays the foundation for future joint products,

6🔥2🏆1

5 Aug 2026, 14:53 UTC60 views8 reactionsread 7 August 2026
Photo

🚨TWO LEADERS. ONE VISION. Today marks the beginning of a new chapter in the Axiome ecosystem. 🙂 RIP Candle and 😎 Hunter Network — two of the fastest-growing and most liquid projects in the ecosystem — are officially joining forces as strategic partners. This is more than just a joint announcement. It marks the beginning of a long-term partnership that will unlock entirely new opportunities for both communities.

🔥42👏2

5 Aug 2026, 08:47 UTC62 views9 reactionsread 7 August 2026

⚡️ Today, we’re about to make one of the biggest announcements in recent months. We’ve been working on this for weeks. Only a few hours remain until the official reveal. 👀 If you’ve been following the growth of the Axiome ecosystem, you won’t want to miss this. 🔔 Turn on notifications for our channel now. Trust us—today’s announcement will mark the beginning of something truly big.

🔥52🏆2

4 Aug 2026, 10:59 UTC88 views16 reactionsread 7 August 2026
Photo

🕯 1,000,000 RIP Have Found Their Owners! This week’s LP Bonus has been successfully distributed. 🎁A total of 1,000,000 RIP has been distributed among RIP/AXM liquidity providers. Every week, liquidity providers receive their share of the reward pool based on the amount of liquidity they contribute. Don’t miss the next distribution — add liquidity to the RIP/AXM pool today and start earning weekly RIP rewards. 🚀

84🔥4

3 Aug 2026, 18:48 UTC100 views11 reactionsread 7 August 2026
Photo

🎉 100,000 RIP Giveaway! To celebrate the growth of the RIP Candle ecosystem, we’re giving away 100,000 RIP! 🕯 How to participate: ✅Follow RIP_Candle on X. ✅Add RIP to your CoinGecko Watchlist. ✅Repost this post. ✅Reply to this post with: 📷A screenshot showing RIP in your CoinGecko Watchlist. 👛 Your Axiome Wallet address. 🎁 Prize Pool: 100,000 RIP 📅 Giveaway ends: August 7 (Friday). ❤️Thank you for supporting t

🔥542

3 Aug 2026, 13:31 UTC122 views16 reactionsread 7 August 2026
Photo

🎉1,000,000 RIP TRADER Prize Pool Distributed! The latest TRADER round has ended, and all rewards have been distributed. 🥇The winner received 526,557 RIP and has joined our private trading education group. 🤝The remaining prize pool was distributed among the other participants according to the final leaderboard. Thank you to everyone who took part! More competitions, bigger rewards, and new opportunities are coming

🔥75🏆4

2 Aug 2026, 12:13 UTC165 views15 reactionsread 7 August 2026
Photo

🎮🤖RIP Candle Climbs to the Top on GeckoTerminal! RIP Candle continues to gain momentum on GeckoTerminal and is now among the most active projects by 24-hour transaction count. 🥇 #1 in the Bots category 🥈 #2 in the Gaming category These rankings reflect the growing activity around the RIP Candle ecosystem and the strength of our community. ⭐Support RIP Candle by adding it to your GeckoTerminal Watchlist. It only t

🔥94🏆2

2 Aug 2026, 11:10 UTC113 views12 reactionsread 7 August 2026
Photo

🔥450,000 RIP Burned This Week This week, the RIP Candle ecosystem permanently burned 450,000 RIP. Burn breakdown: 🔥109,174 RIP — burned by the project. 🔥340,826 RIP — burned by users and internal ecosystem mechanisms. Thank you to everyone contributing to the growth of the ecosystem. 🚀 🕯RIP Candle ✖️ X | ✈️Mini App | 🦎 GeckoTerminal 🤨 CoinGecko

6🔥4🏆2

2 Aug 2026, 08:59 UTC138 views9 reactionsread 7 August 2026
Photo

🦎RIP Candle Updated on GeckoTerminal! Today, the RIP Candle page on GeckoTerminal received several important updates. ✅Updated project logo and description ✅Added official project links ✅Updated categories: Gaming • Bots • Meme 📈GT Security Score increased from 14 to 31 🏆RIP Candle now has the highest GT Security Score among projects in the Axiome ecosystem. The project page is now more complete and informative,

4🔥4🏆1

1 Aug 2026, 22:14 UTC153 views13 reactionsread 7 August 2026
Photo

🦎Official Verification Post This post serves as public verification for the following submitted applications related to the RIP Candle project. GeckoTerminal Project Information Update Application ID: GT- GTIU3107260017 CoinGecko ✅CoinGecko Logo Update Application ID: CU0108260017 ✅CoinGecko Project Information Update Application ID: CU0108260018 ✅Category Tags Update Application ID: TU0108260009 GeckoTermin

🔥64👏3

1 Aug 2026, 20:36 UTC177 views11 reactionsread 7 August 2026
Video

🦎 RIP Candle is now on CoinGecko! Another important milestone for our project. RIP Candle is now officially listed on CoinGecko and has also appeared in the New Listings section for Axiome Trade. This is another step toward increasing the project’s visibility and expanding its presence across the crypto ecosystem. More market data will continue to appear as CoinGecko completes the indexing process. Thank you to

🔥82🏆1

1 Aug 2026, 19:21 UTC105 views6 reactionsread 7 August 2026
Photo

🕯TREASURY NFT NOW SPLITTABLE We’ve reached an important milestone in the evolution of the Treasury Pool: ➡️Treasury NFT holders can now split their NFT into multiple NFTs with smaller ownership shares, with a minimum share size of 0.1%. ➡️This means that any Treasury NFT, regardless of its current share, can be divided into multiple NFTs with ownership percentages in 0.1% increments. ➡️Each NFT can be individual

🔥41🏆1

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

Citation-graph rank — 314,973 of 1,169,250entries 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.

Mentions

Named by 3 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.

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.

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

“RIP Candle” (@R1PCOIN), 556 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/R1PCOIN.

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.