Telegram RegisterThe public register of Telegram
Telegram profile photo for ربات چت دوستیابی و گپ رل یابی

Bot

ربات چت دوستیابی و گپ رل یابی

@gapgofttbot

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

120,366monthly users

-26,590 since we began measuring on 6 August 2026

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

Register entry

Telegram ID1681929663
TypeBot
Username@gapgofttbot
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/gapgofttbot

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

96,430146,956121,693120,3666 August 202610 November 2026
63 measurements spanning 97 days, net -26,590. 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 88,851–154,535 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 63
Measured (UTC)Monthly usersChange
10 Nov 2026, 14:59120,366+247
9 Nov 2026, 02:59120,119+865
7 Nov 2026, 17:59119,254+374
6 Nov 2026, 17:27118,880+117
4 Nov 2026, 17:59118,763+606
3 Nov 2026, 15:07118,157+1,086
2 Nov 2026, 18:19117,071+947
1 Nov 2026, 21:49116,124+1,025
31 Oct 2026, 19:00115,099+1,859
30 Oct 2026, 17:40113,240+1,302
29 Oct 2026, 16:56111,938+4,077
28 Oct 2026, 15:05107,861+513
27 Oct 2026, 16:05107,348-1,467
26 Oct 2026, 14:56108,815+744
25 Oct 2026, 17:20108,071+557
24 Oct 2026, 18:09107,514+484
22 Oct 2026, 23:36107,030+174
21 Oct 2026, 20:51106,856+132
20 Oct 2026, 17:07106,724+789
19 Oct 2026, 15:28105,935first 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 13 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“ربات چت دوستیابی و گپ رل یابی” (@gapgofttbot), 120,366 monthly users as measured 10 November 2026. Telegram Register, tgregister.com/channel/gapgofttbot.

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.