Photo, posted without a caption
🕊30

Channel
@frogyzxvbjgd
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
30subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002578012018 |
|---|---|
| Type | Channel |
| Username | @frogyzxvbjgd |
| Created | Between 1 March 2025 and 20 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 11 September 2026 |
| On Telegram | t.me/frogyzxvbjgd |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 00:03 | 30 | -1 |
| 11 Aug 2026, 03:32 | 31 | no change |
| 7 Aug 2026, 17:41 | 31 | first reading |
20 posts held, back to 20 July 2025 — 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 March 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
558 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 24.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5337193277047194783 | 137 | 24.6% | |
| custom 5334780012232980980 | 102 | 18.3% | |
| custom 5280691758202630062 | 77 | 13.8% | |
| custom 6023647905577963776 | 43 | 7.71% | |
| custom 5397672786011371987 | 41 | 7.35% | |
| custom 5350645836172785157 | 32 | 5.73% | |
| 🕊 | 30 | 5.38% | |
| custom 5276454472317425724 | 25 | 4.48% | |
| custom 5256262465259323793 | 21 | 3.76% | |
| custom 6010251378595729722 | 21 | 3.76% | |
| custom 5350543315303430926 | 18 | 3.23% | |
| custom 5418295904706772802 | 11 | 1.97% |
Custom emoji. 11 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 are Telegram’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 20 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 558 reactions 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 20 July 2025 to 8 March 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 @frogyzxvbjgd. 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 20 July 2025 to 8 March 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.
Photo, posted without a caption
🕊30
меня отчисляют из школы
custom 527645447231742572425
привет, мне 67 лет. стоит ли уходить от семьи в киберспорт по клеш рояль?
custom 528069175820263006217custom 539767278601137198710custom 60236479055779637767
Sticker, posted without a caption
custom 602364790557796377617
Video, posted without a caption
custom 528069175820263006211custom 53976727860113719876custom 60236479055779637765
Photo, posted without a caption
custom 528069175820263006215custom 53976727860113719875custom 60236479055779637765
долбаебство
custom 528069175820263006215custom 53976727860113719875
Sticker, posted without a caption
custom 528069175820263006213custom 60236479055779637763
Photo, posted without a caption
custom 539767278601137198715custom 52806917582026300626custom 60236479055779637766
ку
custom 601025137859572972216custom 53371932770471947835custom 53347800122329809804
Posted without readable text
custom 533478001223298098023custom 533719327704719478311custom 60102513785957297225
незнаю 🫣
custom 533719327704719478320custom 533478001223298098015
Showing the 12 most recent of 20 posts we hold for @frogyzxvbjgd. 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.
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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“‘nekoshka'” (@frogyzxvbjgd), 30 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/frogyzxvbjgd.
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.