2 measurements taken within a single day. 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 223–225 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
19 Sept 2026, 07:22
224
no change
19 Sept 2026, 06:47
224
first reading
Engagement
16 posts held, back to 27 June 2026 — 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.
ERR · 30 days
192.4%
avg views ÷ 224 subscribers
Avg views / post
431
13 posts measured
Reaction rate
11.0%
reactions ÷ views · ER floor
Posts in window
14
of 16 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
Window
Rolling 30 days · latest post in window 14 September 2026
Posts held
16 (27 June 2026 – 14 September 2026)
Views total
5,602
Reactions total
616
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
19 Sept 2026, 07:22 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
163
Videos
169
Links
7
Lifetime counters from Telegram’s own channel header, read 19 September 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.
Video runtime
27s
Average length
9s
Measured directly from 3 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.
Reaction mix
807 reactions across 16 posts, in 18 distinct kinds. The most used accounts for 12.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5303112183272469426
99
12.3%
custom 5424748654982364207
96
11.9%
custom 5269772791695051889
86
10.7%
custom 5219715304342441160
76
9.42%
custom 5411332598783846367
66
8.18%
custom 5413861471232764496
61
7.56%
custom 5413609249278304558
55
6.82%
custom 5386771854071447361
54
6.69%
custom 5460822690891848062
46
5.70%
custom 5197171403257827942
39
4.83%
custom 5373249939813996312
39
4.83%
custom 5212977295223979047
33
4.09%
custom 5411560678727132018
26
3.22%
custom 5413778745867674805
12
1.49%
custom 5373125278388232100
6
0.743%
custom 5395700339460569953
5
0.62%
custom 5417936355814582698
5
0.62%
custom 5436052377545244383
3
0.372%
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 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 16 of the 16 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 807 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 27 June 2026 to 14 September 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.
🔶🔶🔶🔶🔶🔶🔶🔶🔤
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
От вас требуется : поставить реакцию, сделать репость в ваш тгк без цитирования и быть подписанным на мой канал.
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
1 - 2 место подарок за ⚡️⭐️зв.
3 до 7 места подарок за ⚡️⚡️зв.
8 до 12 места подарок за⚡️⚡️зв.
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
Скрины доказательства вашей подписки, реакцией и репоста. — скидываем мне в анон, так же снизу напишите телеграмм канал в который вы репостили. @Fallen_draiven_bot
…
🔤🔤🔤🔤🔤🔤
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
Хотел бы сделать примечания насчет сетки, если вы вдруг меняете своего персонажа на другого кто не из вселенной спн - я буду вынужден вас к сожалению удалить, пока вы не вернете этого персонажа, как я и говорил сетка создана именно по спн и других быть и не должно, правила разглашаются на всех и никто не будет «любимчиком» которого я бы оставил потому что мне нравится их оформа.
The shares total 132%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Showing the 12 most recent of 16 posts we hold for @fallend_devil. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
The shares total 132%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 16 most recent posts we hold, published 27 June 2026 to 14 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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 19 September 2026 — this
entry's latest reading, not the date you are reading this.
“Я — Падший.” (@fallend_devil), 224 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/fallend_devil.
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.
