Channel
@saucebaby
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,888subscribers
+63 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001851008598 |
|---|---|
| Type | Channel |
| Username | @saucebaby |
| Created | Between 1 October 2022 and 31 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/saucebaby |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 56% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
5,120 average views per post against 1,888 subscribers — an engagement rate of 271.1%. Across the 54,164 registered channels in the same cohort — 1,000–3,162 subscribers, posting mainly in Russian — the middle half sit between 10.5% and 35.6%, with a median of 20.1%.
| Window | 30 days (13 July 2026 – 12 August 2026) |
|---|---|
| Posts measured | 8 of 8 published in the window (1 exact, 7 rounded by Telegram) |
| Views totalled | 40,954 |
| Mature posts only | 271.1% over 8 posts read at least 24h after publication |
| Subscribers | 1,888 measured 11 August 2026 |
| Cohort | b1000:rus · 54,164 channels · p10 5.33% · p25 10.5% · p50 20.1% · p75 35.6% · p90 57.1% |
| Position in cohort | 99.729th percentile · 13.5× the cohort median |
| Uncertainty | ±0.169% of the figure, from Telegram’s rounding |
| Post language | Russian · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 16:24 | 1,888 | +5 |
| 9 Aug 2026, 02:31 | 1,883 | +36 |
| 6 Aug 2026, 12:01 | 1,847 | +22 |
| 6 Aug 2026, 08:18 | 1,825 | first reading |
8 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 2 pagesof 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 6 August 2026 |
|---|---|
| Posts held | 8 (28 July 2026 – 6 August 2026) |
| Views total | 40,954 |
| Reactions total | 712 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:25 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
712 reactions across 8 posts, in 9 distinct kinds. The most used accounts for 40.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5314488434948071744 | 291 | 40.9% | |
| custom 5294027137735482273 | 202 | 28.4% | |
| custom 5334860233632139397 | 87 | 12.2% | |
| custom 5255723571417719479 | 39 | 5.48% | |
| custom 5316532805021214111 | 39 | 5.48% | |
| custom 5233290660877977038 | 25 | 3.51% | |
| custom 5422467189829543120 | 15 | 2.11% | |
| custom 5127559982073512872 | 10 | 1.40% | |
| custom 5226531980081904820 | 4 | 0.562% |
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 8 of the 8 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 712reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 28 July 2026 to 6 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.
😳нифига реакций насыпали… вот, посмотрите тогда на мою малышку Китти после операции на сердечко❤️🩹🐶 (все прошло хорошо, она восстанавливается и теперь будет жить долго и счастливо🫂)
custom 531448843494807174454custom 529402713773548227313custom 533486023363213939712custom 52265319800819048203
bratz💅😍
custom 5314488434948071744124custom 529402713773548227336custom 533486023363213939725
эта бро моя любимая пацанка
custom 5294027137735482273134custom 531448843494807174445custom 533486023363213939724custom 52265319800819048201
Video message, posted without a caption
custom 531448843494807174468custom 533486023363213939724custom 529402713773548227319
реакции куда-то делись… возобновите, пж?🩷🩷 https://t.me/boost/saucebaby 🌸
custom 523329066087797703816custom 54224671898295431207custom 52557235714177194795custom 53348602336321393972
кто шагает дружно в ряд?хала Китти наш отряд 💗
custom 525572357141771947925custom 52332906608779770389custom 54224671898295431208
я и мояшкина
custom 531653280502121411120custom 51275599820735128724custom 52557235714177194794
1️⃣2️⃣3️⃣
custom 531653280502121411119custom 51275599820735128726custom 52557235714177194795
Showing the 8 most recent of 8 posts we hold for @saucebaby. 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 — 62,911 of 1,151,006entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 5 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“💖SAUCEBABY💖” (@saucebaby), 1,888 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/saucebaby.
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.