Telegram RegisterThe public register of Telegram
Telegram profile photo for kатерина`s speaking

Channel

kатерина`s speaking

@katerinasspeaking

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

769subscribers

-13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001933903593
TypeChannel
Username@katerinasspeaking
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live27 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/katerinasspeaking

Growth

7697837767 August 2026 — 782 subscribers8 August 2026 — 782 subscribers8 August 2026 — 783 subscribers14 August 2026 — 780 subscribers20 August 2026 — 775 subscribers27 August 2026 — 769 subscribers7 August 202627 August 2026
6 measurements spanning 20 days, net -13. 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 767–785 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 12:04769-6
20 Aug 2026, 20:53775-5
14 Aug 2026, 17:33780-3
8 Aug 2026, 02:06783+1
8 Aug 2026, 01:47782no change
7 Aug 2026, 17:02782first reading

Engagement

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

ERR · 30 days
21.0%
avg views ÷ 769 subscribers
Avg views / post
162
4 posts measured
Reaction rate
11.6%
reactions ÷ views · ER floor
Posts in window
4
of 4 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 held4 (4 August 20265 August 2026)
Views total646
Reactions total75
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:47 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

75 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 37.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2837.3%
💘2026.7%
❤‍🔥1621.3%
custom 542237846010019824845.33%
custom 520183159739282560934.00%
🔥22.67%
custom 539540023721068683611.33%
🍓11.33%

Custom emoji. 3 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 are Telegram’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 4 of the 4 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 75 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 4 most recent posts we hold, published 4 August 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, 08:25 UTC135 views10 reactionsread 8 August 2026
Photo

Герман Гессе «Степной волк» Первое прочитанное мной произведения у Гессе, и мне показалось, что это не лучший вариант у автора для первого почтения. Возможно, это конкретно я пока с трудом воспринимаю такие тексты, а, может быть, у писателя все книги настолько тяжело читаются. Совсем отсутствуют главы + используется прикол «книга в книге», поэтому приходится максимально концентрироваться на тексте, чтобы уловить смыс

💘5custom 520183159739282560931🍓1

4 Aug 2026, 20:34 UTC178 views24 reactionsread 8 August 2026
Photo

к сожалению, маленький московский уикенд подходит к концу :(( в следующий раз увижу белокаменную только в сентябре, но расстраиваться из-за этого не буду, ведь она успеет мне надоесть еще 300 раз за 10 учебных месяцев. так что давайте вернемся к позитивному сторителлингу - за эту поездку успела: - исследовать подмосковье - переехать (ОПЯТЬ) - проведать горячо любимого московского друга и самого нежного в мире московс

❤‍🔥116💘5custom 54223784601001982482

4 Aug 2026, 20:13 UTC174 views22 reactionsread 8 August 2026
Photo

📍Чистые пруды совершенно особой любовью в этом году прониклась к чистым прудам. живу в москве уже два года, и за это время начала складываться своего рода традиция, обычай - раз в полгода/год выбираю одно место, в котором буду проводить 85% своего времени вне дома. в этом году такой локацией стали чистые пруды со своими чудесными бульварами. вы и представить себе не можете, сколько прогулок, встреч, сплетен, обедов,

11❤‍🔥5💘4custom 54223784601001982482

4 Aug 2026, 20:04 UTC159 views19 reactionsread 8 August 2026
Photo

сегодня еще успели с моей crazy friend обойти все бульварное кольцо в москве! планировали сделать это с апреля, но все не складывалось, а вот сегодня, не поверите, сложилось! лето в москве просто чудесно. смотря на эти фото, даже и представить не могу, что скоро осень с ее слякотью, сыростью и холодом :((

10💘6🔥2custom 53954002372106868361

Showing the 4 most recent of 4 posts we hold for @katerinasspeaking. 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.

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.

история и котики / ЕГЭ ОГЭ 2027 стадикэтс иик
@historyandcats · 36,280
Telegram ranks this channel #47 of 72 here — alongside 71 others — read 1 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“kатерина`s speaking” (@katerinasspeaking), 769 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/katerinasspeaking.

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.