Telegram RegisterThe public register of Telegram
Telegram profile photo for Telegram Proxy

Channel

Telegram Proxy

@proxytg7day

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

16,088subscribers

-2,898 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-1003711638942
TypeChannel
Username@proxytg7day
Created3 March 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/proxytg7day

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 the other topics.

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 in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@proxytgtestperiod4/61731 Jul 2026, 13:16 UTC@proxytg7day/77 · this entry31 Jul 2026, 13:16 UTC1.00under a minute
@proxytgtestperiod4/68222 Aug 2026, 14:03 UTC@proxytg7day/91 · this entry22 Aug 2026, 14:03 UTC1.00under a minute
@proxytgtestperiod4/72528 Aug 2026, 12:41 UTC@proxytg7day/115 · this entry28 Aug 2026, 12:41 UTC1.00under a minute
@proxytgtestperiod4/6425 Aug 2026, 15:03 UTC@proxytg7day/120 · this entry29 Aug 2026, 15:03 UTC0.7924 days
@proxytgtestperiod4/67221 Aug 2026, 15:00 UTC@proxytg7day/107 · this entry26 Aug 2026, 12:04 UTC0.795 days
@proxytg7day/105 · this entry25 Aug 2026, 15:03 UTC@proxytgtestperiod4/71927 Aug 2026, 15:03 UTC0.792 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@proxytgtestperiod417 (8/8 hand-verifiable sample passed)0.874 days@proxytgtestperiod4 (9–8)
@proxii14 (8/8 hand-verifiable sample passed)0.846 daysthis entry (8–6)
@proxytgtestperiod59 (8/8 hand-verifiable sample passed)0.92under a minutethis entry (5–4)
@proxytg_news7 (7/7 hand-verifiable sample passed)0.97under a minute@proxytg_news (7–0)

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. 22 of the 26 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 53 comparable posts for this entry, running 11 June 2026 to 3 September 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).

Of the group of 4 channels, the one whose matching posts we hold earliest is @proxytgtestperiod4. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

16,07418,98617,53016,0887 August 202611 November 2026
62 measurements spanning 95 days, net -2,898. 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 15,637–19,423 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
11 Nov 2026, 02:5616,088+14
9 Nov 2026, 08:0616,074-9
7 Nov 2026, 23:0816,083-11
6 Nov 2026, 17:5516,094-16
5 Nov 2026, 19:5016,110-14
4 Nov 2026, 22:4916,124-10
3 Nov 2026, 21:3616,134-12
2 Nov 2026, 22:1516,146-9
1 Nov 2026, 21:5916,155-5
1 Nov 2026, 01:2816,160-12
31 Oct 2026, 03:5216,172-17
30 Oct 2026, 06:3916,189-26
29 Oct 2026, 03:0016,215-18
28 Oct 2026, 00:4816,233-11
27 Oct 2026, 01:4916,244-7
26 Oct 2026, 03:3716,251-7
25 Oct 2026, 01:1116,258-18
24 Oct 2026, 01:0716,276-9
22 Oct 2026, 22:1116,285-14
21 Oct 2026, 22:1516,299first reading

Engagement

55 posts held, back to 3 March 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 71 pages of 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 55 posts for this entry, the most recent from 3 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

3 Sept 2026, 05:02 UTC921 viewsread 3 September 2026

🎁 Бесплатный MTProto-прокси для Telegram Скорость: 100 Мб/с Универсальность: работает c VPN и без Срок действия: 24 часа Статус: активен Server: relay.proxyb.site Port: 443 Secret: eec444f67e0ab0d7e203519a9eb8e15aa572656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

2 Sept 2026, 15:05 UTC≈1,590 viewsread 3 September 2026

🎁 Персональный MTProto-прокси для Telegram Скорость: до 1000 Мб/с Универсальность: работает c VPN и без Срок действия: бесконечно Статус: активен Server: relay.proxyb.site Port: 443 Secret: ee76cf545df87c320c61a0724658b1bac472656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

2 Sept 2026, 12:02 UTC≈1,750 viewsread 3 September 2026

🎁 Бесплатный MTProto-прокси для Telegram Скорость: 100 Мб/с Универсальность: работает c VPN и без Срок действия: 24 часа Статус: активен Server: relay.proxyb.site Port: 443 Secret: ee93b953f16faaa590f00633d05899722b72656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

2 Sept 2026, 05:06 UTC≈1,960 viewsread 3 September 2026

🎁 Бесплатный MTProto-прокси для Telegram Скорость: 100 Мб/с Универсальность: работает c VPN и без Срок действия: 24 часа Статус: активен Server: relay.proxyb.site Port: 443 Secret: ee35984e0c9ef357d59228230c1ffb0db772656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

1 Sept 2026, 15:02 UTC≈2,130 viewsread 3 September 2026

🎁 Персональный MTProto-прокси для Telegram Скорость: до 1000 Мб/с Универсальность: работает c VPN и без Срок действия: бесконечно Статус: активен Server: relay.proxyb.site Port: 443 Secret: eeb0b07dfaf6a785d4fa502318ccce246f72656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

1 Sept 2026, 14:04 UTC≈2,000 viewsread 3 September 2026
Photo

Спасибо, что доверили нам важную миссию — обеспечивать стабильный и безопасный доступ к интернету, каким он должен быть. Теперь мы идём дальше и запускаем ВсеGPT — единый сервис с прямым доступом к оригинальным ChatGPT, Gemini и Claude в их родном интерфейсе. Сейчас сервис работает в тестовом режиме, поэтому все функции доступны бесплатно. Переходите в бота по кнопке ниже и оцените всё сами.

1 Sept 2026, 12:00 UTC≈2,050 viewsread 3 September 2026

🎁 Бесплатный MTProto-прокси для Telegram Скорость: 100 Мб/с Универсальность: работает c VPN и без Срок действия: 24 часа Статус: активен Server: relay.proxyb.site Port: 443 Secret: ee2b198019c09003546c9e068886ec4c5772656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

1 Sept 2026, 05:01 UTC≈2,220 viewsread 3 September 2026

🎁 Бесплатный MTProto-прокси для Telegram Скорость: 100 Мб/с Универсальность: работает c VPN и без Срок действия: 24 часа Статус: активен Server: relay.proxyb.site Port: 443 Secret: ee7b79354e9db2048b7aaa7acc8e8d529372656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

31 Aug 2026, 15:04 UTC≈2,310 viewsread 3 September 2026

🎁 Персональный MTProto-прокси для Telegram Скорость: до 1000 Мб/с Универсальность: работает c VPN и без Срок действия: бесконечно Статус: активен Server: relay.proxyb.site Port: 443 Secret: ee28392405d3e3a289a7b107f1e6d244a972656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

31 Aug 2026, 12:04 UTC≈2,340 viewsread 3 September 2026

🎁 Бесплатный MTProto-прокси для Telegram Скорость: 100 Мб/с Универсальность: работает c VPN и без Срок действия: 24 часа Статус: активен Server: relay.proxyb.site Port: 443 Secret: eef485c511a85bd7e8db9211a48f3a7cfa72656c61792e70726f7879622e73697465 Хочешь такой же прокси, но без деактивации? Получи его бесплатно по кнопке ниже 👇 @proxytg

31 Aug 2026, 05:00 UTC≈2,420 viewsread 3 September 2026

⛔️ MTProto-прокси отключён Статус: ❌ неактивен Server: relay.proxyb.site Port: 443 Secret: ee8cf9883b60f495c756da3942ede574d772656c61792e70726f7879622e73697465 Этот прокси больше не работает. Получи новый рабочий прокси бесплатно по кнопке ниже 👇 @proxytg

30 Aug 2026, 15:04 UTC≈2,420 viewsread 3 September 2026

⛔️ MTProto-прокси отключён Статус: ❌ неактивен Server: relay.proxyb.site Port: 443 Secret: ee33ae5ab945bb3b0500c620fda347d4c772656c61792e70726f7879622e73697465 Этот прокси больше не работает. Получи новый рабочий прокси бесплатно по кнопке ниже 👇 @proxytg

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

Posts edited after publishing

@proxytg7day edited 21 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
24 August 2026
Most recent edit
3 September 2026

Posts recorded as deleted after publishing

We recorded 1 post on @proxytg7day as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
24 August 2026
Most recent seen missing
24 August 2026
Median time before seen missing
7 days
Seen missing in the last 30 days
0

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“Telegram Proxy” (@proxytg7day), 16,088 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/proxytg7day.

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.