Осторожно, возможно, оголённая натура. WIP. #репост_по_желанию
custom 531207930618737084012custom 49567226885979522495custom 49588934853284351735custom 52965377651633321433

Channel
@MEATCELLAR
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
71subscribers
+1 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003921958077 |
|---|---|
| Type | Channel |
| Username | @MEATCELLAR |
| Created | Between 1 April 2026 and 29 May 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 | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/MEATCELLAR |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:13 | 71 | +1 |
| 12 Aug 2026, 03:00 | 70 | no change |
| 12 Aug 2026, 02:46 | 70 | first reading |
20 posts held, back to 29 May 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 27 July 2026 |
|---|---|
| Posts held | 20 (29 May 2026 – 27 July 2026) |
| Views total | 388 |
| Reactions total | 93 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:00 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.
299 reactions across 18 posts, in 8 distinct kinds. The most used accounts for 23.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5312079306187370840 | 71 | 23.7% | |
| custom 5296537765163332143 | 66 | 22.1% | |
| custom 4958893485328435173 | 42 | 14.0% | |
| custom 5298597962190977627 | 39 | 13.0% | |
| custom 4956722688597952249 | 33 | 11.0% | |
| custom 4956458659778406048 | 25 | 8.36% | |
| custom 5445217361013540965 | 20 | 6.69% | |
| custom 5442692061977415086 | 3 | 1.00% |
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 18 of the 20 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 299reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 29 May 2026 to 27 July 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MEATCELLAR. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 29 May 2026 to 27 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Осторожно, возможно, оголённая натура. WIP. #репост_по_желанию
custom 531207930618737084012custom 49567226885979522495custom 49588934853284351735custom 52965377651633321433
Коммишн. #репост_по_желанию
custom 529653776516333214312custom 49564586597784060488custom 54452173610135409656
Ребята, я не могу отвечать на основе потому что у меня какая хня с тг аккаунтом !!! Я постараюсь наладить всё #важно (не репост)
custom 49588934853284351735custom 54452173610135409655custom 53120793061873708404
#репост_по_желанию ; #практика
custom 529859796219097762710custom 49567226885979522498custom 53120793061873708407custom 52965377651633321433
Привет, ребята. У меня сейчас довольно сильные временные проблемы, поэтому я не могу быть активна и так же временно не могу отвечать вам лично. У меня есть готовые работы и я выложу их чуть позже, по возможности #важно
custom 529859796219097762710custom 53120793061873708407custom 49564586597784060484
Sticker, posted without a caption
custom 49564586597784060482
🌟: как всегда красота
custom 49567226885979522493
Sticker, posted without a caption
custom 49588934853284351732
🗝🗝🗝 🗝🗝🗝🥹🥹🥹🥹🥹 🌈: Продлеваю рест. По личным причинам не могу быть активна. #практика ; #репост_по_желанию
custom 52965377651633321438custom 49588934853284351734custom 53120793061873708404custom 49564586597784060481custom 49567226885979522491custom 52985979621909776271custom 54452173610135409651
🗝🗝🗝 🗝🗝🗝🥹🥹🥹🥹🥹 #практика ; #репост_по_желанию
custom 529653776516333214313custom 52985979621909776278custom 53120793061873708407custom 49564586597784060485
🖤💤 🤩🤩🤩🅰️амёк на слфх 🖤 🗝🗝🗝 🗝🗝🗝🥹🥹🥹🥹🥹 #практика ; #репост_по_желанию
custom 529653776516333214311custom 49588934853284351738custom 54452173610135409657custom 49567226885979522493custom 49564586597784060482
🗝🗝🗝 🗝🗝🗝🥹🥹🥹🥹🥹 #практика ; #репост_по_желанию
custom 529653776516333214313custom 49588934853284351737custom 53120793061873708405custom 49567226885979522493custom 52985979621909776272custom 49564586597784060481
Showing the 12 most recent of 20 posts we hold for @MEATCELLAR. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 1,131,278 of 1,169,250entries 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.
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 2 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
“РЕСТ | MEAT CELLAR” (@MEATCELLAR), 71 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/MEATCELLAR.
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.