Telegram RegisterThe public register of Telegram
Telegram profile photo for EACG消息整合频道

Channel

EACG消息整合频道

@EACGRP

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

16subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1001410932948
TypeChannel
Username@EACGRP
DescriptionACG相关转推频道 本频道基于IFTTT运行,EnjoyACG不对内容进行审核。 订阅列表请参见 https://t.me/EnjoyACG_Board/17
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/EACGRP

Growth

1610 Aug 2026, 20:45 — 16 subscribers11 Aug 2026, 21:01 — 16 subscribers10 Aug 2026, 20:4511 Aug 2026, 21:01
2 measurements spanning 1 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 15–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 21:0116no change
10 Aug 2026, 20:4516first reading

Engagement

20 posts held, back to 23 May 2023the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 23 May 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
204,000

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

23 May 2023, 14:57 UTC65 viewsread 11 August 2026

【5月23日に公開した記事ランキング第1位】『僕の心のヤバイやつ(僕ヤバ)』第9話先行場面カット&あらすじ#僕ヤバhttps://t.co/aiVB1oYH93 — アニメイトタイムズ公式 (@animatetimes) May 23, 2023 本消息来自@animatetimes 本消息发送于:May 23, 2023 at 10:30PM

23 May 2023, 14:57 UTC58 viewsread 11 August 2026

【5月23日に公開した記事ランキング第2位】TVアニメ『ぽんのみち』制作決定|春場ねぎがキャラ原案を担当#ぽんのみち#前田佳織里#佐伯伊織#若山詩音#近藤唯https://t.co/weH1WWMOro https://t.co/DiT8vUcO8f — アニメイトタイムズ公式 (@animatetimes) May 23, 2023 本消息来自@animatetimes 本消息发送于:May 23, 2023 at 10:25PM

23 May 2023, 14:57 UTC39 viewsread 11 August 2026

【5月23日に公開した記事ランキング第3位】江口拓也の誕生日に送られた声優仲間からのツイートまとめ【注目トレンド】#江口拓也#小野賢章https://t.co/E6kiN4yR2E https://t.co/NjtOOptboP — アニメイトタイムズ公式 (@animatetimes) May 23, 2023 本消息来自@animatetimes 本消息发送于:May 23, 2023 at 10:20PM

23 May 2023, 14:57 UTC32 viewsread 11 August 2026

【5月23日に公開した記事ランキング第4位】『灼眼のシャナ』11年ぶりとなる最新刊が発売決定【注目トレンド】#灼眼のシャナ#シャナ#シャナ最新刊https://t.co/9xHneK1VU7 https://t.co/oImsYSvXez — アニメイトタイムズ公式 (@animatetimes) May 23, 2023 本消息来自@animatetimes 本消息发送于:May 23, 2023 at 10:15PM

23 May 2023, 14:57 UTC22 viewsread 11 August 2026

【5月23日に公開した記事ランキング第5位】『大奥』予告映像&キービジュアル公開|6/29より配信#大奥#宮野真守#松井恵理子https://t.co/91m502eD1F https://t.co/dBXdEl5njt — アニメイトタイムズ公式 (@animatetimes) May 23, 2023 本消息来自@animatetimes 本消息发送于:May 23, 2023 at 10:10PM

23 May 2023, 13:57 UTC15 viewsread 11 August 2026

【🎉アンケート募集中🍰】05月29日は #早見沙織 さんのお誕生日❣記念して代表作アンケートを実施中♪みなさんの参加お待ちしてます👇👇https://t.co/akvEUAOKwn — アニメイトタイムズ公式 (@animatetimes) May 23, 2023 本消息来自@animatetimes 本消息发送于:May 23, 2023 at 09:35PM

23 May 2023, 13:31 UTC10 viewsread 11 August 2026

\〆切は5月26日⚠/祝! #平川大輔 さんお誕生日🎂「演じた中で一番好きなキャラクターは?」▼回答はコチラ📝https://t.co/l4GhQ6enob…#アニメアニメアンケート https://t.co/NQmu5ukB2P — アニメ!アニメ! (@AnimeAnime_jp) May 23, 2023 本消息来自@AnimeAnime_jp 本消息发送于:May 23, 2023 at 09:23PM

23 May 2023, 13:31 UTC8 viewsread 11 August 2026

\アンケート〆切は5月26日⚠/🐞“虫キャラ”といえば? 🦋 🦗🐌▼回答はコチラ📝https://t.co/F17jG3Q2Kc…#アニメアニメアンケート — アニメ!アニメ! (@AnimeAnime_jp) May 23, 2023 本消息来自@AnimeAnime_jp 本消息发送于:May 23, 2023 at 09:16PM

23 May 2023, 12:30 UTC7 viewsread 11 August 2026

\〆切は5月24日⚠/祝! #沢城みゆき さんお誕生日🎂「演じた中で一番好きなキャラクターは?」▼回答はコチラ📝https://t.co/TaIyqaRN2t…#アニメアニメアンケート https://t.co/kW9TnHCD6u — アニメ!アニメ! (@AnimeAnime_jp) May 23, 2023 本消息来自@AnimeAnime_jp 本消息发送于:May 23, 2023 at 08:24PM

23 May 2023, 11:57 UTC6 viewsread 11 August 2026

【ラジオ】川上千尋StoryJukeBox 第370夜 スプリッツァーを配信開始しました!パーソナリティー: #川上千尋 さん https://t.co/dDYt6QQdIU https://t.co/RV7hUTzYyE — アニメイトタイムズ公式 (@animatetimes) May 23, 2023 本消息来自@animatetimes 本消息发送于:May 23, 2023 at 07:00PM

23 May 2023, 11:29 UTC6 viewsread 11 August 2026

#真野拓実 & #前田誠二 “かっこいいのはリスナーの皆さん” 第8回アニラジアワード「かっこいいラジオ賞」受賞インタビューhttps://t.co/6gB17rJXpZ — アニメ!アニメ! (@AnimeAnime_jp) May 23, 2023 本消息来自@AnimeAnime_jp 本消息发送于:May 23, 2023 at 07:01PM

23 May 2023, 11:29 UTC5 viewsread 11 August 2026

\アンケート〆切は5月25日⚠/“ちょっと抜けている”キャラといえば?🌀#ポンコツの日▼回答はコチラ📝https://t.co/0NUHGzYeZz…#アニメアニメアンケート — アニメ!アニメ! (@AnimeAnime_jp) May 23, 2023 本消息来自@AnimeAnime_jp 本消息发送于:May 23, 2023 at 06:51PM

Showing the 12 most recent of 20 posts we hold for @EACGRP. 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 — 1,022,942 of 1,481,217entries 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.

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

“EACG消息整合频道” (@EACGRP), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/EACGRP.

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.