Channel
بذله گویی
@bazlegoi
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,866subscribers
-33 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001429504849 |
|---|---|
| Type | Channel |
| Username | @bazlegoi |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/bazlegoi |
Topic
Memes & entertainment — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 02:00 | 3,866 | -5 |
| 10 Sept 2026, 19:37 | 3,871 | -5 |
| 6 Sept 2026, 00:09 | 3,876 | no change |
| 2 Sept 2026, 05:43 | 3,876 | -4 |
| 30 Aug 2026, 15:52 | 3,880 | -4 |
| 27 Aug 2026, 15:43 | 3,884 | -1 |
| 24 Aug 2026, 14:53 | 3,885 | -4 |
| 21 Aug 2026, 02:54 | 3,889 | -3 |
| 17 Aug 2026, 17:03 | 3,892 | -4 |
| 14 Aug 2026, 07:04 | 3,896 | -1 |
| 10 Aug 2026, 16:15 | 3,897 | -1 |
| 7 Aug 2026, 13:11 | 3,898 | -1 |
| 6 Aug 2026, 20:54 | 3,899 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@kxhyar · 49,224
Telegram ranks this channel #1 of 83 here — alongside 82 others — read 30 August 2026
@agent_ali · 52,290
Telegram ranks this channel #10 of 88 here — alongside 87 others — read 24 August 2026
@dollar_khabari · 73,526
Telegram ranks this channel #14 of 66 here — alongside 65 others — read 22 August 2026
@Tahlil_aminian · 91,474
Telegram ranks this channel #24 of 86 here — alongside 85 others — read 20 August 2026
@healthclinic_ir · 22,881
Telegram ranks this channel #31 of 78 here — alongside 77 others — read 19 September 2026
@dokolismz · 40,082
Telegram ranks this channel #70 of 81 here — alongside 80 others — read 30 August 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“بذله گویی” (@bazlegoi), 3,866 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/bazlegoi.
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.