4 measurements spanning 9 days, net +49. 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 75–138 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
17 Aug 2026, 11:34
131
+44
9 Aug 2026, 15:47
87
no change
9 Aug 2026, 07:51
87
+5
8 Aug 2026, 18:45
82
first reading
Engagement
16 posts held, back to 26 July 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
102.6%
avg views ÷ 131 subscribers
Avg views / post
134
15 posts measured
Reaction rate
2.57%
reactions ÷ views · ER floor
Posts in window
16
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. It is computed over the 6 of 15 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 30 July 2026
Posts held
16 (26 July 2026 – 30 July 2026)
Views total
2,017
Reactions total
26
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
9 Aug 2026, 15: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.
Reaction mix
26 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 76.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
20
76.9%
👍
4
15.4%
🔥
2
7.69%
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 6 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 26reactions 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 26 July 2026 to 30 July 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.
halo bosq!,Kalian punya informasi ripper?terus bingung mau sebarin nya kemana?tenang bosq! Gua sudah sediakan channel & bot buat laporan ripper!
#botnya : @rzxasistenv2_bot
#channel info ripper : @rezzxinfo
#Cara Buat Laporan ripper di bot :
1.start dulu di bot @rzxasistenv2_bot
2.setelah respon klick pada button "Buat laporan" atau bisa juga ketik /report
3.Jika bot respon dan menyuruh untuk mengirimkan gambar seba…
#SCRIPT CREATE REPORT RIPPER BY REZZX
Halo bosq!sesuai janji gua Ya gua bakal send script create report ripper!
Fungsinya? = Cocok untuk owner yang punya channel informasi ripper jadi lu ga perlu manual BLA bla tinggal pake script ini selesai beres!
[ # ] Link ( Jika Tidak Bisa Download File diatas ) : https://www.mediafire.com/file/bhi36j064vd0vel/Script+Create+Report+ripper+info+By+RezzX.zip/file
[ # ] Ukuran Scrip…
🚨 INFORMASI RIPPER BARU 🚨
📖 Deskripsi Kejadian:
NEW HAMA RIPER TLOL
KRONOLOGI
GUA KAN BUY SC UBOT DIA NAH GUA MAU MINTA ADD ADMIN SI HAMA INI MALAH DI READ DOANG DAN YAP DI BAN DI GB NYA
SEBARIN CUY HAMA NIH
usn @Dimazgwbg
tg://openmesseage?user_id=1940337435
👤 INFORMASI PELAPOR
├ Nama Pelapor : àlzy #immortalBoys #Lrzo
├ Username : @vvalzyy
├ ID Pelapor : 1370318280
└ Waktu Report : 27-07-2026 | 20:48:56 W
Showing the 12 most recent of 16 posts we hold for @rezzxinfo. 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
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
Names
Channels on the register whose handles appear in this channel's posts.
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 17 August 2026 — this
entry's latest reading, not the date you are reading this.
“#igneel - Herbivorous” (@rezzxinfo), 131 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/rezzxinfo.
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.
