Telegram RegisterThe public register of Telegram
Telegram profile photo for Spin City Bot

Bot

Spin City Bot

@SpinCityBot

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

12,479monthly users

+99 since we began measuring on 7 August 2026

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

Register entry

Telegram ID957208369
TypeBot
Username@SpinCityBot
First recorded20 August 2026
Last confirmed live25 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/SpinCityBot

Growth

12,21212,78312,497.57 August 2026 — 12,380 monthly users8 August 2026 — 12,473 monthly users9 August 2026 — 12,657 monthly users10 August 2026 — 12,783 monthly users12 August 2026 — 12,663 monthly users13 August 2026 — 12,455 monthly users15 August 2026 — 12,321 monthly users16 August 2026 — 12,243 monthly users17 August 2026 — 12,234 monthly users18 August 2026 — 12,212 monthly users19 August 2026 — 12,294 monthly users20 August 2026 — 12,294 monthly users21 August 2026 — 12,279 monthly users22 August 2026 — 12,308 monthly users24 August 2026 — 12,492 monthly users25 August 2026 — 12,479 monthly users12,4797 August 202625 August 2026
16 measurements spanning 18 days, net +99. 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 12,126–12,869 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 16:3612,479-13
24 Aug 2026, 13:1812,492+184
22 Aug 2026, 21:1412,308+29
21 Aug 2026, 14:2712,279-15
20 Aug 2026, 20:1212,294no change
19 Aug 2026, 14:3512,294+82
18 Aug 2026, 17:3612,212-22
17 Aug 2026, 19:0312,234-9
16 Aug 2026, 16:1612,243-78
15 Aug 2026, 03:1712,321-134
13 Aug 2026, 23:1712,455-208
12 Aug 2026, 17:4412,663-120
10 Aug 2026, 18:2112,783+126
9 Aug 2026, 20:2112,657+184
8 Aug 2026, 21:2712,473+93
7 Aug 2026, 09:3112,380first 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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Spin City Bot” (@SpinCityBot), 12,479 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/SpinCityBot.

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.