Telegram RegisterThe public register of Telegram
Telegram profile photo for • || Grenka_cos | Licka_Lee🍁

Channel

• || Grenka_cos | Licka_Lee🍁

@grenka_cos_art

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

151subscribers

-3 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-1001747563839
TypeChannel
Username@grenka_cos_art
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/grenka_cos_art

Growth

151154152.56 August 2026 — 154 subscribers8 August 2026 — 154 subscribers14 August 2026 — 151 subscribers6 August 202614 August 2026
3 measurements spanning 7 days, net -3. 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 151–154 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 02:38151-3
8 Aug 2026, 19:00154no change
6 Aug 2026, 21:03154first reading

Engagement

20 posts held, back to 3 August 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
35.9%
avg views ÷ 151 subscribers
Avg views / post
54.1
20 posts measured
Reaction rate
11.8%
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 17 of 20 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 8 August 2026
Posts held20 (3 August 20268 August 2026)
Views total1,083
Reactions total110
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 19: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.

Reaction mix

110 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 49.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53575379701926615265449.1%
custom 54539308746995429061210.9%
custom 53935023555871078441110.0%
custom 545614031754573976687.27%
custom 546287929732681846587.27%
custom 538667145921089896665.45%
custom 542934721633664245565.45%
custom 533010192526426242643.64%
custom 604208361031441205510.909%

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 17 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 110reactions 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 3 August 2026 to 8 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

8 Aug 2026, 17:01 UTC20 views4 reactionsread 8 August 2026

На хвост у меня не хватило сил... сделаю завтра😑 #щп

custom 53575379701926615264

8 Aug 2026, 12:53 UTC32 views1 reactionsread 8 August 2026

Теперь можно почиллить и приступить к хвосту. Ауеееее. #щп

custom 53575379701926615261

8 Aug 2026, 12:50 UTC33 views7 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 53935023555871078443custom 54293472163366424552custom 54561403175457397662

8 Aug 2026, 10:15 UTC44 views3 reactionsread 8 August 2026

Лишь бы не сбить никого этими рогами на фесте😂

custom 53575379701926615263

8 Aug 2026, 10:13 UTC45 views6 reactionsread 8 August 2026

Я их померила и на мне они выглядят ужасно...... Может не надо было такие огромные делать😭😭😭 Да и переделывать.. краски не хватит😭😭😭 А может просто сначала парик уложить и они как-то будут более менее гармонично смотреться. Да и плащ у меня длинный + хвост будет. Думаю баланс в образе будет нормальным😑😑😑 #щп

custom 53575379701926615266

8 Aug 2026, 08:41 UTC46 views2 reactionsread 8 August 2026
Photo

Вроде норм отшлефовала

custom 53575379701926615262

8 Aug 2026, 06:54 UTC44 views1 reactionsread 8 August 2026

Хочу немного оригинальности рогам добавить. Типо не супер канон, но хочу оставить где-то "трещины", или даже место отлома рога, потому что могу, а не потому что руки из жопы 😂. И вообще. Я ничего не делала из пеноплекса! Мне простительно для первого раза!!! #щп

custom 53575379701926615261

8 Aug 2026, 06:51 UTC43 views4 reactionsread 8 August 2026
Photo

Пеноплекс оказался не очень хорошим по качеству, хотя продавец при мне резал кусок и шло гладко всё. Может у меня руки из жопы, но поздно сдаваться😂😂😂

custom 53575379701926615264

7 Aug 2026, 15:48 UTC53 views1 reactionsread 8 August 2026

Я так хочу поучаствовать, но очень боюсь, волнуюсь, переживаю...😭😭😭

custom 53575379701926615261

Showing the 12 most recent of 20 posts we hold for @grenka_cos_art. 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 — 341,264 of 1,481,217entries 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

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

“• || Grenka_cos | Licka_Lee🍁” (@grenka_cos_art), 151 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/grenka_cos_art.

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.