Posted without readable text
custom 533924731079678457916custom 526503451934958596912

Channel
@silencesubs
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
702subscribers
+93 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003789693616 |
|---|---|
| Type | Channel |
| Username | @silencesubs |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/silencesubs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 09:37 | 702 | +93 |
| 12 Aug 2026, 11:31 | 609 | first reading |
13 posts held, back to 28 July 2026 — the 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 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 12 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 13 (28 July 2026 – 12 August 2026) |
| Views total | 6,318 |
| Reactions total | 844 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 11:31 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.
844 reactions across 12 posts, in 31 distinct kinds. The most used accounts for 6.64% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5217982164779426084 | 56 | 6.64% | |
| custom 5264822567008505820 | 56 | 6.64% | |
| custom 5424629903431604726 | 53 | 6.28% | |
| custom 5244730430824930577 | 51 | 6.04% | |
| custom 5247129286023865760 | 51 | 6.04% | |
| custom 5436368212260321788 | 49 | 5.81% | |
| custom 5463364139005019251 | 48 | 5.69% | |
| custom 5215680242697399716 | 45 | 5.33% | |
| custom 5280856002047014097 | 39 | 4.62% | |
| custom 5253574185099219391 | 35 | 4.15% | |
| custom 5375284096454926146 | 33 | 3.91% | |
| custom 5247064715485531744 | 29 | 3.44% | |
| custom 5411207443436839549 | 24 | 2.84% | |
| custom 5217637502243856309 | 22 | 2.61% | |
| custom 5246855615002729218 | 21 | 2.49% | |
| custom 5449506736262115689 | 21 | 2.49% | |
| custom 5213312302673066376 | 20 | 2.37% | |
| custom 5217679146246757867 | 19 | 2.25% | |
| custom 5280929665031110471 | 18 | 2.13% | |
| custom 5375526229531206446 | 18 | 2.13% | |
| 11 further kinds | 136 | 16.1% |
Custom emoji. Every row above is a 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 12 of the 13 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 844reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 28 July 2026 to 12 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.
Posted without readable text
custom 533924731079678457916custom 526503451934958596912
ㅤㅤ ₊˚ ʚ 🌟 #Мечта №3:: ☆ – Собрать свою домашнюю ㅤбиблиотеку, на полках которой можно будет найти все-все полюбившиеся мне произведения японских писателей ୧ ‧₊˚ 🤩 🤩 ⋅
custom 528085600204701409739custom 528092966503111047118
‧₊ ᵎᵎ 🤩🤩• You cannot suffer the past or future because they do not exist. ㅤㅤ What you are suffering is your memory and your imagination ‧₊˚ 🪮 ⋅
custom 537528409645492614633custom 537552622953120644618
Posted without readable text
custom 521568024269739971645custom 521331230267306637620
File, posted without a caption
ㅤㅤㅤㅤㅤ୧ ‧₊˚ 🤩 ⋅
custom 546336413900501925148custom 527636540758061876815custom 546312783849432874715
Posted without readable text
custom 524473043082493057751custom 524706471548553174429custom 524685561500272921821
Posted without readable text
custom 543636821226032178833custom 547239416601093447414custom 543847995319048436610
Posted without readable text
custom 542462990343160472653custom 541120744343683954924custom 541355308828594340912
Posted without readable text
custom 526482256700850582056custom 521763750224385630922custom 54250063830848869844
Posted without readable text
custom 521798216477942608456custom 544950673626211568921custom 521767914624675786719
Posted without readable text
custom 525357418509921939135custom 543636821226032178816custom 524474711677287258115
Showing the 12 most recent of 13 posts we hold for @silencesubs. 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 — 415,250 of 1,549,704entries 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.
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.
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.
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.
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.
“silence with subtitles 空” (@silencesubs), 702 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/silencesubs.
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.