Channel
@proxysale
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
2,475subscribers
-14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001694812212 |
|---|---|
| Type | Channel |
| Usernames | @proxyline @proxysale |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 22 August 2026 |
| On Telegram | t.me/proxysale |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 16:55 | 2,475 | -1 |
| 19 Aug 2026, 03:03 | 2,476 | no change |
| 19 Aug 2026, 00:34 | 2,476 | +4 |
| 15 Aug 2026, 20:49 | 2,472 | no change |
| 15 Aug 2026, 18:09 | 2,472 | -8 |
| 12 Aug 2026, 04:02 | 2,480 | no change |
| 11 Aug 2026, 22:02 | 2,480 | -3 |
| 9 Aug 2026, 05:51 | 2,483 | no change |
| 9 Aug 2026, 05:11 | 2,483 | -3 |
| 6 Aug 2026, 15:53 | 2,486 | no change |
| 6 Aug 2026, 14:08 | 2,486 | -3 |
| 6 Aug 2026, 06:47 | 2,489 | first reading |
20 posts held, back to 7 May 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 13 June 2026. An engagement rate over an empty window would be a number about nothing.
24 reactions across 9 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 100.0% |
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 13 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 24reactions 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 7 May 2024 to 13 June 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @proxysale. 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 7 May 2024 to 13 June 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 traffic gets expensive fast — unless your price per GB drops as you scale. With proxy-sale.pro, you can start small and move up to high-volume plans when your workload grows. Pool 1 — best value for daily proxy traffic From $1/GB for 1 GB Down to $0.55/GB at 10 TB Pool 2 — more power for demanding workloads From $2/GB for 1 GB Down to $0.90/GB at 10 TB More GB = lower cost per GB. Stable sessions. Worldwide IP …
❤2
Posted without readable text
Subaccounts help separate workflows When several tasks or team members use the same proxy service, separation becomes important. Subaccounts make it easier to organize access, distribute traffic and keep usage more transparent. This can be useful when one project needs one setup, while another project requires different limits or locations. Instead of mixing everything together, teams can manage proxy usage in a …
❤4
Traffic control is part of a stable workflow Residential proxy traffic should be easy to monitor. When a team can clearly see purchased traffic, remaining traffic and usage by users, planning becomes much easier. This helps avoid confusion during active projects and gives a better view of how resources are used. For business analytics, localized testing and market research, traffic visibility is important because…
❤2
GEO coverage is not only about the number of countries A large country list looks strong on paper. But in practical work, the real value is in having the right regions available for the exact task. For market research, price monitoring and localized QA, relevant GEO access helps teams compare regional data more accurately and keep workflows organized. Sometimes one stable region is more useful than many locations…
❤1
The dashboard should make proxy work easier A good proxy service is not only about access. It is also about control. When teams work with residential proxies, they need to see traffic balance, manage users, choose locations and generate endpoints without unnecessary steps. This is why dashboard experience matters. Clear management helps teams understand what is available, what is already used and what should be …
The best proxy choice usually starts with 3 questions Before choosing a setup, it helps to answer three simple questions: Which GEOs do you actually need? How stable should the session be? How much traffic will the task require? These questions sound basic, but they shape everything that comes after: routing, sessions, scaling and overall efficiency. In many cases, the right setup becomes much easier to see once …
❤2
Residential vs datacenter is not a “better or worse” question This comparison is often framed the wrong way. It is not really about which type is better in general. It is about which type fits the task better. Datacenter proxies are often used where simplicity and straightforward routing are enough. Residential proxies become more relevant when real-user IPs and GEO-based access are a bigger part of the workflow. …
Pool size is useful. Pool quality is what matters A large residential proxy pool is a good thing. But on its own, it does not explain how well that pool will perform in real work. What matters more is how the pool behaves across practical tasks: GEO availability, consistency, traffic handling and overall predictability. In other words, size can be impressive. Quality is what makes it usable. That is the differen…
Why session behavior matters more than people expect A lot of proxy discussions focus on IP count, traffic or pricing. But session behavior is often just as important. If the workflow depends on continuity, predictable session handling can make the whole process easier to manage. This matters in regional checks, localized testing and other tasks where consistency inside one session is important. Sometimes the dif…
A long country list does not solve everything Seeing a large list of available GEOs looks good on paper. But in practice, the real question is simpler: do you have the right regions for the exact task you need to run? For many workflows, quality of GEO access matters more than quantity. Stable access to the needed locations is usually more valuable than a long list of countries you will never use. Good GEO planni…
Price per GB is not the whole picture When people choose residential proxies, the first thing they usually compare is price. That makes sense. But in real work, price alone rarely tells the full story. If the task depends on stable GEO, predictable sessions and solid IP quality, the better choice is often the setup that works more consistently over time, not just the one that looks cheaper at first glance. For ma…
❤3
Showing the 12 most recent of 20 posts we hold for @proxysale. 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 — 546,026 of 1,584,733entries 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 1 registered channel — 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Proxy-sale.pro 0.7$/GB” (@proxysale), 2,475 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/proxysale.
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.