Telegram RegisterThe public register of Telegram

Channel

Лавка Грибогпай (Рест)

@gribog_pieeee

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

89subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002229201463
TypeChannel
Username@gribog_pieeee
DescriptionГлавный в этом канале - @gribog_piee
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/gribog_pieeee

Growth

897 August 2026 — 89 subscribers9 August 2026 — 89 subscribers7 August 20269 August 2026
2 measurements spanning 2 days. 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 88–90 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 15:1589no change
7 Aug 2026, 14:3489first reading

Engagement

19 posts held, back to 5 March 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
21.3%
avg views ÷ 89 subscribers
Avg views / post
19.0
1 post measured
Reaction rate
21.1%
reactions ÷ views · ER floor
Posts in window
1
of 19 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 18 July 2026
Posts held19 (5 March 202618 July 2026)
Views total19
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 15: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.

What this channel posts

Photos
270
Videos
1
Links
14

Lifetime counters from Telegram’s own channel header, read 9 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.

Reaction mix

156 reactions across 15 posts, in 19 distinct kinds. The most used accounts for 35.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5535.3%
custom 54001403478021605261610.3%
custom 5425138006652643262159.62%
❤‍🔥159.62%
custom 5377355855534526818138.33%
custom 580097849580271206974.49%
🔥63.85%
custom 530782000429980206753.21%
custom 537541195333634418042.56%
custom 544043059419234964631.92%
🍓31.92%
💘31.92%
🥰31.92%
custom 496072454155586934921.28%
21.28%
🌭10.641%
🎉10.641%
💔10.641%
🙏10.641%

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

Measured over the 19 most recent posts we hold, published 5 March 2026 to 18 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.

Recent posts

18 Jul 2026, 16:41 UTC19 views4 reactionsread 9 August 2026
Photo

Всем привет!! Я пересдала английский и теперь в Казахстане.

4

28 Jun 2026, 16:29 UTC41 views12 reactionsread 9 August 2026

Art fight видимо отменяется для меня , так как я иду на пересдачу по английскому 🥺

custom 54251380066526432629custom 53078200042998020671custom 54001403478021605261custom 54404305941923496461

27 Jun 2026, 03:33 UTC139 views9 reactionsread 9 August 2026

Кому интересен art fight можете подписаться на меня. Буду очень признательна 🥺🥺🥺 Я пока что только оформляю. Вскоре буду делиться оформление https://artfight.net/~gribog_piee

custom 54001403478021605265custom 53773558555345268182custom 53078200042998020671custom 58009784958027120691

21 Jun 2026, 19:18 UTC153 views13 reactionsread 9 August 2026
Photo

Пытаюсь научиться заново рисовать 🤩

custom 53773558555345268185custom 53078200042998020673custom 54404305941923496462custom 58009784958027120692custom 54251380066526432621

18 Jun 2026, 19:28 UTC62 views14 reactionsread 9 August 2026

Дам небольшой спойлер ⭐️ Скорее всего скоро открою реквесты, что бы немного поменять стиль и вернуться в русло

custom 54001403478021605265custom 53754119533363441804custom 53773558555345268183custom 49607245415558693492

18 Jun 2026, 19:26 UTC61 views11 reactionsread 9 August 2026

Я разучилась рисовать . ЕГЭ убивает людей ⭐️

custom 54001403478021605264custom 54251380066526432624custom 58009784958027120693

18 Jun 2026, 08:37 UTC57 views13 reactionsread 9 August 2026
Photo

Всем привет!! 😜 ЕГЭ наконец-то закончилось, и я смогу рисовать. Вы бы знали, как сильно я скучала по рисованию. 😈 - я понимаю, что многие про меня забыли и забросили, но вскоре я начну публиковать арты и пытаться вернуть аудиторию ( не знаю буду ли я переезжать на другой канал, но если кто-то живой , то оставьте пожалуйста комментарий. Мне будет приятно 😊) И всех поздравляю с разблокировкой роблокс 🤓

7custom 53773558555345268183custom 54001403478021605261custom 54251380066526432621custom 58009784958027120691

4 Jun 2026, 08:18 UTC68 views4 reactionsread 9 August 2026
Photo

Написала ЕГЭ по русскому. Мой самый первый экзамен

3🙏1

1 Jun 2026, 16:46 UTC70 views3 reactionsread 9 August 2026

Всех поздравляю с первым днём лета и написанными экзаменом!!

2🔥1

24 May 2026, 17:57 UTC85 viewsread 9 August 2026

Извините, если кому-то не отвечаю. Я вся в подготовке 🤓👌

Showing the 12 most recent of 19 posts we hold for @gribog_pieeee. 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 — 619,768 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.

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.

Mentions

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.

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

“Лавка Грибогпай (Рест)” (@gribog_pieeee), 89 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/gribog_pieeee.

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.