Telegram RegisterThe public register of Telegram
Telegram profile photo for Надя list_bumagi

Channel

Надя list_bumagi

@list_bumagi

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

2,275subscribers

-28 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001610797220
TypeChannel
Username@list_bumagi
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/list_bumagi

Growth

2,2752,3032,28911 August 2026 — 2,303 subscribers11 August 2026 — 2,303 subscribers15 August 2026 — 2,300 subscribers17 August 2026 — 2,298 subscribers20 August 2026 — 2,297 subscribers24 August 2026 — 2,290 subscribers27 August 2026 — 2,286 subscribers30 August 2026 — 2,284 subscribers2 September 2026 — 2,278 subscribers7 September 2026 — 2,279 subscribers11 September 2026 — 2,275 subscribers11 August 202611 September 2026
11 measurements spanning 31 days, net -28. 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 2,271–2,307 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 22:162,275-4
7 Sept 2026, 02:562,279+1
2 Sept 2026, 07:252,278-6
30 Aug 2026, 07:472,284-2
27 Aug 2026, 10:562,286-4
24 Aug 2026, 19:472,290-7
20 Aug 2026, 21:552,297-1
17 Aug 2026, 19:162,298-2
15 Aug 2026, 01:252,300-3
11 Aug 2026, 21:032,303no change
11 Aug 2026, 15:162,303first reading

Engagement

3 posts held, back to 5 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 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 3 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

165 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 41.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥6941.8%
6137.0%
🔥2112.7%
custom 533007005660691745574.24%
💘74.24%

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

Measured over the 3 most recent posts we hold, published 5 August 2026 to 6 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

6 Aug 2026, 16:33 UTC355 views53 reactionsread 11 August 2026
Photo

gaafchick – это тот самый человек, который обожает комиксы и рисует их с большим интересом! (Если вы ищете румангу, обновления которой большие и частые, то вам точно сюда!) Мне очень приятно, что у меня есть возможность вдохновлять и направлять таких людей 🥳 Рассказывать про техники и настройки, которые меняют систему работы, упрощают и делают процесс приятным❤️ (А ещё в комиксе Музыкальный вкус уж очень много кра

37🔥9custom 53300700566069174557

6 Aug 2026, 16:16 UTC356 views54 reactionsread 11 August 2026
Photo

Моя ученица gaafchick (рисует комикс Музыкальный вкус: черный список и другие) решила не мелочиться и вместо обычного отзыва про нашу работу сделала целую страницу вебтуна!!! 🖱 ЧИТАТЬ 🖱 Прочитайте, если тоже рисуете комикс, возможно это так же важно вам услышать ❤️ (ну и ради мемов конечно же)

❤‍🔥2814🔥12

5 Aug 2026, 10:09 UTC451 views58 reactionsread 11 August 2026
Photo

Итоги мини-конкурса: ✨1 Место Lylce ( Шмель и жучиха к) ✨2 место Escape Magenta room ✨3 место Хороми (чужестранка из мира звезд) и Lilskridt (Спасти вечность) —— Спасибо всем, кто делится своими историями и творит миры ❤️

❤‍🔥4110💘7

Showing the 3 most recent of 3 posts we hold for @list_bumagi. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Надя list_bumagi” (@list_bumagi), 2,275 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/list_bumagi.

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.