Telegram RegisterThe public register of Telegram
Telegram profile photo for Soul Scanner

Bot

Soul Scanner

@soul_scanner_bot

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

23,786monthly users

-991 since we began measuring on 6 August 2026

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

Register entry

Telegram ID6872314605
TypeBot
Username@soul_scanner_bot
First recorded15 August 2026
Last confirmed live15 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/soul_scanner_bot

Growth

23,54024,77724,158.56 August 2026 — 24,777 monthly users7 August 2026 — 24,655 monthly users8 August 2026 — 24,478 monthly users9 August 2026 — 24,287 monthly users10 August 2026 — 23,540 monthly users11 August 2026 — 23,830 monthly users12 August 2026 — 23,834 monthly users14 August 2026 — 23,843 monthly users15 August 2026 — 23,843 monthly users15 August 2026 — 23,786 monthly users23,7866 August 202615 August 2026
10 measurements spanning 10 days, net -991. 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,354–24,963 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
15 Aug 2026, 20:0823,786-57
15 Aug 2026, 17:2323,843no change
14 Aug 2026, 10:3723,843+9
12 Aug 2026, 07:4423,834+4
11 Aug 2026, 08:3623,830+290
10 Aug 2026, 10:3123,540-747
9 Aug 2026, 08:0124,287-191
8 Aug 2026, 07:1124,478-177
7 Aug 2026, 08:5624,655-122
6 Aug 2026, 03:3824,777first 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

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 45 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Soul Scanner” (@soul_scanner_bot), 23,786 monthly users as measured 15 August 2026. Telegram Register, tgregister.com/channel/soul_scanner_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.