Telegram RegisterThe public register of Telegram

Channel

𝑹𝒆✧𝐙𝐄𝐑𝐎 ꪀꫀ᭙𝘴🗞️ᵉ ρ𝓲ᥴ 🖼️

@ReZEROChannel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

243subscribers

-1 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001370985574
TypeChannel
Username@ReZEROChannel
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/ReZEROChannel

Growth

243244243.59 Aug 2026, 19:46 — 244 subscribers10 Aug 2026, 19:47 — 243 subscribers9 Aug 2026, 19:4610 Aug 2026, 19:47
2 measurements spanning 1 day, net -1. 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 243–244 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 19:47243-1
9 Aug 2026, 19:46244first reading

Engagement

17 posts held, back to 30 June 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
94.6%
avg views ÷ 243 subscribers
Avg views / post
230
11 posts measured
Reaction rate
4.75%
reactions ÷ views · ER floor
Posts in window
11
of 17 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 5 August 2026
Posts held17 (30 June 20265 August 2026)
Views total2,528
Reactions total120
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 19:46 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

Video runtime
2m 29s
Average length
1m 15s

Measured directly from 2 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

177 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 48.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8548.0%
🔥5229.4%
🎉2413.6%
custom 633440231000060929284.52%
custom 633704602987502138942.26%
custom 633446688053893737421.13%
custom 633447562938731958210.565%
custom 633453059637877368910.565%

Custom emoji. 5 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 areTelegram’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 17 of the 17 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 177reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 30 June 2026 to 5 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

5 Aug 2026, 15:00 UTC131 views9 reactionsread 9 August 2026
Video

Re:ZERO Stagione 4 - Episodio 12 “Parlare di quello che ci Aspetta” 🔴Teaser Trailer - Disponibile tra 7 Giorni Mercoledì 12 Agosto alle 16:00 su Crunchyroll!💥

6🔥2🎉1

5 Aug 2026, 15:00 UTC120 views10 reactionsread 9 August 2026
Photo

🔴IL PROSSIMO EPISODIO…🔴 💥S4 EP12💥 “Parlare di quello che ci Aspetta” Finalmente ci siamo.

🔥72🎉1

4 Aug 2026, 06:00 UTC230 views10 reactionsread 9 August 2026
Video

🔴RE:ZERO S4 - PARTE 2 TEASER PV🔴 Manca UNA SETTIMANA alla parte più INCREDIBILE di Re:ZERO‼️ MERCOLEDÌ 12 AGOSTO 2026💥

8🎉1🔥1

2 Aug 2026, 10:05 UTC163 views12 reactionsread 9 August 2026
Photo

🔴Mancano solo 10 GIORNI al ritorno dell’incredibile QUARTA STAGIONE di RE:ZERO con il Climax del suo arco MIGLIORE‼️ SIETE PRONTI?💥

🔥92🎉1

31 Jul 2026, 21:17 UTC342 views19 reactionsread 9 August 2026
Photo

🔴Finalmente la rivelazione‼️ L’EPISODIO 16 della QUARTA STAGIONE di Re:ZERO, che uscirà il 9 settembre 2026, adatterà il Capitolo più apprezzato della Novel dall’intero fandom di Re:ZERO e sarà l’EPISODIO NOMINATO dal TITOLO “NATSUKI SUBARU” e sarà un episodio MOLTO ESTESO (probabilmente attorno ai 30 minuti).

8🔥5🎉2custom 63344668805389373742custom 63344023100006092921custom 63345305963787736891

25 Jul 2026, 15:30 UTC233 views17 reactionsread 9 August 2026
Photo

Photo, posted without a caption

7🔥5custom 63370460298750213893custom 63344023100006092921custom 63344756293873195821

25 Jul 2026, 15:30 UTC245 views7 reactionsread 9 August 2026

🔴Nella Storia Prequel Shaula EX “SCORPION TALE” sono state rivelate alcune informazioni molto importanti riguardo alcuni aspetti della lore di Re:Zero, per altri aspetti ha creato addirittura nuove domande.🔥 Nella postfazione, l’autore Tappei Nagatsuki conferma che questa SS è solo un assaggio delle storie che riguardano il Mondo di 400 anni fa, e che alla fine verrano svelate.💥

5🎉1🔥1

25 Jul 2026, 10:35 UTC392 views9 reactionsread 9 August 2026

🔴È UFFICIALE🔴 💥LA QUARTA STAGIONE PARTE 2 DI RE:ZERO AVRÀ PIÙ EPISODI LUNGHI/ESTESI DELLA PRIMA PARTE‼️

5🎉3🔥1

24 Jul 2026, 14:00 UTC242 views9 reactionsread 9 August 2026
Photo

🟣L’INNOCENZA DI SATELLA🟣 Per il mondo di Lugunica, il suo nome era una maledizione. Nei testi di storia e nelle leggende sussurrate attorno ai falò, lei era la STREGA DELL’INVIDIA: l’essere immondo che 400 anni prima aveva divorato metà del mondo, sterminato le altre Streghe del Peccato e portato la rovina nel Mondo. Ma la verità, sepolta da quattro secoli, era assai diversa. Prima della cosiddetta Grande Calamità,

custom 63344023100006092925🔥21custom 63370460298750213891

24 Jul 2026, 08:04 UTC170 views6 reactionsread 9 August 2026

🔴Sapevate che Re:ZERO è suddiviso in 4 grandi parti (saghe teoriche)?💥 Ogni arco narrativo ha un suo tema narrativo ufficiale‼️📖 —RE:ZERO— 『 DRAGON KINGDOM SAGA 』 Arco 1 (Stagione 1 Parte 1) Tema: Inizio Arco 2 (Stagione 1 Parte 1) Tema: Fiducia Arco 3 (Stagione 1 Parte 2) Tema: Consapevolezza di sé Arco 4 (Stagione 2) Tema: Fiducia in sé stessi 『 STARS’ JOURNEY SAGA 』 Arco 5 (Stagione 3) Tema: Ostacoli A

4🎉1🔥1

19 Jul 2026, 16:30 UTC260 views12 reactionsread 9 August 2026
Photo

🔴Mancano 3 settimane al ritorno di Re:ZERO con la PARTE 2 della QUARTA STAGIONE‼️ La Parte 2 adatterà il Climax dell’Arco 6 “La Sala dei Ricordi”🕊️ Questo Cour viene considerato dai lettori della Novel la parte MIGLIORE dell’intera Storia di Re:ZERO finora.💥

7🔥3🎉1custom 63344023100006092921

13 Jul 2026, 09:38 UTC329 views8 reactionsread 9 August 2026
Photo

Photo, posted without a caption

5🔥2🎉1

Showing the 12 most recent of 17 posts we hold for @ReZEROChannel. 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 — 284,643 of 1,336,469entries 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.

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

“𝑹𝒆✧𝐙𝐄𝐑𝐎 ꪀꫀ᭙𝘴🗞️ᵉ ρ𝓲ᥴ 🖼️” (@ReZEROChannel), 243 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/ReZEROChannel.

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.