Telegram RegisterThe public register of Telegram
Telegram profile photo for ᴘʀᴏxʏ_ᴛᴍ_ᴜɴʟɪᴍɪᴛᴇᴅ

Channel

ᴘʀᴏxʏ_ᴛᴍ_ᴜɴʟɪᴍɪᴛᴇᴅ

@Proxy_tm_unlimited

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Cite this entry

6,755subscribers

+189 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-1002665811692
TypeChannel
Username@Proxy_tm_unlimited
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Proxy_tm_unlimited

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 47% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Proxy_tm_unlimited/1434 · this entry6 Aug 2026, 14:25 UTC@grammproxy/716176 Aug 2026, 15:00 UTC0.8934 minutes
@Proxy_tm_unlimited/1435 · this entry7 Aug 2026, 16:21 UTC@grammproxy/716217 Aug 2026, 16:33 UTC0.8713 minutes
@Proxy_tm_unlimited/1409 · this entry1 Aug 2026, 13:45 UTC@grammproxy/716031 Aug 2026, 19:37 UTC0.865.9 hours
@Proxy_tm_unlimited/1433 · this entry5 Aug 2026, 11:46 UTC@grammproxy/716155 Aug 2026, 12:08 UTC0.8222 minutes
@Proxy_tm_unlimited/1414 · this entry2 Aug 2026, 08:41 UTC@grammproxy/716062 Aug 2026, 10:30 UTC0.801.8 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@grammproxy5 (5/5 hand-verifiable sample passed)0.8534 minutesthis entry (50)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 30 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @Proxy_tm_unlimited — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

6,5666,7556,660.57 August 2026 — 6,566 subscribers7 August 2026 — 6,566 subscribers8 August 2026 — 6,568 subscribers11 August 2026 — 6,623 subscribers14 August 2026 — 6,755 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +189. 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,538–6,783 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 21:276,755+132
11 Aug 2026, 05:426,623+55
8 Aug 2026, 03:596,568+2
7 Aug 2026, 19:476,566no change
7 Aug 2026, 19:406,566first reading

Engagement

41 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 7 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
30.5%
avg views ÷ 6,755 subscribers
Avg views / post
2,060
41 posts measured
Reaction rate
1.11%
reactions ÷ views · ER floor
Posts in window
41
of 41 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 36 of 41 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 11 August 2026
Posts held41 (30 July 202611 August 2026)
Views total84,484
Reactions total882
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:59 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

882 reactions across 36 posts, in 12 distinct kinds. The most used accounts for 74.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
65474.1%
🔥9610.9%
697.82%
🎉192.15%
❤‍🔥111.25%
🕊101.13%
🥰80.907%
👾60.68%
🤩50.567%
💘20.227%
🍓10.113%
💯10.113%

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

Measured over the 41 most recent posts we hold, published 30 July 2026 to 11 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

11 Aug 2026, 19:17 UTC703 views16 reactionsread 12 August 2026

https://t.me/proxy?server=boost.telehelp.top&port=443&secret=eed4f42b03cae4d1a0f2e2a51454a6e0d7626f6f73742e74656c6568656c702e746f70 https://t.me/proxy?server=chpr.kochvpn.pw&port=443&secret=eedf0415e539b7fedca70bd50370b699e5636870722e6b6f636876706e2e7077 https://t.me/proxy?server=ne.koraivpn.cfd&port=443&secret=ee9f08d078eb2b66285616e9c67f5370f16e652e6b6f72616976706e2e636664 https://t.me/proxy?server=vk.nftauction

151

11 Aug 2026, 17:00 UTC≈1,020 views15 reactionsread 12 August 2026
Photo

🪟 Windows бесит? Исправь за 5 минут. В WinExperty — короткие решения без воды: ошибки, тормоза, полезные функции и софт. 👉 Подпишись, чтобы не искать решение часами. На правах рекламы

❤‍🔥9🔥4💯1🤩1

11 Aug 2026, 16:59 UTC990 views14 reactionsread 12 August 2026

https://t.me/proxy?server=195.209.210.163&port=8443&secret=ee39f2f36ec93338eae372566cb078c0aa7467322e676f696e67666c75782e6f6e6c696e65 tg://proxy?server=echo01.whiskeytangofoxtrot.lol&port=443&secret=ee2313a25d4190befe5ac411390e3b71de6563686f30312e776869736b657974616e676f666f7874726f742e6c6f6c https://t.me/proxy?server=213.219.212.18&port=443&secret=dd9e1dde0de02a2e7c22d10e2fff841013 https://t.me/proxy?server=imppr

9🔥2🥰21

11 Aug 2026, 11:06 UTC≈1,520 views20 reactionsread 12 August 2026

https://t.me/proxy?server=cdn.nowabst.net&port=853&secret=ee55aabc9752a9d9d379e02943cf811795766b2e636f6d https://t.me/proxy?server=mt.nowabst.net&port=853&secret=ee4e9fcd5caf6e9be2f8ec43e370e902d6766b2e636f6d https://t.me/proxy?server=srv.utkanos.life&port=443&secret=eec3f59ac6ee4ae5f57bc581a1fb321bbf7372762e75746b616e6f732e6c696665 https://t.me/proxy?server=hub.utkanos.life&port=443&secret=ee40854ff173077abb80426

163🎉1

11 Aug 2026, 06:34 UTC≈1,660 views31 reactionsread 12 August 2026

https://t.me/proxy?server=82.115.13.164&port=443&secret=6150a3afbbd6c13027a90b397e3ae3ff https://t.me/proxy?server=de1proxy.kochvpn.pw&port=443&secret=eebca4be8f43140ac1cb90f54704a97c7564653170726f78792e6b6f636876706e2e7077 https://t.me/proxy?server=durev.chunkycorp.shop&port=443&secret=ee6a0333c1db3f8eaba5c76731a44203b6617669746f2e7275 https://t.me/proxy?server=freeinternet.skin&port=2052&secret=ee6a0333c1db3f8ea

22🔥52🕊2

10 Aug 2026, 10:34 UTC≈2,200 views31 reactionsread 12 August 2026

tg://proxy?server=redflag.yazaebalsyadelatproxy.cc&port=443&secret=ee69e899d89ec68e220ca177557322b27f726564666c61672e79617a616562616c73796164656c617470726f78792e6363 https://t.me/proxy?server=spproxy.kochvpn.pw&port=8443&secret=ee3cf83879692052fb9fe48c8b5b5f7bee737070726f78792e6b6f636876706e2e7077 https://t.me/proxy?server=app2.klyuch1k.org&port=443&secret=eea7829bb257995a5d0e83f5345b7033ae617070322e6b6c7975636831

24🔥52

10 Aug 2026, 09:49 UTC≈2,100 views24 reactionsread 12 August 2026

https://t.me/proxy?server=wolf.baboon.digital&port=443&secret=eea21bac021798ed6830e6d6c67ba496ad706574726f766963682e7275 https://t.me/proxy?server=45.144.52.104&port=2302&secret=dd2084c7e58d8213296a3206da70356c81 https://t.me/proxy?server=45.131.108.207&port=443&secret=79e344818749bd7ac519130220c25d09 https://t.me/proxy?server=eerie.proxytales.life&port=443&secret=ee6a0333c1db3f8eaba5c76731a44203b6617669746f2e7275

18🔥41🤩1

Showing the 12 most recent of 41 posts we hold for @Proxy_tm_unlimited. 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“ᴘʀᴏxʏ_ᴛᴍ_ᴜɴʟɪᴍɪᴛᴇᴅ” (@Proxy_tm_unlimited), 6,755 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Proxy_tm_unlimited.

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.