Telegram RegisterThe public register of Telegram
Telegram profile photo for Rangers Procotol Announcements

Channel

Rangers Procotol Announcements

@RangersProtocolAnnouncement

On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

6,267subscribers

-40 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001380475192
TypeChannel
Username@RangersProtocolAnnouncement
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/RangersProtocolAnnouncement

Growth

6,2676,3076,2877 August 2026 — 6,307 subscribers7 August 2026 — 6,307 subscribers10 August 2026 — 6,299 subscribers13 August 2026 — 6,296 subscribers16 August 2026 — 6,282 subscribers19 August 2026 — 6,280 subscribers23 August 2026 — 6,273 subscribers26 August 2026 — 6,267 subscribers7 August 202626 August 2026
8 measurements spanning 19 days, net -40. 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 6,261–6,313 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Aug 2026, 07:476,267-6
23 Aug 2026, 03:456,273-7
19 Aug 2026, 22:426,280-2
16 Aug 2026, 17:186,282-14
13 Aug 2026, 07:546,296-3
10 Aug 2026, 16:276,299-8
7 Aug 2026, 01:156,307no change
7 Aug 2026, 01:076,307first reading

Engagement

20 posts held, back to 5 July 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pagesof 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 20 posts for this entry, the most recent from 9 December 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

38 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 42.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1642.1%
615.8%
👍615.8%
👏615.8%
❤‍🔥37.89%
12.63%

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 9 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 38reactions 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 5 July 2024 to 9 December 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.

Recent posts

9 Dec 2024, 10:15 UTC≈1,180 views3 reactionsread 12 August 2026
Photo

🥂November Progress Report is Here! In November, most of the work was targeted in improving and optimizing user experience in Rangers ecosystem. 🔍Intend to read more? Click the link below🔽 https://x.com/RangersProtocol/status/1866063901806498274

1👍1🔥1

Signed Rangers Protocol Admin

5 Dec 2024, 09:04 UTCviews —

Rangers Procotol Announcements pinned «Rangers Protocol Governance Proposal: Optimizing Miner Rewards to Strengthen Decentralization ‼️ 🫂Dear Rangers Community, To further drive Rangers Protocol towards decentralization and enhance the confidence of the Web3-focused community, we are introducing…»

5 Dec 2024, 09:04 UTC734 views3 reactionsread 12 August 2026

Rangers Protocol Governance Proposal: Optimizing Miner Rewards to Strengthen Decentralization ‼️ 🫂Dear Rangers Community, To further drive Rangers Protocol towards decentralization and enhance the confidence of the Web3-focused community, we are introducing a governance proposal aimed at optimizing the miner reward mechanism. This adjustment seeks to fairly and effectively incentivize active participation from net

🔥21

Signed Rangers Protocol Admin

13 Nov 2024, 09:51 UTC707 views3 reactionsread 12 August 2026
Photo

🔟Rangers October Progress Report In October, Rangers Mainnet operated stably generated over 66,640,000 blocks. We achieved several milestones on Rangers Mainnet. 🔛The cross-chain bridge has successfully integrated with @KaiaChain and @trondao 💁‍♂️The KOL version of the #CLLM product, Rangers Assistant, has been released. For more details, please read the full article: https://x.com/RangersProtocol/status/18566358

1👏1🔥1

Signed Rangers Protocol Admin

17 Oct 2024, 10:05 UTC681 views4 reactionsread 12 August 2026
Photo

📜Rangers September Monthly Report This month, the mainnet has been running smoothly, with a total of 66.64 million blocks produced. The network continues to operate efficiently and securely. 💥Exciting News - Virtual Machine Upgrade: The team is actively working on upgrading the Virtual Machine (VM). We will have more supported languages in coding smart contracts, approximately 10 times the efficiency. Read On: htt

👏21🔥1

Signed Rangers Protocol Admin

16 Oct 2024, 03:33 UTC551 views3 reactionsread 12 August 2026
Photo

🚀Huge Rewards for Game Developers! 🚀 Rangers Now refunds 100% of your gas fees! 🥂Don’t miss out—follow us and get in on the action today https://x.com/RangersProtocol/status/1846393370899632628

👍2🔥1

Signed Rangers Protocol Admin

10 Oct 2024, 10:05 UTC785 views3 reactionsread 12 August 2026
Photo

🗣The Rangers team is reminding all users: $RPG token conversion website will officially close on October 31st The conversion process is simple & can be completed by visiting $RPG Token Conversion Website: https://airdrop-rpg.rangersprotocol.com To access the updated claim site, visit $RPG Claim Website: https://rpgclaim.rangersprotocol.com/home 👇For more info, read our guide: https://rpg.build/final-deadline-for-r

🔥21

Signed Rangers Protocol Admin

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

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

“Rangers Procotol Announcements” (@RangersProtocolAnnouncement), 6,267 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/RangersProtocolAnnouncement.

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.