Telegram RegisterThe public register of Telegram

Channel

Плотвиная бессонница

@gplotva_a

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

146subscribers

+0 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-1002339426416
TypeChannel
Username@gplotva_a
DescriptionРисую, шью и не сплю🌚
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/gplotva_a

Growth

1466 August 2026 — 146 subscribers8 August 2026 — 146 subscribers6 August 20268 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 145–147 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 20:47146no change
6 Aug 2026, 21:32146first reading

Engagement

10 posts held, back to 17 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
167.5%
avg views ÷ 146 subscribers
Avg views / post
245
10 posts measured
Reaction rate
9.12%
reactions ÷ views · ER floor
Posts in window
10
of 10 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 8 August 2026
Posts held10 (17 July 20268 August 2026)
Views total2,445
Reactions total223
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 20:47 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
321
Videos
16
Links
62

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

223 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 41.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
9341.7%
custom 52494806947190727204319.3%
💅2511.2%
❤‍🔥198.52%
😱177.62%
💋125.38%
🙏73.14%
🤬73.14%

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

Measured over the 10 most recent posts we hold, published 17 July 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, 00:44 UTC37 views21 reactionsread 8 August 2026
Forwarded from @budni_bliznyukaPhoto

МЫ ПРОШЛИ НА ЮНИКОН ОНА УЗНАЛА ПРО МИНСК

13❤‍🔥4💅4

3 Aug 2026, 13:23 UTC114 views9 reactionsread 8 August 2026

Я могу сейчас думать только о двух вещах: проскочим ли мы на Юникон, и Джорно Джованне 😐 Я в своих бесконечных экспериментах с покраской ткани ненамеренно получила прекрасный цвет для его костюма несколькими способами. Щас бы психануть и сделать другого блондина в костюмчике с ромбами😏 Ладно, игнорируем сосущее чувство страха и 20 часов экспериментов с российскими красками для синтетики Пойду трогать траву и понюха

9

1 Aug 2026, 21:17 UTC320 views41 reactionsread 8 August 2026
Photo

Пиджак я конечно не успела, но заявка на Юникон подана ✨

😱17💋12💅83custom 52494806947190727201

31 Jul 2026, 21:35 UTC116 views23 reactionsread 8 August 2026
Photo

Я все хотела показать вам какой великолепный забор получился в итоге (Но меня поглотила подача заявки на Юникон) Очень радует как зашла людям эта идея ❤ Теперь не знаю как его выкидывать, но места в квартире ограниченное количество. Кто-нибудь хочет кусок картонного забора себе? Утащила с Куно-феста всяких красивостей и приколюх, а Жан теперь полетит на Кипр (может, солнышко и море помогут ему справиться с депрессие

10custom 52494806947190727207❤‍🔥6

25 Jul 2026, 11:38 UTC355 views42 reactionsread 8 August 2026
Photo

Мчимся на сходку по Дискачу Ещё и полтора тиктока сняли с Настенькой #DiscoElysium

custom 52494806947190727202213🤬7

24 Jul 2026, 17:30 UTC268 views32 reactionsread 8 August 2026
Photo

Я пооочти закончила с экспериментами, скоро можно будет...ну, просто шить 🔪🤍 Натыкайте сердечков авансом, а вам потом притащу, что получается

17❤‍🔥8custom 52494806947190727207

23 Jul 2026, 16:26 UTC264 views19 reactionsread 8 August 2026
Photo

🤍 У меня сегодня и макет, и ножницы, и даже рубашка мэтчатся с новым брелоком 🤍 Очень думаю подавать ли что-нибудь на Старкон, место новое и какое-то маленькое, а у меня после эпика маловато готовности к экспериментам 🤔

💅117❤‍🔥1

21 Jul 2026, 20:58 UTC450 views15 reactionsread 8 August 2026
Photo

Судя по набору тканей мы будем шить Барби и нищенку🌟💕 Но нет🫣

12custom 52494806947190727203

20 Jul 2026, 15:45 UTC243 views14 reactionsread 8 August 2026

Придумали, что подать на Юникон в Минске, теперь надо ну очень быстро это сшить💐

🙏75💅2

17 Jul 2026, 12:03 UTC278 views7 reactionsread 8 August 2026
Photo

Буду на Гнезде ловить себе приколов по жиже❤️ Скорость событий в первой части ДжоДжо это какой-то особый прикол🌟 Как вообще у главгада может быть настолько мало экранного времени (в шоках) А это попытка разобраться в родословной (с прекрасной иллюстрацией ДЫО от моего брата)

4custom 52494806947190727203

Showing the 10 most recent of 10 posts we hold for @gplotva_a. 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 — 7,186 of 1,189,255entries 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 2 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.

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

“Плотвиная бессонница” (@gplotva_a), 146 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/gplotva_a.

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.