Telegram RegisterThe public register of Telegram
Telegram profile photo for TrueCallerBot

Bot

TrueCallerBot

@TruecallerR0Bot

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

375,459monthly users

+4,553 since we began measuring on 7 August 2026

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

Register entry

Telegram ID6235241056
TypeBot
Username@TruecallerR0Bot
First recorded7 August 2026
Last confirmed live26 October 2026
Measurements held49
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/TruecallerR0Bot

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 96% 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 why it has no browse page of its own yet.

Growth

366,450391,289378,869.57 August 2026 — 370,906 monthly users7 August 2026 — 370,906 monthly users8 August 2026 — 371,259 monthly users9 August 2026 — 373,376 monthly users10 August 2026 — 373,770 monthly users11 August 2026 — 375,002 monthly users12 August 2026 — 376,611 monthly users13 August 2026 — 375,883 monthly users15 August 2026 — 374,841 monthly users16 August 2026 — 373,821 monthly users17 August 2026 — 374,200 monthly users18 August 2026 — 374,239 monthly users20 August 2026 — 375,645 monthly users21 August 2026 — 377,424 monthly users22 August 2026 — 378,884 monthly users24 August 2026 — 378,147 monthly users25 August 2026 — 377,156 monthly users26 August 2026 — 377,581 monthly users27 August 2026 — 379,168 monthly users28 August 2026 — 382,347 monthly users29 August 2026 — 384,169 monthly users30 August 2026 — 385,555 monthly users31 August 2026 — 385,602 monthly users1 September 2026 — 384,838 monthly users2 September 2026 — 386,951 monthly users3 September 2026 — 387,049 monthly users5 September 2026 — 387,884 monthly users9 September 2026 — 382,173 monthly users11 September 2026 — 389,117 monthly users13 September 2026 — 391,289 monthly users15 September 2026 — 383,237 monthly users17 September 2026 — 382,635 monthly users25 September 2026 — 387,736 monthly users4 October 2026 — 382,612 monthly users8 October 2026 — 383,508 monthly users13 October 2026 — 379,412 monthly users14 October 2026 — 376,626 monthly users15 October 2026 — 375,854 monthly users16 October 2026 — 375,700 monthly users17 October 2026 — 375,336 monthly users18 October 2026 — 374,386 monthly users19 October 2026 — 373,916 monthly users20 October 2026 — 373,194 monthly users21 October 2026 — 373,930 monthly users22 October 2026 — 366,450 monthly users23 October 2026 — 367,044 monthly users24 October 2026 — 367,787 monthly users25 October 2026 — 375,511 monthly users26 October 2026 — 375,459 monthly users375,4597 August 202626 October 2026
49 measurements spanning 80 days, net +4,553. 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 362,724–395,015 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 49
Measured (UTC)Monthly usersChange
26 Oct 2026, 16:08375,459-52
25 Oct 2026, 19:08375,511+7,724
24 Oct 2026, 22:16367,787+743
23 Oct 2026, 21:57367,044+594
22 Oct 2026, 19:00366,450-7,480
21 Oct 2026, 13:46373,930+736
20 Oct 2026, 10:51373,194-722
19 Oct 2026, 12:37373,916-470
18 Oct 2026, 09:45374,386-950
17 Oct 2026, 09:58375,336-364
16 Oct 2026, 11:21375,700-154
15 Oct 2026, 09:37375,854-772
14 Oct 2026, 11:37376,626-2,786
13 Oct 2026, 01:41379,412-4,096
8 Oct 2026, 17:01383,508+896
4 Oct 2026, 04:38382,612-5,124
25 Sept 2026, 13:15387,736+5,101
17 Sept 2026, 04:57382,635-602
15 Sept 2026, 01:59383,237-8,052
13 Sept 2026, 08:19391,289first 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 5 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 26 October 2026 — this entry's latest reading, not the date you are reading this.

“TrueCallerBot” (@TruecallerR0Bot), 375,459 monthly users as measured 26 October 2026. Telegram Register, tgregister.com/channel/TruecallerR0Bot.

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.