Telegram RegisterThe public register of Telegram

Channel

Пельменный сомелье | Лорд Злыдень

@ruciwold

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

349subscribers

+1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001594735554
TypeChannel
Username@ruciwold
Created4 July 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/ruciwold

Growth

3473493486 August 2026 — 348 subscribers6 August 2026 — 348 subscribers7 August 2026 — 347 subscribers13 August 2026 — 349 subscribers6 August 202613 August 2026
4 measurements spanning 6 days, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 347–349 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:17349+2
7 Aug 2026, 02:31347-1
6 Aug 2026, 21:18348no change
6 Aug 2026, 18:03348first reading

Engagement

10 posts held, back to 23 June 2026the 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 · 30 days
78.3%
avg views ÷ 349 subscribers
Avg views / post
273
5 posts measured
Reaction rate
9.74%
reactions ÷ views · ER floor
Posts in window
5
of 10 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 July 2026
Posts held10 (23 June 202631 July 2026)
Views total1,366
Reactions total133
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 21:18 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.

Reaction mix

314 reactions across 10 posts, in 12 distinct kinds. The most used accounts for 36.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 547422281705669016811436.3%
10332.8%
🥰3310.5%
😭165.10%
🔥134.14%
custom 5971895289122920602103.18%
💘92.87%
😍61.91%
💋41.27%
😱41.27%
🎉10.318%
👍10.318%

Custom emoji. 2 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 10 of the 10 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 314reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 23 June 2026 to 31 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.

Telegram Stars

Stars received
17
across the posts below
Posts paid on
3
of 10 we hold a reading for · 30%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ruciwold. 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 10 most recent posts we hold for this entry, published 23 June 2026 to 31 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.

Recent posts

31 Jul 2026, 18:25 UTC98 views28 reactions1 Starread 6 August 2026

Когда-нибудь тут будут не только репосты и я чета буду делать сам🤣🤣🤣

13custom 547422281705669016810💘4🎉1

31 Jul 2026, 18:25 UTC92 views27 reactionsread 6 August 2026
Forwarded from @allexkriiVideo

Подумалось мне, что можно неудачные дубли не удалять, а пилить доп контент в тгк 😁 Как вам идея? Деку дал зелёный свет 😡 А завтра принесу бэки с нового фотоса!

custom 54742228170566901681211💘3custom 59718952891229206021

26 Jul 2026, 21:53 UTC154 views23 reactionsread 6 August 2026
Forwarded from @allexkriiPhoto

🤩🤩🤩🤩🤩🤩🤩 Фест прошёл так, что я не увидела ни одно выступление, конец 🙂 Но было очень весело! 🥳🥳🥳 💚 Деку ❤️ Ястреб 💛 Анастасия 💙 Официально, как на бэйдже, ЕКАТЕРИНА 💜 Шикарная Сева

custom 5474222817056690168145💋3💘1

23 Jul 2026, 07:28 UTC779 views25 reactionsread 6 August 2026
Photo

Друзья!!! Купите мэрчик, пожалуйста, или я умру голодной смертью🤣 Подробнее можно узнать тут - https://t.me/munmun_ie Есть возможность передать на акамару (Москва) в это вс/пересыл Ещё можете заглянуть на моё авито - там не только костюмы и рассмотрю торг (там почти везде включен % авито)👉👈

14custom 54742228170566901686🥰4💘1

18 Jul 2026, 04:35 UTC243 views30 reactionsread 6 August 2026
Forwarded from @daftezzerrrVideo message

Video message, posted without a caption

custom 5474222817056690168138😍6custom 59718952891229206022🥰1

15 Jul 2026, 17:58 UTC265 views39 reactions6 Starsread 6 August 2026
Photo

🌟Сегодня у Деку-Деку ДР и в честь этого на покекать…🌟 (есть еще более ранние варианты, но там совсем файлы смерти, ахаха. Были ещё разные версии, но…) Следующие коспики на Деку будут через 6 лет, чтобы укладываться в статистику.

15custom 547422281705669016811🔥9🥰2💋1custom 59718952891229206021

10 Jul 2026, 09:04 UTC260 views35 reactionsread 6 August 2026
Video

🎉Наступает время чистить галерею, поэтому попощу сюда всякого прошлогоднего…🎉 С теплотой вспоминаю этот фотос, несмотря на все сложности. И большое спасибо Наташе, которая подбила меня на Гинро и даже парик сделала, птмшт теперь считаю этого бро одним из своих самых удачных образов, хд. Бтв, можете заглянуть сюда и поставить луцк/посмотреть, какие мы красивые, хд

15custom 54742228170566901689🥰7🔥4

9 Jul 2026, 17:45 UTC252 views69 reactions10 Starsread 6 August 2026
Photo

✨Я ухожу из косплея, но обязательств перед другими у меня ещё на два года, поэтому…✨ 🌟Вкидываю небольшой спойлер к следующей съемке🌟 Возможно, кто-то помнит удаленный закос год назад, так вот… И, если кому-то интересно, что происходит все это время: с конца прошлого года случилось сильное выгорание к коспику. С начала года у меня началась успешная карьера витубера (за 6 коротких стримов 150 сабов, йоу), рисоваки-ме

custom 547422281705669016830😭16🥰14😱4custom 59718952891229206024👍1

23 Jun 2026, 18:25 UTC339 views19 reactionsread 6 August 2026

⬆️Я сделал, кстати🫦 Подпишитесь/купите, пж… там ещё приколы будут!

10custom 54742228170566901685🥰3custom 59718952891229206021

23 Jun 2026, 18:23 UTC306 views19 reactionsread 6 August 2026
Forwarded from @munmun_ieVideo

💥💥💥💥💥💥💥 💥2,7 сантиметра ярости на блестящем акриле💥 Всего 💥💥💥💥 и ты станешь обладателем Великого Взрывоубийственного Бога Динамита🫦 💥Если хотите забрать микроба - он ждёт вас в лс сообщества💥 *итоговый цвет подвески золотой. Цена указана без учета доставки

12custom 54742228170566901684🥰2custom 59718952891229206021

Showing the 10 most recent of 10 posts we hold for @ruciwold. 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

Citation-graph rank — 181,573 of 1,345,403entries 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.

Forward network

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.

Mentions

Named by 7 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.

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.

Cite this entry

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.

“Пельменный сомелье | Лорд Злыдень” (@ruciwold), 349 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ruciwold.

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.