Telegram RegisterThe public register of Telegram
Telegram profile photo for @гурман #555

Channel

@гурман #555

@sorocpyatiyscvad

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

120subscribers

+4 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1001561261934
TypeChannel
Username@sorocpyatiyscvad
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live17 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/sorocpyatiyscvad

Growth

11612011810 August 2026 — 116 subscribers10 August 2026 — 116 subscribers17 August 2026 — 120 subscribers10 August 202617 August 2026
3 measurements spanning 7 days, net +4. 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 115–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 12:45120+4
10 Aug 2026, 09:15116no change
10 Aug 2026, 09:02116first reading

Engagement

20 posts held, back to 22 July 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
68.5%
avg views ÷ 120 subscribers
Avg views / post
82.2
18 posts measured
Reaction rate
2.46%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 14 of 18 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held20 (22 July 20269 August 2026)
Views total1,480
Reactions total29
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 09:15 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

29 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 37.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1137.9%
❤‍🔥931.0%
💯724.1%
custom 530564286390260448913.45%
🔥13.45%

Custom emoji. One 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 count beside it isTelegram’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 14 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 29reactions 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 22 July 2026 to 9 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.

Recent posts

9 Aug 2026, 19:57 UTC33 views6 reactionsread 10 August 2026

Ой заебали тимур и нукари, оба наныли себе хуйни какой-то. Похуй вщ кто там че делает, сидишь от нехуй делать угараешь с пацана, еще и тгк забиваешь ебучим спамом, чтобы удовлетворить свое эго. Я за разумные переговоры, и про личную жизнь, а не такое свинское поведение #eternalgood555 #555clUbforpeace

❤‍🔥5custom 53056428639026044891

Signed @гурман 𓍼

9 Aug 2026, 16:15 UTC37 views1 reactionsread 10 August 2026

рецепт джуга 1. 808 в ритме джерка 2. воксы 3. БОЛЬШЕ ВОКСОВ 4. БОЛЬШЕ 808 5. пишем воКАЛ (НИ В КОЕМ СЛУЧАЕ НЕ СВОДИТЕ) 6. ладно , напиздел , единственное - добавьте delay чтобы ГЛУШИЛ НАХУЙ 7. рендер 8. КУЧА ЭФФЕКТОВ И АВТОМАТИЗАЦИЙ (фейзер, лав фильтр , куча затуханий, повторениц и тд) 9. ПОЗДРАВЛЯЮ ВЫ ДОСТИГЛИ ДНА СК 🎉🎉🎉

💯1

Signed @гурман 𓍼

8 Aug 2026, 04:53 UTC46 viewsread 10 August 2026

Бля я хз оформлять с графиком чет или не

Signed @гурман 𓍼

7 Aug 2026, 23:48 UTC48 views1 reactionsread 10 August 2026

СЛИЛ ТРЕК ГУРМАНА НОВЫЙ

1

Signed @гурман 𓍼

7 Aug 2026, 23:48 UTC50 views1 reactionsread 10 August 2026
Video message

Video message, posted without a caption

💯1

Signed @гурман 𓍼

7 Aug 2026, 21:29 UTC49 views0 reactionsread 10 August 2026
Forwarded from @cutwarrio

с днем рождения меня

Signed @гурман 𓍼

4 Aug 2026, 21:27 UTC96 views2 reactionsread 10 August 2026
File

ГРАФИКЛМАО ПРЕСЕТ (плагины никакие удалять не надо. Открываете папку, мейн на мейн, сенд на сенд и мастер на мастер. Все. (Пресет не от самого графика, так что один в один звучания не ждите)

❤‍🔥2

Signed @гурман 𓍼

3 Aug 2026, 17:48 UTC89 viewsread 10 August 2026
Forwarded from @clUb555ddx

завтра (04.08) в 17:00 по МСК будет стрим с оценкой треков,закидывайте в комы +3gund DDX nukari

Signed @гурман 𓍼

2 Aug 2026, 17:36 UTC100 views2 reactionsread 10 August 2026
Forwarded from @shotby11Photo

❤️

2

Signed @гурман 𓍼

2 Aug 2026, 13:25 UTC77 viewsread 10 August 2026
Forwarded from @smileDDXPhoto

DDX, @гурман - fanat (p. jjukai) гурма джука

Signed @гурман 𓍼

Showing the 12 most recent of 20 posts we hold for @sorocpyatiyscvad. 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

Citation-graph rank — 864,310 of 1,480,975entries 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

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 4 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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“@гурман #555” (@sorocpyatiyscvad), 120 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/sorocpyatiyscvad.

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.