Telegram RegisterThe public register of Telegram
Telegram profile photo for D&D Book Share

Supergroup

D&D Book Share

@dndbookshare

On this record: Topic · Growth · Engagement · Cite this entry

9,029members

+124 since we began measuring on 7 August 2026

569 online right now

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

Register entry

Telegram ID-1001395598469
TypeSupergroup
Username@dndbookshare
CreatedBetween 1 September 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 August 2026
Last confirmed live27 October 2026
Measurements held22
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/dndbookshare

Topic

Literature — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 92% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

8,9059,0298,9677 August 2026 — 8,905 members8 August 2026 — 8,910 members11 August 2026 — 8,917 members15 August 2026 — 8,919 members18 August 2026 — 8,923 members20 August 2026 — 8,930 members24 August 2026 — 8,930 members24 August 2026 — 8,943 members27 August 2026 — 8,957 members30 August 2026 — 8,956 members3 September 2026 — 8,959 members8 September 2026 — 8,975 members13 September 2026 — 8,974 members17 September 2026 — 8,973 members25 September 2026 — 8,980 members5 October 2026 — 8,983 members10 October 2026 — 9,001 members14 October 2026 — 9,010 members18 October 2026 — 9,008 members21 October 2026 — 9,015 members24 October 2026 — 9,026 members27 October 2026 — 9,029 members7 August 202627 October 2026
22 measurements spanning 81 days, net +124. 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 8,886–9,048 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 22
Measured (UTC)MembersChange
27 Oct 2026, 08:409,029+3
24 Oct 2026, 12:019,026+11
21 Oct 2026, 07:079,015+7
18 Oct 2026, 00:189,008-2
14 Oct 2026, 13:579,010+9
10 Oct 2026, 23:219,001+18
5 Oct 2026, 00:028,983+3
25 Sept 2026, 19:598,980+7
17 Sept 2026, 02:028,973-1
13 Sept 2026, 02:158,974-1
8 Sept 2026, 16:378,975+16
3 Sept 2026, 16:408,959+3
30 Aug 2026, 23:138,956-1
27 Aug 2026, 20:548,957+14
24 Aug 2026, 15:248,943+13
24 Aug 2026, 11:108,930no change
20 Aug 2026, 21:358,930+7
18 Aug 2026, 02:228,923+4
15 Aug 2026, 09:068,919+2
11 Aug 2026, 13:498,917first reading

Engagement

No public post preview. We read this entry on 24 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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

“D&D Book Share” (@dndbookshare), 9,029 members as measured 27 October 2026. Telegram Register, tgregister.com/channel/dndbookshare.

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.