6 measurements spanning 16 days, net +9. 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 4,775β4,799 and does not start at zero.
Measurement log β every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
23 Aug 2026, 09:59
4,787
-4
16 Aug 2026, 20:39
4,791
-5
13 Aug 2026, 10:36
4,796
+10
10 Aug 2026, 20:55
4,786
+5
7 Aug 2026, 11:31
4,781
+3
7 Aug 2026, 08:46
4,778
first reading
Engagement
21 posts held, back to 25 November 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 8 pagesof Telegramβs post history, 20 posts per page.
ERR Β· 30 days
19.7%
avg views Γ· 4,787 subscribers
Avg views / post
944
3 posts measured
Reaction rate
0.988%
reactions Γ· views Β· ER floor
Posts in window
3
of 21 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 10 August 2026
Posts held
21 (25 November 2025 β 10 August 2026)
Views total
2,833
Reactions total
28
Forwards / comments
not exposed by the public surface β not measured, not estimated
Readings taken
12 Aug 2026, 05:19 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
195 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 42.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
β€
83
42.6%
π₯
43
22.1%
π€£
27
13.8%
π
22
11.3%
β‘
6
3.08%
π₯°
5
2.56%
π±
4
2.05%
π
2
1.03%
π€
2
1.03%
π
1
0.513%
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 20 of the 21 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 195reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 21 most recent posts we hold, published 25 November 2025 to 10 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
60
across the posts below
Posts paid on
2
of 20 we hold a reading for Β· 10%
Most on one post
30
single highest reading
A paid reaction is a reader spending Telegram Stars β bought with money β on a post by @ProdigyNet. 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 21 most recent posts we hold for this entry, published 25 November 2025 to 10 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.
π Proxy Geolocation β Quick Clarification
Hey everyone,
Getting different countries for the same IP across sites? That's expected β there's no single universal geolocation database. IPinfo, Scamalytics, IP2Location and supplier DBs often disagree due to:
Different update schedules
ASN/routing propagation delays
Different classification methods
Recently we found IPinfo showing outdated locations β e.g. DE proxies β¦
π Datacenter Proxies β Upgraded & Sale
Some of you ran into instability and slowdowns on our Datacenter network recently β we hear you. We've rebuilt how it handles connections from the ground up, and those issues are now resolved.
What's changed:
β‘ Faster β a leaner, tuned data path
π‘οΈ Stable β no more slowdowns under sustained load
π Reliable β consistent throughput even at high concurrency
Thanks for sticking wβ¦
π Shared ISP Proxies β Now Live at Proxies.fo
We've been hard at work expanding our network, and we're proud to launch our brand-new Shared ISP Proxies β premium ISP IPs built for speed, stability, and trust.
Powered by Tier 1 ISPs with 10Gbps uplinks, our Shared ISP pool delivers high-trust static IPs at shared-pool pricing β perfect for account management, checkout flows, and high-traffic scraping.
π20,000+ ISP β¦
π±Mobile Proxies - One of The Most Awaited Product at Proxies.fo
Weβve been hard at work over the past weeks, developing one of the largest π±Mobile Proxy pools, featuring IPs exclusively from ISPs providing 4G and 5G Internet services, such as T-Mobile & Verizon in πΊπΈUnited States.
We are proud to announce that our Mobile Pool will offer approximately over 1,000,000 active IPs at any given time, spanning over π 100β¦
π§ Scheduled Maintenance Notice
We will be performing scheduled maintenance on our datacenter network on Tuesday at 14:00 EST.
β’ Estimated downtime: ~1 hour
β’ Reason: Upgrading our datacenter NIC for improved throughput and speed
During this window, you may experience brief interruptions or degraded performance. Service will be restored as soon as the upgrade is complete.
Thank you for your patience β these improvβ¦
π’ Service Notice β HTTP/3 / UDP Traffic (DC Product)
We wanted to give you a heads-up that HTTP/3 / UDP traffic is temporarily unavailable on our Datacenter (DC) product. Our team is actively working to resolve this as quickly as possible.
β All other traffic types remain fully operational β this issue is isolated exclusively to HTTP/3 / UDP on the DC product. Residential, ISP, and all other proxy traffic are unaffβ¦
π¨β¨ Proxies.Fo GIVEAWAY ALERT β¨π¨
π 1GB Residential Proxy Access π
π Available to 100 Registered Users ONLY on proxies.fo!
CLICK HERE - > Claim Here
π₯ Whatβs Inside? π₯
π 1GB Residential Proxy
π Rotating / Sticky Options to match your needs
π Millions of Premium Residential IPs
β‘οΈ Unlimited Threads for unmatched speed
πUDP SOCKS5 SUPPORT
---
β° HURRY! 100 Spots Available! β Exclusive, powerful, and ready for you!β¦
π RESIDENTIAL β UDP NOW LIVE
UDP is now supported on our Residential SOCKS5 network.
Same gateway. Same port :13337. Nothing to reconfigure.
ββββββββββββββββββββββ
What you can do now
Route HTTP/3 & QUIC through residential IPs
Real UDP via SOCKS5 β not TCP fallback
Same auth, same endpoint, same setup
ββββββββββββββββββββββ
Most residential providers are TCP-only. We're not.
Existing customers get instant acceβ¦
New Documentation is Live!
We've just dropped our brand new docs site β everything you need to get the most out of Proxies.fo, all in one clean place.
π What's covered:
β’ Residential β country, state, city & ASN targeting across 180+ countries
β’ Datacenter β IPv4 & IPv6 with sticky sessions and unlimited threads
β’ ISP Proxies β premium static IPs on Tier 1 networks
β’ Code examples in Python, Node.js, Go, PHP, Ruby,β¦
πͺπΊ EU Datacenter Proxies Is back Online
Netherlands is live again across two products.
π₯ Datacenter Β· IPv4
πΊπΈ USA β 2,500 IPs
π³π± Netherlands β 2,500 IPs
Fresh, clean, unburned pool
HTTPS / SOCKS5 / UDP
Gateway: dcp-eu.proxies.fo
π‘ IPv6 Β· Rotating
/29 split across πΊπΈ US & π³π± NL
Unlimited concurrent connections
HTTPS / SOCKS5 / UDP
Existing customers get instant access β no action needed.
Purchase Now - >
π₯4β€3
Showing the 12 most recent of 21 posts we hold for @ProdigyNet. 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 β 639,437 of 1,584,486entries 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.
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 23 August 2026 β this
entry's latest reading, not the date you are reading this.
βProxies.fo πβ (@ProdigyNet), 4,787 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/ProdigyNet.
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.