Telegram RegisterThe public register of Telegram
Telegram profile photo for Agent Fire

Bot

Agent Fire

@Claw_Quest_bot

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

40,924monthly users

-110,143 since we began measuring on 6 August 2026

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

Register entry

Telegram ID8421967119
TypeBot
Username@Claw_Quest_bot
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/Claw_Quest_bot

Topic

Gaming — 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 9 August 2026 and assigned it the closest of 31 fixed categories, at 63% 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

40,273151,06795,6706 August 2026 — 151,067 monthly users6 August 2026 — 148,608 monthly users6 August 2026 — 148,608 monthly users7 August 2026 — 146,134 monthly users9 August 2026 — 142,758 monthly users10 August 2026 — 137,598 monthly users11 August 2026 — 133,545 monthly users12 August 2026 — 125,526 monthly users14 August 2026 — 121,182 monthly users16 August 2026 — 118,747 monthly users17 August 2026 — 105,288 monthly users18 August 2026 — 103,076 monthly users20 August 2026 — 104,538 monthly users23 August 2026 — 94,519 monthly users24 August 2026 — 88,402 monthly users25 August 2026 — 86,585 monthly users27 August 2026 — 85,170 monthly users29 August 2026 — 75,806 monthly users30 August 2026 — 76,018 monthly users1 September 2026 — 73,229 monthly users2 September 2026 — 73,014 monthly users3 September 2026 — 73,029 monthly users5 September 2026 — 72,008 monthly users8 September 2026 — 74,786 monthly users11 September 2026 — 74,961 monthly users14 September 2026 — 65,958 monthly users16 September 2026 — 65,817 monthly users18 September 2026 — 73,029 monthly users25 September 2026 — 67,222 monthly users4 October 2026 — 62,926 monthly users8 October 2026 — 60,686 monthly users13 October 2026 — 58,025 monthly users14 October 2026 — 51,923 monthly users16 October 2026 — 51,713 monthly users17 October 2026 — 50,929 monthly users18 October 2026 — 50,395 monthly users19 October 2026 — 43,204 monthly users20 October 2026 — 42,983 monthly users21 October 2026 — 42,347 monthly users23 October 2026 — 42,037 monthly users24 October 2026 — 41,483 monthly users27 October 2026 — 41,383 monthly users27 October 2026 — 41,204 monthly users28 October 2026 — 40,915 monthly users31 October 2026 — 40,593 monthly users2 November 2026 — 40,381 monthly users3 November 2026 — 40,273 monthly users4 November 2026 — 41,029 monthly users5 November 2026 — 41,043 monthly users7 November 2026 — 40,924 monthly users40,9246 August 20267 November 2026
50 measurements spanning 93 days, net -110,143. 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 23,654–167,686 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
7 Nov 2026, 06:5040,924-119
5 Nov 2026, 09:3541,043+14
4 Nov 2026, 06:2041,029+756
3 Nov 2026, 04:0740,273-108
2 Nov 2026, 03:5840,381-212
31 Oct 2026, 01:5040,593-322
28 Oct 2026, 23:0040,915-289
27 Oct 2026, 23:4141,204-179
27 Oct 2026, 01:5541,383-100
24 Oct 2026, 22:1941,483-554
23 Oct 2026, 19:1942,037-310
21 Oct 2026, 21:5042,347-636
20 Oct 2026, 16:3942,983-221
19 Oct 2026, 17:4943,204-7,191
18 Oct 2026, 15:5650,395-534
17 Oct 2026, 14:0750,929-784
16 Oct 2026, 10:4651,713-210
14 Oct 2026, 15:3851,923-6,102
13 Oct 2026, 02:0658,025-2,661
8 Oct 2026, 16:1660,686first 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.

Mentions

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

“Agent Fire” (@Claw_Quest_bot), 40,924 monthly users as measured 7 November 2026. Telegram Register, tgregister.com/channel/Claw_Quest_bot.

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.