Channel
@silencedtos
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
19subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002886461039 |
|---|---|
| Type | Channel |
| Username | @silencedtos |
| Description | Read TOS carefully before Dealing! |
| Created | 12 June 2025 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/silencedtos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 17:01 | 19 | no change |
| 9 Aug 2026, 12:32 | 19 | first reading |
8 posts held, back to 12 June 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 21 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Crypto Exchange TOS 🤥 Fee Policy: Fees start at 0.4% and may vary slightly. Any pair that includes Monero (XMR) has a fee of 1.7%. Digital Asset Risks: Crypto carries volatility and possible transaction delays, failures, or smart-contract problems. By using my Exchange service, you agree to these risks. Prohibited Use: Illegal or sanctioned actions are not allowed. Features and services can change or be discontinu…
Middleman TOS 🤥 • I will only hold and facilitate transactions involving cryptocurrencies. • My service fee is non-refundable. Upon receiving any funds, i will deduct my service fee, regardless of any changes in the deal. • I am not responsible for any changes in the value of cryptocurrencies or for any gas/sending fees that are associated with transactions. • I will not facilitate any illegal transactions. This …
PROXY TOS 🤥 • If you sell the username, I must be informed immediately, so I can take it off my list. • I will not proxy usernames that are obtained illegitimately (scammed/stolen). • I remain the right to refuse dealing with anybody without having to disclose the reason. • I will not proxy banned/disabled accounts. You can come back to me if & once it is unbanned. • I will not proxy overpriced usernames, I only…
Selling TOS 🤥 • Once the Handle informations are released i‘m no longer responsible for anything. • Once the Payment has confirmed all sales are final. • Trusted Middleman’s are always accepted at the buyer’s expense. Info: These terms apply whether we’re dealing through a Middleman or you’re going first! i cannot and will not be held responsible for ANYTHING that happens to an account once it has left my hand…
TOS = Terms Of Service 🤥 Please read the Terms of Services carefully before dealing with me. 🤥 📤 @Silenced
.
.
Channel created
Showing the 8 most recent of 8 posts we hold for @silencedtos. 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 — 1,113,684 of 1,480,688entries 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Silenced’s TOS” (@silencedtos), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/silencedtos.
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.