Telegram RegisterThe public register of Telegram
Telegram profile photo for Plants vs Brainrots | СТОК | 24/7

Channel

Plants vs Brainrots | СТОК | 24/7

@pvsbstock1

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

278subscribers

-11 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-1002850726133
TypeChannel
Username@pvsbstock1
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/pvsbstock1

Growth

278289283.57 August 2026 — 289 subscribers8 August 2026 — 289 subscribers15 August 2026 — 288 subscribers22 August 2026 — 284 subscribers29 August 2026 — 278 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net -11. 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 276–291 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 08:13278-6
22 Aug 2026, 16:34284-4
15 Aug 2026, 04:34288-1
8 Aug 2026, 08:18289no change
7 Aug 2026, 17:32289first reading

Engagement

20 posts held, back to 21 October 2025the 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 22 October 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

56 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52764772871836871942035.7%
💩2035.7%
custom 5242344653801415939610.7%
47.14%
😁35.36%
🔥11.79%
😢11.79%
🤮11.79%

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 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 8 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 56 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 21 October 2025 to 22 October 2025, 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

22 Oct 2025, 08:44 UTC819 views46 reactionsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:44:37 👥 Чат | 📌 Предметы | ☁️ Погода

💩20custom 527647728718368719416custom 52423446538014159396🔥1🤮1😁1😢1

22 Oct 2025, 08:41 UTC735 views4 reactionsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:56 👥 Чат | 📌 Предметы | ☁️ Погода

custom 52764772871836871944

22 Oct 2025, 08:41 UTC561 views1 reactionsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:50 👥 Чат | 📌 Предметы | ☁️ Погода

😁1

22 Oct 2025, 08:41 UTC491 views1 reactionsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:44 👥 Чат | 📌 Предметы | ☁️ Погода

1

22 Oct 2025, 08:41 UTC287 views1 reactionsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:38 👥 Чат | 📌 Предметы | ☁️ Погода

1

22 Oct 2025, 08:41 UTC256 views1 reactionsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:32 👥 Чат | 📌 Предметы | ☁️ Погода

1

22 Oct 2025, 08:41 UTC226 views1 reactionsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:25 👥 Чат | 📌 Предметы | ☁️ Погода

1

22 Oct 2025, 08:41 UTC206 viewsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:19 👥 Чат | 📌 Предметы | ☁️ Погода

22 Oct 2025, 08:41 UTC200 viewsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:13 👥 Чат | 📌 Предметы | ☁️ Погода

22 Oct 2025, 08:41 UTC198 viewsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:07 👥 Чат | 📌 Предметы | ☁️ Погода

22 Oct 2025, 08:41 UTC191 viewsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:41:00 👥 Чат | 📌 Предметы | ☁️ Погода

22 Oct 2025, 08:40 UTC207 viewsread 8 August 2026
Photo

🌱 РЕДКИЙ СТОК 🥥 Cocotank: x1 ⏱️ Время (МСК): 11:40:54 👥 Чат | 📌 Предметы | ☁️ Погода

Showing the 12 most recent of 20 posts we hold for @pvsbstock1. 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 — 122,390 of 1,629,452 entries 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.

Mentions

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

“Plants vs Brainrots | СТОК | 24/7” (@pvsbstock1), 278 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/pvsbstock1.

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.