Telegram RegisterThe public register of Telegram

Channel

19:24

@tme1924

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

2,622subscribers

+9 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001168413847
TypeChannel
Username@tme1924
Created27 January 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/tme1924

Growth

2,6132,6222,617.56 August 2026 — 2,613 subscribers7 August 2026 — 2,615 subscribers10 August 2026 — 2,616 subscribers14 August 2026 — 2,622 subscribers6 August 202614 August 2026
4 measurements spanning 8 days, net +9. 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 2,612–2,623 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 00:482,622+6
10 Aug 2026, 09:142,616+1
7 Aug 2026, 02:312,615+2
6 Aug 2026, 12:332,613first reading

Engagement

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

ERR · 30 days
82.6%
avg views ÷ 2,622 subscribers
Avg views / post
2,170
9 posts measured
Reaction rate
3.73%
reactions ÷ views · ER floor
Posts in window
9
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (21 June 20265 August 2026)
Views total19,503
Reactions total728
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:20 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

Video runtime
15s
Average length
15s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

1,651 reactions across 20 posts, in 24 distinct kinds. The most used accounts for 21.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 534577328596976826235621.6%
😁26416.0%
custom 524240103813206117620112.2%
🔥1348.12%
1177.09%
👍835.03%
🕊784.72%
🙏593.57%
custom 5393140972743841269583.51%
custom 5273833425575355571553.33%
custom 5465638169569430937452.73%
custom 5465376382722803540392.36%
custom 5343788839280325285321.94%
custom 5273820429004317075291.76%
custom 5465405219133242151261.57%
💔241.45%
🎉160.969%
🤬150.909%
🤡60.363%
👎40.242%
4 further kinds100.606%

Custom emoji. 9 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 20 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 1,651reactions 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 21 June 2026 to 5 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

5 Aug 2026, 07:08 UTC753 views88 reactionsread 7 August 2026
Forwarded from @ibns1924

Мечты сбываются! Кроме уже понятных выездов, в этом году случится ещё один интереснейший вояж — ЕВРОвыезд в братскую Беларусь! Жодинское «Торпедо» в этом году празднует 65-летие, и в честь этого события они решили провести настоящий гала-матч. Для такого дела пригласили лучший клуб из возможных — «Торпедо Москва»! В том же историческом 1961 году, 14 сентября, был собран первый самосвал БелАЗ-540, который, кстати,

custom 534577328596976826245🔥23custom 5242401038132061176117👎1😁1

2 Aug 2026, 12:30 UTC≈1,930 views86 reactionsread 7 August 2026

Эй, Гоцук, где твой Пиджак?! - разносится над стадионом

😁56🔥18custom 539314097274384126911👎1

2 Aug 2026, 07:15 UTC≈1,980 views29 reactionsread 7 August 2026

7 вопросов перед «Арсеналом» 1. Что с Юшиным? Как дела у Кирилла Иванова, главного врача клуба? Почему вдруг отказались от его комментариев? Очередная идея блокировки информации - точно не лучший вариант. По слухам у Юшина повреждение задней поверхности бедра, «Шинник» он пропустил, «Арсенал» пропустит скорее всего тоже. 2. Снова ждать в старте Галояна? Галоян забил «Волге», выйдя на замену, и растворился в ярос

🔥13custom 534577328596976826296😁1

31 Jul 2026, 16:16 UTC≈1,050 views31 reactionsread 7 August 2026
Forwarded from @KeyOn32

Билеты на матч в Туле. 2 августа Арсенал-Торпедо Цена билета 250₽ 🔥Только за наличку! В субботу в Туле по договоренности В воскресенье за час до матча у гостевого входа. Все на сектор в белых футболках или любой игровой Т. 🏁🏁🏁

🔥247

30 Jul 2026, 18:35 UTC≈1,470 views96 reactionsread 7 August 2026
Photo

Есть ли у нас пресс-служба?!)))

😁70custom 546537638272280354011🔥8custom 527382042900431707561

27 Jul 2026, 15:55 UTC≈4,410 views144 reactionsread 7 August 2026

Сегодня Юлии Комовой исполнилось бы 39 лет.... Человек жив, пока его помнят... 🙏🏻🏆⚽️💔

🕊78🙏38💔24custom 52424010381320611764

26 Jul 2026, 11:31 UTC≈2,450 views53 reactionsread 7 August 2026

7 вопросов перед «Шинником» 1. Сдаст ли Сторожук самый неудобный тест? «Шинник» первый в этом сезоне оборонительный соперник, насколько команда будет убедительна против такого сопротивления - любопытно. «Урал» стремился доминировать, «Волга» - играть, в обоих случаях решение нашли. Посмотрим, что будут делать с ярославским бетоном, который при Бояринцеве ещё и неплохо стартовал. 2. Ждём изменения в старте? Обор

custom 524240103813206117628custom 534378883928032528513👍73😁2

19 Jul 2026, 18:04 UTC≈2,600 views165 reactionsread 7 August 2026

На багаже Кононова!!!

😁114custom 539314097274384126929🎉10🤡5custom 52738334255753555713💯2custom 52738204290043170752

19 Jul 2026, 13:16 UTC≈2,860 views36 reactionsread 7 August 2026

ВОПРОСЫ ПЕРЕД «ВОЛГОЙ» 1) Что по составу? Роганович провалил матч в Екатеринбурге, сохранит ли он место в старте - вопрос принципиальности и последовательности Сторожука. Замена, со слов тренера, была по игровым показателям, Бояна Александр Александрович поддержал, но если мы правильно научились считывать главного тренера, Роганович, как минимум игру с «Волгой» начнет на лавке. Варианта замены два: прямой по позиции

👍257custom 53457732859697682624

13 Jul 2026, 16:00 UTC≈3,250 views137 reactionsread 7 August 2026

🔥🔥🔥 Есть первая победа в новом сезоне, нового тренера и новой надежды!!! Тяжелый РАВНЫЙ матч, тяжелая рубка, но удача улыбнулась нам!!! И оооочень многие сораТники надеялись на это и предчувствовали - вы знаете, в каких чатах это читать) Всех поздравляем!!! Анализы и разборы игры - позднее!!!

custom 53457732859697682626543custom 524240103813206117620🔥9

13 Jul 2026, 13:05 UTC≈3,470 views114 reactionsread 7 August 2026
Video

Пиджак тоже на выезде)) Ловит овации))

custom 527383342557535557144🔥31custom 546563816956943093716custom 539314097274384126911😁8👎2🤡1🤬1

13 Jul 2026, 10:03 UTC≈2,750 views75 reactionsread 7 August 2026

⁉️Один вопрос перед «Уралом» - Что представляет из себя «Торпедо» Сторожука? Речь именно о игровых решениях тренера, всё остальное, включая руководство и его планы в ближней и дальней перспективе, останется за рамками игры. Мы знаем, что команда готова хорошо (знаем, а не видели), знаем, что её, команду, подвели к старту чемпионата в максимальных кондициях. Знаем, что ставка Сторожука именно на старт сезона - ни вр

custom 534577328596976826249custom 524240103813206117614custom 54656381695694309379🤔21

Showing the 12 most recent of 20 posts we hold for @tme1924. 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 — 388,182 of 1,350,102entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 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.

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.

“19:24” (@tme1924), 2,622 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/tme1924.

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.