Telegram RegisterThe public register of Telegram
Telegram profile photo for Купер.тех

Channel

Купер.тех

@tech_kuper

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

8,127subscribers

+47 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-1001598837262
TypeChannel
Username@tech_kuper
Created28 September 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live29 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/tech_kuper

Growth

8,0778,1308,103.57 August 2026 — 8,080 subscribers7 August 2026 — 8,077 subscribers10 August 2026 — 8,078 subscribers14 August 2026 — 8,086 subscribers17 August 2026 — 8,089 subscribers20 August 2026 — 8,097 subscribers24 August 2026 — 8,095 subscribers26 August 2026 — 8,130 subscribers29 August 2026 — 8,127 subscribers8,1277 August 202629 August 2026
9 measurements spanning 22 days, net +47. 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 8,069–8,138 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 13:538,127-3
26 Aug 2026, 21:438,130+35
24 Aug 2026, 04:178,095-2
20 Aug 2026, 07:218,097+8
17 Aug 2026, 11:238,089+3
14 Aug 2026, 08:178,086+8
10 Aug 2026, 16:148,078+1
7 Aug 2026, 14:408,077-3
7 Aug 2026, 04:458,080first reading

Engagement

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

ERR · 30 days
19.2%
avg views ÷ 8,127 subscribers
Avg views / post
1,560
4 posts measured
Reaction rate
1.10%
reactions ÷ views · ER floor
Posts in window
4
of 7 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 25 August 2026
Posts held7 (17 July 202625 August 2026)
Views total6,257
Reactions total69
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 18:36 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

159 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 23.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54204633427728417233723.3%
custom 51883424236710308733622.6%
3220.1%
🔥3220.1%
🏆95.66%
❤‍🔥42.52%
🤔42.52%
🆒21.26%
🎉21.26%
👏10.629%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

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

25 Aug 2026, 11:00 UTC827 views18 reactionsread 28 August 2026
Photo

😎 Вот бы лето не кончалось... Лето каждый год начинается одинаково: кажется, что впереди куча времени, а потом внезапно уже конец августа, и ты пытаешься понять, куда делись три месяца. Сейчас самое время подвести летние итоги — не грустить, что август почти закончился, а вспомнить, сколько всего классного успело случиться. И, конечно же, передать летний вайб дальше! Заглядывайте в каналы коллег, подписывайтесь и

custom 51883424236710308738custom 54204633427728417236❤‍🔥4

13 Aug 2026, 07:34 UTC≈1,690 views1 reactionsread 28 August 2026
Video message

Video message, posted without a caption

1

13 Aug 2026, 07:34 UTC≈1,520 views23 reactionsread 28 August 2026

🌧 Никто из нас не представлял середину августа такой дождливой... До выходных осталось совсем немного, но хорошей погоды пока не видно. Ставьте огонечки 🔥, чтобы высушить лужи и плавать можно было только в бассейне, а не по пути на работу!

🔥15custom 54204633427728417236🆒1custom 51883424236710308731

5 Aug 2026, 13:55 UTC≈2,220 views27 reactionsread 28 August 2026
Photo

📢 Что происходит с React Native прямо сейчас — и почему технология до сих пор остаётся одним из рабочих вариантов для кросс-платформенной разработки? Евгений Прокопьев, руководитель группы мобильной разработки, стал гостем подкаста Evrone Development. Поговорили о том, как изменилась архитектура, куда делся bridge и насколько выросла реальная производительность. Отдельно остановились на том, что сейчас больше всего

10custom 51883424236710308739custom 54204633427728417235🔥2🆒1

30 Jul 2026, 11:43 UTC≈2,160 views18 reactionsread 28 August 2026
Forwarded from @ML_kuperPhoto

✨Хороший work-life balance сам себя не настроит В ML много задач, где мозг постоянно что-то считает, сравнивает, проверяет гипотезы и пытается понять, почему метрика снова ведёт себя странно. Поэтому особенно важно уметь переключаться и отдыхать от рутины. Спросили ребят из команды: от руководителей до стажеров, чем они занимаются в свободное от работы время, что любят и как расслабляются. Читайте в карточках выше

custom 542046334277284172375custom 51883424236710308734🤔2

20 Jul 2026, 08:06 UTC≈2,320 views34 reactionsread 25 August 2026
Photo

⚽️Выспались и готовы работать — или смотрели вчера ночью футбол? Чемпионат мира в 2026 году получился богатым на яркие моменты, а интернет, как обычно, быстро превратил их в мемы. Мы не смогли пройти мимо и собрали футбольные кадры, которые слишком хорошо описывают корпоративную жизнь.

🔥14🏆8custom 54204633427728417236🎉2🤔2👏1custom 51883424236710308731

17 Jul 2026, 09:03 UTC≈1,860 views38 reactionsread 12 August 2026
Photo

💭 Лучше спросите Евгения React Native — важный стек для нашей мобильной разработки, а лучший способ поговорить о нём — задать вопросы человеку, который видит и техническую сторону, и продуктовый контекст. Поэтому решили сделать короткий Q&A с Евгением Прокопьевым, руководителем группы мобильной разработки: 🟢Как изменился React Native за последние 2–3 года? Можно с уверенностью сказать, что фреймворк повзрослел: ап

16custom 518834242367103087313custom 54204633427728417237🏆1🔥1

Showing the 7 most recent of 7 posts we hold for @tech_kuper. 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 — 125,927 of 1,626,935entries 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 5 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Avito Career
@avito_career · 65,167
Telegram ranks this channel #6 of 98 here — alongside 97 others — read 21 August 2026
Alfa Digital
@alfadigital_jobs · 54,284
Telegram ranks this channel #9 of 99 here — alongside 98 others — read 24 August 2026
Карьера в Сбере!
@careersber · 136,961
Telegram ranks this channel #15 of 96 here — alongside 95 others — read 13 August 2026
Young&&Yandex
@Young_and_Yandex · 110,319
Telegram ranks this channel #30 of 92 here — alongside 91 others — read 14 August 2026
Школа 21
@school21sber · 71,318
Telegram ranks this channel #61 of 94 here — alongside 93 others — read 19 August 2026
Т-Образование
@tbank_education · 111,935
Telegram ranks this channel #68 of 91 here — alongside 90 others — read 14 August 2026
Т-Банк: работа с клиентами
@tbank_team · 68,509
Telegram ranks this channel #70 of 96 here — alongside 95 others — read 20 August 2026
Карьера в ВТБ
@vtb_career · 57,940
Telegram ranks this channel #74 of 93 here — alongside 92 others — read 23 August 2026

This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Купер.тех” (@tech_kuper), 8,127 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/tech_kuper.

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.