Telegram RegisterThe public register of Telegram
Telegram profile photo for Dialog Spy Bot

Bot

Dialog Spy Bot

@DialogSpyBot

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

313,720monthly users

+7,251 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID7301157676
TypeBot
Username@DialogSpyBot
First recorded7 August 2026
Last confirmed live4 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/DialogSpyBot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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

299,139313,720306,429.57 August 2026 — 306,469 monthly users7 August 2026 — 306,469 monthly users8 August 2026 — 300,262 monthly users9 August 2026 — 299,139 monthly users10 August 2026 — 299,384 monthly users11 August 2026 — 306,689 monthly users12 August 2026 — 307,998 monthly users13 August 2026 — 307,964 monthly users15 August 2026 — 307,709 monthly users16 August 2026 — 306,171 monthly users17 August 2026 — 306,845 monthly users18 August 2026 — 307,308 monthly users19 August 2026 — 307,636 monthly users20 August 2026 — 308,168 monthly users21 August 2026 — 308,730 monthly users22 August 2026 — 308,143 monthly users24 August 2026 — 307,954 monthly users25 August 2026 — 308,671 monthly users27 August 2026 — 309,626 monthly users28 August 2026 — 308,503 monthly users30 August 2026 — 308,473 monthly users31 August 2026 — 307,005 monthly users1 September 2026 — 306,579 monthly users2 September 2026 — 306,047 monthly users4 September 2026 — 306,189 monthly users6 September 2026 — 304,443 monthly users9 September 2026 — 306,368 monthly users12 September 2026 — 304,887 monthly users13 September 2026 — 303,846 monthly users15 September 2026 — 303,930 monthly users17 September 2026 — 304,874 monthly users26 September 2026 — 304,482 monthly users4 October 2026 — 305,198 monthly users9 October 2026 — 307,154 monthly users13 October 2026 — 307,366 monthly users14 October 2026 — 308,798 monthly users15 October 2026 — 308,740 monthly users16 October 2026 — 309,088 monthly users17 October 2026 — 309,026 monthly users18 October 2026 — 308,831 monthly users19 October 2026 — 309,407 monthly users20 October 2026 — 310,084 monthly users21 October 2026 — 309,924 monthly users22 October 2026 — 310,267 monthly users24 October 2026 — 312,689 monthly users25 October 2026 — 312,831 monthly users26 October 2026 — 313,234 monthly users27 October 2026 — 313,543 monthly users28 October 2026 — 312,944 monthly users29 October 2026 — 312,082 monthly users30 October 2026 — 312,382 monthly users31 October 2026 — 311,236 monthly users1 November 2026 — 311,741 monthly users2 November 2026 — 312,408 monthly users3 November 2026 — 312,958 monthly users4 November 2026 — 313,720 monthly users7 August 20264 November 2026
56 measurements spanning 89 days, net +7,251. 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 296,952–315,907 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 56
Measured (UTC)Monthly usersChange
4 Nov 2026, 22:20313,720+762
3 Nov 2026, 22:59312,958+550
2 Nov 2026, 20:31312,408+667
1 Nov 2026, 18:27311,741+505
31 Oct 2026, 18:31311,236-1,146
30 Oct 2026, 20:19312,382+300
29 Oct 2026, 20:08312,082-862
28 Oct 2026, 22:56312,944-599
27 Oct 2026, 18:51313,543+309
26 Oct 2026, 15:34313,234+403
25 Oct 2026, 18:40312,831+142
24 Oct 2026, 16:20312,689+2,422
22 Oct 2026, 19:59310,267+343
21 Oct 2026, 15:38309,924-160
20 Oct 2026, 13:19310,084+677
19 Oct 2026, 14:06309,407+576
18 Oct 2026, 17:20308,831-195
17 Oct 2026, 16:17309,026-62
16 Oct 2026, 17:04309,088+348
15 Oct 2026, 20:01308,740first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 4 registered channels — 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.

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

“Dialog Spy Bot” (@DialogSpyBot), 313,720 monthly users as measured 4 November 2026. Telegram Register, tgregister.com/channel/DialogSpyBot.

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.