Telegram RegisterThe public register of Telegram

Channel

ТГ прокси

@pushkaPROXY

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

233subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003862068749
TypeChannel
Username@pushkaPROXY
DescriptionЯ- @Turbo_PushkaOFFICAL чат- https://t.me/pushkaBAZA
CreatedBetween 1 February 2026 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/pushkaPROXY

Growth

2338 Aug 2026, 01:46 — 233 subscribers8 Aug 2026, 10:03 — 233 subscribers8 Aug 2026, 01:468 Aug 2026, 10:03
2 measurements taken within a single day. 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 232–234 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 10:03233no change
8 Aug 2026, 01:46233first reading

Engagement

20 posts held, back to 31 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
95.7%
avg views ÷ 233 subscribers
Avg views / post
223
5 posts measured
Reaction rate
2.61%
reactions ÷ views · ER floor
Posts in window
5
of 20 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 4 of 5 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 14 July 2026
Posts held20 (31 May 202614 July 2026)
Views total1,115
Reactions total23
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:03 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.

What this channel posts

Photos
7
Links
22

Lifetime counters from Telegram’s own channel header, read 8 August 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.

Reaction mix

76 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 60.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4660.5%
👍1519.7%
💋79.21%
👎45.26%
🆒22.63%
11.32%
🕊11.32%

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 17 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 76reactions 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 31 May 2026 to 14 July 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

14 Jul 2026, 11:43 UTC273 views4 reactionsread 8 August 2026

https://t.me/proxy?server=mirror.balalaika.click&port=443&secret=ee204fd0f2f4584c289c6aa284e46ed6406d6972726f722e62616c616c61696b612e636c69636b https://t.me/proxy?server=tg.deepwoof.net&port=443&secret=ee6164732e78352e727530ac46ef4d53 https://t.me/proxy?server=185.241.195.77&port=443&secret=eedcaae509a2455bbfc6165f1708fd5c586d61782e7275 https://t.me/proxy?server=data.n3o.lol&port=5432&secret=0404040400004444000044

👍3👎1

14 Jul 2026, 11:43 UTC234 viewsread 8 August 2026

Это короче за все пропущенные деньки

14 Jul 2026, 11:43 UTC234 views14 reactionsread 8 August 2026

Надеюсь я заслужил ваше прощение

10💋2👍1🕊1

14 Jul 2026, 11:13 UTC189 views3 reactionsread 8 August 2026

Папочка возвращается по чуть чуть

3

14 Jul 2026, 11:13 UTC185 views2 reactionsread 8 August 2026

https://t.me/proxy?server=cloud.neoqua.pro&port=443&secret=ee4c40bfc1c32022e21d85e597be8652f7636c6f75642e6e656f7175612e70726f https://t.me/proxy?server=proxy.lodkirmm.ru&port=8443&secret=ee16309abd572d284b309ef26bd7a3f685d0b7d0ba70726f78792e6c6f646b69726d6d2e7275 https://t.me/proxy?server=ad5.arixo.shop&port=443&secret=ee995469d4d5a3221f69a1cc24d1cafa506164322e617269786f2e73686f70 https://t.me/proxy?server=max.ru.

2

23 Jun 2026, 18:26 UTC381 views2 reactionsread 8 August 2026

https://t.me/proxy?server=85.192.33.204&port=8443&secret=ee9e1dde0de02a2e7c22d10e2fff84101374676e6e2e6c697665

👍2

19 Jun 2026, 06:43 UTC463 viewsread 8 August 2026

https://t.me/proxy?server=mt.nowabst.net&port=853&secret=7hKJP_0gRM7NMRBO3AKn5VhhZHMueDUucnU https://t.me/proxy?server=mt.femboylover.org&port=443&secret=5f52936aa7e559b6bf6b6c62d28f0ae6 https://t.me/proxy?server=blue.protocolsix.info&port=22&secret=ee1603010200010001fc030386e24c3add626973636f7474692e79656b74616e65742e636f6d https://t.me/proxy?server=max.kimt.click&port=443&secret=ee1b153cf06dbd43c6085c359a6702eb9

18 Jun 2026, 18:02 UTC313 views3 reactionsread 8 August 2026

Если телеграмм не работает, попробуйте MTProxy. Например: tg://proxy?server=main.mtproxy.pw&port=443&secret=ee3f8a91c2d7e04b6a9f12c5e8370bd4aa27786170692e6f7a6f6e2e727527

3

18 Jun 2026, 18:02 UTC317 views2 reactionsread 8 August 2026

Если телеграмм не работает, попробуйте MTProxy. Например: tg://proxy?server=main.mtproxy.pw&port=443&secret=ee3f8a91c2d7e04b6a9f12c5e8370bd4aa27786170692e6f7a6f6e2e727527

2

16 Jun 2026, 09:50 UTC409 views6 reactionsread 8 August 2026

Проксятина для ЧС https://t.me/proxy?server=mt1.kurduk.store&port=443&secret=ee2c359976c0e74101ab25d285b51faf306d74312e6b757264756b2e73746f7265 https://t.me/proxy?server=orbit3.mtproxy.zip&port=443&secret=ee3f8a91c2d7e04b6a9f12c5e8370bd4aa786170692e6f7a6f6e2e7275 https://t.me/proxy?server=signal3.mtproxy.zip&port=443&secret=ee3f8a91c2d7e04b6a9f12c5e8370bd4aa786170692e6f7a6f6e2e7275 https://t.me/proxy?server=cargo.

👍42

8 Jun 2026, 10:37 UTC450 views2 reactionsread 8 August 2026
Forwarded from @rostunnel

⚡️ Выпускаем MTProto + Fake TLS — Германия tg://proxy?server=tourist.maxmir.ru&port=443&secret=eeb021d11b931a1387a957f4ddad6b89e031632e7275 Делитесь с друзьями! ❤️ Поддержать ⛔️ Дисклеймер 🇷🇺 @rostunnel

2

4 Jun 2026, 14:33 UTC613 views4 reactionsread 8 August 2026

Сейчас ркн борщат сложно стало находить нормальные прокси

4

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

Citation-graph rank

Citation-graph rank — 1,086,481 of 1,160,990entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

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

“ТГ прокси” (@pushkaPROXY), 233 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/pushkaPROXY.

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.