5 measurements spanning 10 days, net +8. 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 1,203–1,213 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
20 Aug 2026, 08:23
1,212
+4
14 Aug 2026, 00:38
1,208
+3
10 Aug 2026, 21:51
1,205
+1
10 Aug 2026, 10:00
1,204
no change
10 Aug 2026, 09:46
1,204
first reading
Engagement
20 posts held, back to 12 July 2025 — 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.
ERR · 30 days
11.5%
avg views ÷ 1,212 subscribers
Avg views / post
139
1 post measured
Reaction rate
5.04%
reactions ÷ views · ER floor
Posts in window
1
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 8 August 2026
Posts held
20 (12 July 2025 – 8 August 2026)
Views total
139
Reactions total
7
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Aug 2026, 10:00 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
176 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 71.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
125
71.0%
🔥
23
13.1%
👍
16
9.09%
🥰
6
3.41%
😱
3
1.70%
👏
2
1.14%
🎉
1
0.568%
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 19 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 176reactions 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 12 July 2025 to 8 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.
Telegram Stars
Stars received
3
across the posts below
Posts paid on
2
of 20 we hold a reading for · 10%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Coreproxyio. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 12 July 2025 to 8 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
THE WAIT IS OVER! 🎉🆕
We’re excited to announce that CoreProxy.io now accepts card payments!
The payment option many of you have been waiting for is finally here. ▶️
💱 Pay easily with your credit or debit card
⚡️ Fast & convenient checkout
🛡 Secure payment processing
🌐 Available for customers worldwide
🔥 Get your proxies instantly and get to work
No more hassle - just choose your package, pay by card, and you're go…
💡 New Tools Section Live at CoreProxy!
We're excited to introduce our brand-new Tools Center designed to help you test, verify, and troubleshoot your proxies and network connections with ease.
🛡 Tools Included:
✔️ Proxy Checker – Verify proxy functionality and connectivity
📍 IP Location Lookup – Check geolocation and IP details instantly
📊 Proxy Benchmark – Compare proxy performance and reliability
⚡️ Proxy Speed …
🔈 BIG Updates at CoreProxy! 🔔
We’re excited to announce a complete redesign of our CoreProxy website! 🎉
✨ Cleaner interface
⚡️ Faster experience
🖥 Improved dashboard & navigation
⚙️ Better usability across all devices
We’d love to hear your feedback!
If you have any suggestions, ideas, or run into any issues, please reach out to our support team - we’re always listening. 💬
━━━━━━━━━━━━━━━
🔔 Also Happy To Introdu…
📢 CoreProxy.io Update
We are currently aware of some issues affecting the website due to ongoing backend updates. Our team is actively working to resolve them and improve performance and stability.
Thank you for your patience and understanding 💙
We’re happy to inform you that the issue has now been successfully resolved.
If anyone is still experiencing any issues, please don’t hesitate to reach out to our support team at @Coreproxy_Support, and we will be glad to assist you promptly.
Thank you again for your patience, understanding, and continued trust in CoreProxy.io.
Dear CoreProxy.io Family,
Thank you for being a valued part of CoreProxy.io. We wish you a peaceful, blessed, and secure Ramadan! 💙
We would also like to inform you that we are aware of an issue affecting the extension of rotating residential plans purchased before February 27, 2026. Our team is actively working on resolving this matter in the best and most efficient way possible.
Additionally, the coupon code RAM…
🌙 Ramadan Kareem from CoreProxy! ✨
As the holy month begins, we’re excited to share special updates and offers with you!
🎁 Exclusive Ramadan Offer
Get an extra 30% OFF any package of your choice.
- Code: RAMADAN
- Availability: Limited time only!
📢 New: Scaling Made Smarter
As part of our ongoing commitment to provide better value and flexibility, we’ve updated our pricing structure and introduced improved bulk dis…
❄️ Christmas Update from CoreProxy ❄️
This festive season, we’re happy to share some important improvements made to the CoreProxy platform - thanks to your valuable feedback.
▶️ What’s New?
• Upgraded dashboard performance
• Improved user interface for a smoother experience
• Enhanced and simplified checkout process
• Multiple bug fixes and stability improvements
Your suggestions and reports played a key role in t…
🚀 Mobile Proxy Service Update - We're Back Online!
We experienced a brief downtime with our mobile proxy service, but everything is now fully restored and running smoothly. Thank you for your patience!
Here’s what our mobile proxies offer:
📡 Supports HTTP & SOCKS5 Protocols
🌍 Worldwide Locations
🎯 Country / City Targeting
🏢 ISP Targeting
📶 Clean Mobile IPs from real carrier networks
🛡 Low Fraud Score, High-Trust R…
We’re aware that some visitors may experience timeout errors when connecting.
Our team is actively investigating the issue and working on a fix. 🔧
Thank you for your patience and continued trust in CoreProxy.
✔️ All Systems Back Online ✔️
We’re glad to let you know that everything is now fully up and running - with even better stability and faster performance than before ⚡️
If you were affected during the downtime, you can reach out to our support team for refunds or replacements for the missing days:
✉️ Support: @Coreproxy_Support
Thank you for your patience and continued trust in CoreProxy 💙
❤9👍2
Showing the 12 most recent of 20 posts we hold for @Coreproxyio. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank — 256,816 of 1,583,249entries 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 6 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.
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 20 August 2026 — this
entry's latest reading, not the date you are reading this.
“CoreProxy.io” (@Coreproxyio), 1,212 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/Coreproxyio.
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.