Channel
@rottensalt
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
96subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003142364897 |
|---|---|
| Type | Channel |
| Username | @rottensalt |
| Description | ЛИЧКО @pervmind |
| Created | Between 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/rottensalt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 08:01 | 96 | no change |
| 11 Aug 2026, 07:47 | 96 | first reading |
15 posts held, back to 27 June 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.
| Window | Rolling 30 days · latest post in window 2 August 2026 |
|---|---|
| Posts held | 15 (27 June 2026 – 2 August 2026) |
| Views total | 1,191 |
| Reactions total | 218 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 08:01 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.
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.
373 reactions across 15 posts, in 20 distinct kinds. The most used accounts for 29.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍓 | 108 | 29.0% | |
| custom 5451617098507790318 | 47 | 12.6% | |
| custom 5285069648432227199 | 31 | 8.31% | |
| custom 5314447830327274596 | 26 | 6.97% | |
| 🍌 | 25 | 6.70% | |
| 🌭 | 24 | 6.43% | |
| custom 5307904726824693446 | 22 | 5.90% | |
| custom 5215190375907499040 | 21 | 5.63% | |
| custom 5285402104670739975 | 18 | 4.83% | |
| custom 5454012418948634907 | 18 | 4.83% | |
| 😭 | 8 | 2.14% | |
| custom 5215451509919094633 | 7 | 1.88% | |
| custom 5285070704994181350 | 4 | 1.07% | |
| custom 5409240936825790353 | 4 | 1.07% | |
| custom 5453972127860427619 | 3 | 0.804% | |
| custom 5456301945755047252 | 3 | 0.804% | |
| custom 5201957744877248121 | 1 | 0.268% | |
| custom 5249131161690605400 | 1 | 0.268% | |
| custom 5447495072364922949 | 1 | 0.268% | |
| 🎉 | 1 | 0.268% |
Custom emoji. 15 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 15 of the 15 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 373reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 27 June 2026 to 2 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.
Just doing some shi
custom 52850696484322271998custom 54540124189486349076custom 54563019457550472523custom 54539721278604276192custom 52019577448772481211custom 52491311616906054001custom 54474950723649229491
Ой нет опять оно
custom 52854021046707399758custom 52154515099190946336custom 54092409368257903534custom 52850696484322271992custom 54540124189486349071
Ркбята кого рисовать подскажите у меня нет идей
custom 545401241894863490711custom 52850696484322271996custom 52850707049941813504custom 52854021046707399753🎉1custom 52154515099190946331custom 54539721278604276191
I don't like it скетч был лучше
custom 528506964843222719915custom 52854021046707399757🍌3🍓2🌭1
Лабно вот лучше psina ❤️
🍓16custom 54516170985077903187🌭6🍌3
Неизлечимо
🍓10custom 54516170985077903186🌭5🍌2
Ларпить не забываем ребята
custom 545161709850779031816🌭8🍓8🍌4custom 53144478303272745961
Да бля почему без надписи
custom 53144478303272745968custom 54516170985077903181
Photo, posted without a caption
custom 531444783032727459611🍓5custom 54516170985077903183
Кстати очень даже хуево
custom 545161709850779031814🍓8custom 53144478303272745966🌭1🍌1
Photo, posted without a caption
🍓22🍌8custom 53079047268246934467custom 52151903759074990403
😔😔
🍓12custom 52151903759074990407custom 53079047268246934465😭1
Showing the 12 most recent of 15 posts we hold for @rottensalt. 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,107,696 of 1,189,255entries 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.
“Deul” (@rottensalt), 96 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/rottensalt.
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.