Telegram RegisterThe public register of Telegram
Telegram profile photo for PincoSupportBot

Bot

PincoSupportBot

@PincoSupportChatBot

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

61,385monthly users

+764 since we began measuring on 4 September 2026

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

Register entry

Telegram ID8991278886
TypeBot
Username@PincoSupportChatBot
First recorded4 September 2026
Last confirmed live24 October 2026
Measurements held20
Confirmed unchanged2 times, most recently 24 October 2026
On Telegramt.me/PincoSupportChatBot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 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 why it has no browse page of its own yet.

Growth

59,08764,29561,6914 September 2026 — 60,621 monthly users4 September 2026 — 60,621 monthly users6 September 2026 — 60,964 monthly users9 September 2026 — 59,087 monthly users11 September 2026 — 61,055 monthly users13 September 2026 — 61,184 monthly users15 September 2026 — 61,423 monthly users17 September 2026 — 61,424 monthly users19 September 2026 — 61,562 monthly users27 September 2026 — 60,811 monthly users4 October 2026 — 62,249 monthly users9 October 2026 — 63,968 monthly users13 October 2026 — 64,295 monthly users14 October 2026 — 63,966 monthly users15 October 2026 — 63,890 monthly users16 October 2026 — 63,882 monthly users19 October 2026 — 63,797 monthly users20 October 2026 — 63,546 monthly users22 October 2026 — 62,951 monthly users23 October 2026 — 61,385 monthly users61,3854 September 202623 October 2026
20 measurements spanning 49 days, net +764. 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 58,306–65,076 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
23 Oct 2026, 10:0961,385-1,566
22 Oct 2026, 09:2062,951-595
20 Oct 2026, 02:4063,546-251
19 Oct 2026, 03:2063,797-85
16 Oct 2026, 22:3863,882-8
15 Oct 2026, 19:1763,890-76
14 Oct 2026, 15:4963,966-329
13 Oct 2026, 07:4864,295+327
9 Oct 2026, 05:5963,968+1,719
4 Oct 2026, 19:1862,249+1,438
27 Sept 2026, 00:3560,811-751
19 Sept 2026, 17:4061,562+138
17 Sept 2026, 07:0061,424+1
15 Sept 2026, 07:5961,423+239
13 Sept 2026, 18:2061,184+129
11 Sept 2026, 21:5761,055+1,968
9 Sept 2026, 13:2159,087-1,877
6 Sept 2026, 06:5860,964+343
4 Sept 2026, 19:2060,621no change
4 Sept 2026, 18:4760,621first 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.

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

“PincoSupportBot” (@PincoSupportChatBot), 61,385 monthly users as measured 23 October 2026. Telegram Register, tgregister.com/channel/PincoSupportChatBot.

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.