Telegram RegisterThe public register of Telegram
Telegram profile photo for tmp_notes_Speaker

Channel

tmp_notes_Speaker

@Thomas_Speaker

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

13subscribers

+3 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1004379638534
TypeChannel
Username@Thomas_Speaker
Created5 August 2026measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/Thomas_Speaker

Growth

101311.512 Aug 2026, 19:33 — 10 subscribers13 Aug 2026, 11:58 — 13 subscribers12 Aug 2026, 19:3313 Aug 2026, 11:58
2 measurements taken within a single day, net +3. 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 10–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 11:5813+3
12 Aug 2026, 19:3310first reading

Engagement

18 posts held, back to 5 August 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
130.3%
avg views ÷ 13 subscribers
Avg views / post
16.9
17 posts measured
Reaction rate
35.8%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 11 August 2026
Posts held18 (5 August 202611 August 2026)
Views total288
Reactions total103
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 19:33 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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😈8380.6%
😁87.77%
🤓54.85%
🤪43.88%
👾10.971%
💋10.971%
🥰10.971%

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

Measured over the 18 most recent posts we hold, published 5 August 2026 to 11 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

11 Aug 2026, 16:04 UTC12 views5 reactionsread 12 August 2026

Запись №5.0 Маршрут беглеца удалось восстановить по камерам почти без разрывов. Он двигался совсем предсказуемо: дворами, перебежками, избегая освещенных проспектов. Очевидно, старался не покидать слепые зоны. Но город тебе не лес, в наше время камеры понатыканы у любой помойки. Забавный момент, в переулке за прачечной на третьей линии он остановился минуты на четыре. Прислонился к стене, достал смартфон и принялся

😈4😁1

10 Aug 2026, 18:22 UTC14 views3 reactionsread 12 August 2026

Запись №4.0. Клон №187 вернулся на базу с опозданием в 36 минут. С его слов, на завершающем этапе облета квадрата G7, когда он уже настраивался на обратный курс, им был замечен наблюдатель. Мужчина скрывался за кустарником возле старого водонапорного блока. Как только их взгляды пересеклись, вышеупомянутый проявил панику и незамедлительно бросмлся в бегство. 187-й утверждает, что опознал в беглеце одного из участни

😈3

9 Aug 2026, 19:12 UTC14 views5 reactionsread 12 August 2026

Запись №3.2. Проверил палату №187. Осмотрел его крыло, сгибается и разгибается под правильным углом, хорошо заживает. Покормил — ест нормально, хотя суетится меньше обычного. Молчал почти все время, очевидно, в обиде на меня. Хотя, признаюсь, я был даже рад. Весь день голова трещит по швам, не хватало еще выслушивать его словесную диарею.

😈4👾1

9 Aug 2026, 09:12 UTC15 views6 reactionsread 12 August 2026

Запись №3.1. Достало. Кручусь здесь как белка в колесе, и все без толку, потому-что люди, которые по идее должны были меня разгрузить, приносят больше проблем, чем пользы.

😈6

9 Aug 2026, 05:00 UTC15 views7 reactionsread 12 August 2026

Запись №3.0. Проверял реакцию №187 на внештатные ситуации. Ввел в симуляцию внезапное препятствие, столб дыма на траектории полета. Клон успешно уклонился, но при посадке повредил правое крыло. Пришлось отключить симуляцию. Проверил степень повреждения, ничего критичного. Обычный ушиб, через пару дней снова сможет летать. Клон устроил такую драму, что у меня разболелась голова. Принял решение запереть его в палате д

😈7

8 Aug 2026, 19:54 UTC15 views6 reactionsread 12 August 2026

Запись №2.2. И снова провал. Если бы энтузиазмом можно было заменить глупость — №187 был бы гением.

😈5🥰1

8 Aug 2026, 10:42 UTC18 views6 reactionsread 12 August 2026

Запись №2.1. Попытка №34 восстановить схему первичного излучателя потерпела очередной провал. Судя по всему, была ошибка в расчете волновой дифракции. Роберт всегда решал эти уравнения быстрее. У него было какое-то иррациональное, антинаучное чутье на физику. Я же руководствуюсь системным перебором вариантов, но он занимает месяцы работы, которых у меня нет.

😈5💋1

8 Aug 2026, 01:37 UTC17 views5 reactionsread 12 August 2026

Запись №2.0. 04:37. Четвертый день подряд просыпаюсь раньше будильника. Организм, кажется, нашел новый способ саботажа.

😈5

7 Aug 2026, 14:05 UTC20 views6 reactionsread 12 August 2026

Запись №1.2. Мониторинг соцсетей показывает спад протестной активности на 9%. Хороший показатель. Люди быстро забывают, когда их не кормить новыми раздражителями. Проблема в том, что сбежавшие клоны и есть ходячие раздражители. Нужно найти их раньше журналистов.

😈6

7 Aug 2026, 09:47 UTC18 views5 reactionsread 12 August 2026

Запись №1.1. Клон №187 прошел базовый тест на когнитивные способности. Как я и ожидал, результат: нижняя граница нормы. Он интерпретирует самые прямые намерения с неожиданных сторон. Как будто нарочно хулиганит каждый раз, снова и снова. Я надеюсь, что это связано с какими-то физическими отклонениями и может быть исправлено в будущем. Для моих целей недостаточно лишь физической силы, мой подчиненный должен быть расс

😈5

7 Aug 2026, 07:48 UTC14 views4 reactionsread 12 August 2026

Запись №1.0. Сегодня поместил №187 в симуляцию открытого пространства. Ветровой поток 15 м/с. Клон держится в воздухе неуверенно, но стабильно. Размах крыльев соответствует расчетным параметрам. По возвращении в лабораторный бокс он 12 минут рассказывал мне об ощущении ветра в перьях, о том, как бодрят полеты, и что ему хотелось бы делать это почаще. Я дал ему энциклопедию о птицах, чтобы тот отстал.

😈4

6 Aug 2026, 18:56 UTC16 views5 reactionsread 12 August 2026

Запись №0.4. Система зафиксировала попытку несанкционированного доступа к архиву "BOBSOC Legacy". Средний уровень допуска, значит кто-то из младшего персонала. Либо журналист под прикрытием, либо просто любопытный дурак. Отправил данные службе безопасности. Увольнять лично не буду — нет времени на истерики.

😈5

Showing the 12 most recent of 18 posts we hold for @Thomas_Speaker. 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,111,797 of 1,549,376entries 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.

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

“tmp_notes_Speaker” (@Thomas_Speaker), 13 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Thomas_Speaker.

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.