Telegram RegisterThe public register of Telegram
Telegram profile photo for Прокси tg | настройка

Channel

Прокси tg | настройка

@proxy_telegramt

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

13,648subscribers

+2,262 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002105869070
TypeChannel
Username@proxy_telegramt
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/proxy_telegramt

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 56% 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@proxy_telegramt/94 · this entry14 Jun 2026, 06:31 UTC@adrconf/30014 Jun 2026, 06:53 UTC0.9323 minutes
@proxy_telegramt/110 · this entry1 Aug 2026, 07:07 UTC@adrconf/3065 Aug 2026, 11:02 UTC0.924 days
@proxy_telegramt/103 · this entry8 Jul 2026, 16:46 UTC@adrconf/3028 Jul 2026, 18:28 UTC0.881.7 hours
@proxy_telegramt/91 · this entry10 Jun 2026, 11:49 UTC@adrconf/29611 Jun 2026, 05:49 UTC0.8718 hours
@proxy_telegramt/93 · this entry12 Jun 2026, 07:49 UTC@adrconf/29913 Jun 2026, 11:33 UTC0.8728 hours
@proxy_telegramt/100 · this entry20 Jun 2026, 06:00 UTC@adrconf/30121 Jun 2026, 15:02 UTC0.8433 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@adrconf7 (7/7 hand-verifiable sample passed)0.8726 hoursthis entry (70)

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 10 June 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_telegramt — 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 7 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

11,38613,64812,5177 August 2026 — 11,386 subscribers8 August 2026 — 11,430 subscribers9 August 2026 — 11,519 subscribers10 August 2026 — 11,569 subscribers11 August 2026 — 11,667 subscribers12 August 2026 — 11,768 subscribers13 August 2026 — 11,821 subscribers14 August 2026 — 11,930 subscribers16 August 2026 — 12,074 subscribers17 August 2026 — 12,146 subscribers18 August 2026 — 12,222 subscribers19 August 2026 — 12,306 subscribers20 August 2026 — 12,362 subscribers21 August 2026 — 12,410 subscribers22 August 2026 — 12,467 subscribers24 August 2026 — 12,553 subscribers25 August 2026 — 12,608 subscribers26 August 2026 — 12,660 subscribers27 August 2026 — 12,729 subscribers28 August 2026 — 12,783 subscribers29 August 2026 — 12,847 subscribers30 August 2026 — 12,887 subscribers31 August 2026 — 12,936 subscribers1 September 2026 — 12,992 subscribers2 September 2026 — 13,052 subscribers3 September 2026 — 13,116 subscribers5 September 2026 — 13,268 subscribers9 September 2026 — 13,478 subscribers11 September 2026 — 13,648 subscribers7 August 202611 September 2026
29 measurements spanning 35 days, net +2,262. 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 11,047–13,987 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
11 Sept 2026, 19:3613,648+170
9 Sept 2026, 04:5813,478+210
5 Sept 2026, 22:1713,268+152
3 Sept 2026, 16:3913,116+64
2 Sept 2026, 10:1813,052+60
1 Sept 2026, 10:2312,992+56
31 Aug 2026, 12:5712,936+49
30 Aug 2026, 12:4512,887+40
29 Aug 2026, 10:5612,847+64
28 Aug 2026, 07:3612,783+54
27 Aug 2026, 09:2812,729+69
26 Aug 2026, 08:5512,660+52
25 Aug 2026, 11:3312,608+55
24 Aug 2026, 12:1412,553+86
22 Aug 2026, 22:2412,467+57
21 Aug 2026, 15:2812,410+48
20 Aug 2026, 13:5812,362+56
19 Aug 2026, 13:0412,306+84
18 Aug 2026, 16:3512,222+76
17 Aug 2026, 14:1712,146first reading

Engagement

33 posts held, back to 10 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 45 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
84.5%
avg views ÷ 13,648 subscribers
Avg views / post
11,500
10 posts measured
Reaction rate
0.658%
reactions ÷ views · ER floor
Posts in window
10
of 33 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
WindowRolling 30 days · latest post in window 2 September 2026
Posts held33 (10 June 20262 September 2026)
Views total115,390
Reactions total759
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 20:47 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

2,596 reactions across 33 posts, in 23 distinct kinds. The most used accounts for 63.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,64863.5%
👍36013.9%
🤝1626.24%
🔥1616.20%
🙏522.00%
👏431.66%
🙊321.23%
🥰311.19%
💋180.693%
❤‍🔥160.616%
💘150.578%
🍓100.385%
👀70.27%
💊70.27%
🕊70.27%
🤷‍♂70.27%
🤪50.193%
👎40.154%
👌30.116%
😎30.116%
3 further kinds50.193%

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

Measured over the 33 most recent posts we hold, published 10 June 2026 to 2 September 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
57
across the posts below
Posts paid on
25
of 33 we hold a reading for · 76%
Most on one post
7
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @proxy_telegramt. 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 33 most recent posts we hold for this entry, published 10 June 2026 to 2 September 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.

Recent posts

2 Sept 2026, 14:59 UTC≈3,170 views52 reactionsread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=l01.antenna-mzt.live&port=443&secret=ee5a42e3752e724f2fdae9c117e7f076fe6c30312e616e74656e6e612d6d7a742e6c697665 https://t.me/proxy?server=130.49.150.132&port=443&secret=ee00d85706e58f9b5ead3b6c8a08d984df636c6f75642e6d61696c2e7275 https://t.me/proxy?server=mesh.eeluma.org&port=443&secret=eedcaae509a2455bbfc6165f1708fd5c586d6573682e65656c756d612e6f7267 https://t.me/proxy?serv

40👍6🙏3🥰2💋1

29 Aug 2026, 06:51 UTC≈10,100 views76 reactions3 Starsread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=103.118.209.9&port=443&secret=ee87285de664d75001b306b0ca6f3a33ec74672e6c696d626f76706e2e7275 https://t.me/proxy?server=freenet.ddnsgeek.com&port=443&secret=eef43cfa0cb4b1d1124643927f09de3c7b70696e7465726573742e636f6d https://t.me/proxy?server=googel.alo-otp.info.&port=25565&secret=ee104462821249bd7ac519130220c25d0963646e2e79656b74616e65742e636f6d https://t.me/proxy?server=1

55👍14🤝4💋2🎉1

27 Aug 2026, 08:47 UTC≈10,900 views71 reactions1 Starread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=media8.happtg.org&port=443&secret=eeaf794bcc20f70b1436b6b92b01b207e26d61676e69742e7275 https://t.me/proxy?server=skill-issue.top&port=853&secret=ee54ce330e4690cc297d2b031ff3f288b06d742e616b656e61692e636c69636b https://t.me/proxy?server=cover-acid.top&port=853&secret=ee54ce330e4690cc297d2b031ff3f288b06d742e616b656e61692e636c69636b https://t.me/proxy?server=focus-ultimate.top

44👍13❤‍🔥6💊4💋4

26 Aug 2026, 05:47 UTC≈11,200 views55 reactionsread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=static.antenna-mzt.live&port=443&secret=7lpC43Uuck8v2unBF-fwdv5zdG9yZS5zdGVhbXBvd2VyZWQuY29t https://t.me/proxy?server=freeconnect.lol&port=443&secret=eef7a565db46f8f5bf156054d86db42969617669746f2e7275 https://t.me/proxy?server=185.173.145.5&port=443&secret=ee68ae8284982465dfcb198342d01cdedb6f7a6f6e2e7275 https://t.me/proxy?server=shared2.ddproxy.xyz&port=443&secret=eeddddd

43👍10💘1🔥1

24 Aug 2026, 09:17 UTC≈12,300 views70 reactions3 Starsread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=t4.myrka.digital&port=443&secret=ee1111222233334444555566667777888874342e6d79726b612e6469676974616c https://t.me/proxy?server=jarko.myrka.digital&port=443&secret=ee04daa35f7150d1d16c43f270c26831086a61726b6f2e6d79726b612e6469676974616c https://t.me/proxy?server=zarinpluse.info&port=22&secret=eeNEgYdJvXrFGRMCIMJdCQ https://t.me/proxy?server=akenai.top&port=853&secret=ee54ce33

43👍16💘4🥰4👏3

24 Aug 2026, 09:17 UTC≈8,420 views67 reactions3 Starsread 2 September 2026

Друзья, Telegram тестирует новый вид web прокси, который должен быть более незаметным и менее подверженный блокировкам, сейчас такие прокси внедрили на Telegram Desktop, у кого есть телеграм на ноутбуке обновите телеграм до последней версии и пробуйте вот эти прокси: https://t.me/webproxy?server=web.prx.mom&secret=9d4983f30be13908b85897fa41b9be45 tg://webproxy?server=netherlands.gamma-kvn.com&secret=1f39305372faa2

🔥4016👍9💘1🤷1

22 Aug 2026, 13:50 UTC≈10,400 views60 reactions3 Starsread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=45.11.92.251&port=443&secret=eea339ca5cc76d3f7946a1356a63f0947d6b69636b2e636f6d https://t.me/proxy?server=94.228.171.174&port=443&secret=ee68ae8284982465dfcb198342d01cdedb6f7a6f6e2e7275 https://t.me/proxy?server=150.241.65.113&port=443&secret=eeb87dc15f92c391155eccb9293e2881796f7a6f6e2e7275 https://t.me/proxy?server=159.194.234.168&port=443&secret=eedddddddddddddddddddddddd

42🔥8👍6💋2🥰2

20 Aug 2026, 07:54 UTC≈12,700 views93 reactions3 Starsread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=s1.postpulse.space&port=443&secret=ee402900cd57c3daef160c3a2aef80a29c6164312e617269786f2e73686f70 https://t.me/proxy?server=ad2.arixo.shop&port=443&secret=eed09b88cbbd4e744865b890e5a0bd26876164322e617269786f2e73686f70 https://t.me/proxy?server=155.212.141.156&port=443&secret=eedddddddddddddddddddddddddddddddd6d2e6265626f6f2e7275 https://t.me/proxy?server=redflag.yazaebalsya

63👍16🔥8💊3💋3

15 Aug 2026, 08:28 UTC≈19,200 views91 reactionsread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=45.147.28.139&port=443&secret=ee74800ce2de3966b457dfc27717db52d07a6f6f6d2e7573 https://t.me/proxy?server=horse.baboon.digital&port=7000&secret=ee81c8859edbe6515397c8a79550708aaf636c6f7564666c6172652e636f6d https://t.me/proxy?server=nl2.v6n.tech&port=443&secret=ee0aedf5da176681ddc584345068c518437777772e626f6f6b696e672e636f6d https://t.me/proxy?server=ad2.arixo.shop&port=443&

53👍20🔥10💋4🤝4

14 Aug 2026, 09:43 UTC≈17,000 views124 reactionsread 2 September 2026

Друзья, РКН массово блокирует прокси, актуальные для вас сейчас: https://t.me/proxy?server=veltaro.ru&port=443&secret=dd9dd5353c6c0485f0f64b1471c9f3d370 https://t.me/proxy?server=shared.ddproxy.xyz&port=443&secret=eedddddddddddddddddddddddddddddddd6d2e6265626f6f2e7275 https://t.me/proxy?server=t3.myrka.digital&port=444&secret=7oiId3dmZlVVREQzMyIiERF0My5teXJrYS5kaWdpdGFs https://t.me/proxy?server=impforyou.notdev.

87🤝22👍9🥰4💘2

12 Aug 2026, 06:54 UTC≈15,500 views73 reactions1 Starread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=gg.fsproxy.site&port=8443&secret=eec89526f2260269efb17e34e1c05221ad67672e667370726f78792e73697465 https://t.me/proxy?server=proxy-dag.ru&port=443&secret=ee94fc2b484af6e1e1c87e6576b33c257579612e7275 https://t.me/proxy?server=redflag.yazaebalsyadelatproxy.cc&port=443&secret=ee69e899d89ec68e220ca177557322b27f726564666c61672e79617a616562616c73796164656c617470726f78792e6363 http

47👍13🤝7❤‍🔥3🥰3

11 Aug 2026, 06:50 UTC≈12,900 views73 reactions7 Starsread 2 September 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=lynette.myrka.digital&port=443&secret=ee54701e1686de96a44721501a7bee9e4c6c796e657474652e6d79726b612e6469676974616c https://t.me/proxy?server=185.114.156.160&port=443&secret=ee212b8d26ec678658af5cd0180f33d3047a6f6f6d2e7573 https://t.me/proxy?server=213.165.63.226&port=443&secret=eec8bcc2216d80c00b093510420635ceb0736f6e792e7275 https://t.me/proxy?server=195.133.35.199&port=44

48👍10🔥10🤝3👏2

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

Posts edited after publishing

@proxy_telegramt edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
26 August 2026
Most recent edit
27 August 2026

Mentions

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.

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

“Прокси tg | настройка” (@proxy_telegramt), 13,648 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/proxy_telegramt.

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.