Telegram RegisterThe public register of Telegram
Telegram profile photo for Anime1.me 更新通知

Channel

Anime1.me 更新通知

@anime1notify

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

10,505subscribers

+84 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001354974109
TypeChannel
Username@anime1notify
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live3 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/anime1notify

Growth

10,41810,50510,461.56 August 2026 — 10,421 subscribers6 August 2026 — 10,421 subscribers7 August 2026 — 10,420 subscribers8 August 2026 — 10,421 subscribers9 August 2026 — 10,419 subscribers10 August 2026 — 10,418 subscribers11 August 2026 — 10,422 subscribers13 August 2026 — 10,421 subscribers14 August 2026 — 10,428 subscribers15 August 2026 — 10,434 subscribers17 August 2026 — 10,441 subscribers18 August 2026 — 10,443 subscribers19 August 2026 — 10,445 subscribers20 August 2026 — 10,454 subscribers21 August 2026 — 10,464 subscribers23 August 2026 — 10,475 subscribers24 August 2026 — 10,481 subscribers25 August 2026 — 10,487 subscribers27 August 2026 — 10,486 subscribers28 August 2026 — 10,490 subscribers29 August 2026 — 10,489 subscribers30 August 2026 — 10,493 subscribers31 August 2026 — 10,496 subscribers1 September 2026 — 10,500 subscribers2 September 2026 — 10,499 subscribers3 September 2026 — 10,505 subscribers6 August 20263 September 2026
26 measurements spanning 28 days, net +84. 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 10,405–10,518 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
3 Sept 2026, 16:1610,505+6
2 Sept 2026, 10:5610,499-1
1 Sept 2026, 13:4610,500+4
31 Aug 2026, 13:4510,496+3
30 Aug 2026, 14:0410,493+4
29 Aug 2026, 14:1310,489-1
28 Aug 2026, 15:1710,490+4
27 Aug 2026, 15:3610,486-1
25 Aug 2026, 20:2810,487+6
24 Aug 2026, 21:5910,481+6
23 Aug 2026, 08:4810,475+11
21 Aug 2026, 21:0610,464+10
20 Aug 2026, 15:1810,454+9
19 Aug 2026, 15:2910,445+2
18 Aug 2026, 12:4910,443+2
17 Aug 2026, 10:0610,441+7
15 Aug 2026, 20:2510,434+6
14 Aug 2026, 09:1710,428+7
13 Aug 2026, 01:4710,421-1
11 Aug 2026, 22:2210,422first reading

Engagement

263 posts held, back to 1 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 38 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.17%
avg views ÷ 10,505 subscribers
Avg views / post
544
243 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
243
of 263 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 29 August 2026
Posts held263 (1 August 202629 August 2026)
Views total132,102
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 13:29 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.

Recent posts

28 Aug 2026, 16:46 UTC480 viewsread 29 August 2026

地獄模式 ~喜歡挑戰特殊成就的玩家在廢設定的異世界成為無雙~ 第二季 [21] 已更新

28 Aug 2026, 15:08 UTC497 viewsread 29 August 2026

關於我轉生變成史萊姆這檔事 第四季 [20] 已更新

Showing the 12 most recent of 263 posts we hold for @anime1notify. 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.

Mentions

Named by 1 registered channel — 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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“Anime1.me 更新通知” (@anime1notify), 10,505 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/anime1notify.

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.