Channel
@doloreshazeanime
On this record: Growth · Engagement · Posts · Cite this entry
15,768subscribers
-176 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001267139106 |
|---|---|
| Type | Channel |
| Username | @doloreshazeanime |
| Created | 5 June 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/doloreshazeanime |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 21:01 | 15,768 | -5 |
| 5 Sept 2026, 16:41 | 15,773 | -4 |
| 3 Sept 2026, 16:17 | 15,777 | -8 |
| 2 Sept 2026, 10:27 | 15,785 | -13 |
| 1 Sept 2026, 10:57 | 15,798 | -5 |
| 31 Aug 2026, 08:04 | 15,803 | -2 |
| 29 Aug 2026, 08:05 | 15,805 | -1 |
| 28 Aug 2026, 05:24 | 15,806 | -1 |
| 27 Aug 2026, 06:44 | 15,807 | -1 |
| 26 Aug 2026, 08:53 | 15,808 | -13 |
| 25 Aug 2026, 08:26 | 15,821 | -3 |
| 24 Aug 2026, 09:35 | 15,824 | -5 |
| 22 Aug 2026, 19:36 | 15,829 | -1 |
| 21 Aug 2026, 10:17 | 15,830 | -1 |
| 20 Aug 2026, 09:38 | 15,831 | -7 |
| 19 Aug 2026, 12:06 | 15,838 | -15 |
| 18 Aug 2026, 08:53 | 15,853 | -7 |
| 17 Aug 2026, 09:33 | 15,860 | -4 |
| 15 Aug 2026, 18:14 | 15,864 | -3 |
| 14 Aug 2026, 06:05 | 15,867 | first reading |
18 posts held, back to 9 April 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 54 pages of 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 18 posts for this entry, the most recent from 23 July 2026. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
https://twitter.com/RUTON/status/1794652275740438703
Signed Yuko Amamiya
https://twitter.com/riokasen94/status/1779707415383941365
Signed Yuko Amamiya
https://www.pixiv.net/artworks/118945858
Signed Yuko Amamiya
https://twitter.com/cluseller/status/1786198739893497919
Signed Yuko Amamiya
https://twitter.com/commushows/status/1784579589987258520
Signed Yuko Amamiya
Photo, posted without a caption
Signed Yuko Amamiya
Photo, posted without a caption
Signed Yuko Amamiya
https://twitter.com/dmvvhv_ver2/status/1785791808783479027
Signed Yuko Amamiya
Photo, posted without a caption
Signed Yuko Amamiya
https://twitter.com/pro_p24/status/1777641411996708967
Signed Yuko Amamiya
Photo, posted without a caption
Signed Yuko Amamiya
Showing the 12 most recent of 18 posts we hold for @doloreshazeanime. 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“优子的沙雕吐槽频道” (@doloreshazeanime), 15,768 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/doloreshazeanime.
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.