Telegram RegisterThe public register of Telegram
Telegram profile photo for 🗂 Anime Dungeon Project 🔧

Channel

🗂 Anime Dungeon Project 🔧

@AnimeDungeonProject

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

56subscribers

+5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001279923993
TypeChannel
Username@AnimeDungeonProject
Created4 August 2018measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/AnimeDungeonProject

Growth

515653.56 August 2026 — 51 subscribers10 August 2026 — 51 subscribers15 August 2026 — 55 subscribers23 August 2026 — 56 subscribers6 August 202623 August 2026
4 measurements spanning 17 days, net +5. 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 50–57 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 00:2656+1
15 Aug 2026, 00:4555+4
10 Aug 2026, 10:4551no change
6 Aug 2026, 05:0951first reading

Engagement

4 posts held, back to 4 August 2018the 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 4 posts for this entry, the most recent from 19 October 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

19 Oct 2021, 21:20 UTC≈18,900 viewsread 10 August 2026

­­Network: ­ • @AnimeDungeon +SFW • @HDungeon +NSFW • @AnimeFeetDungeon +NSFW • @AnimeThighs +NSFW • @ZettaiRyouiki2D +SFW • @StreetMoeDungeon +SFW • @AnimeGuns +SFW - 🔴 • @AnimeArmpits +NSFW • @DailySalter 🆕 +SFW Music: ♪ @Otogatari +FLAC Other // Bots: • @DiclosGallery +Personal • @DanbooruDump +(N)SFW • @SFWYuri +(N)SFW • @TorrChan +Torrent leech ⚠️ • @FSN_SpringSong +Fate movies • @ArturiaAI_Bot +AI Bot ⚠️ ⚠️

Signed ­ Diclo ❮ 𝙻𝚊𝚋 𝚖𝚎𝚖𝚋𝚎𝚛 00𝟺 ❯

Showing the 4 most recent of 4 posts we hold for @AnimeDungeonProject. 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

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

“🗂 Anime Dungeon Project 🔧” (@AnimeDungeonProject), 56 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/AnimeDungeonProject.

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.