Channel
Говоров0⃣7⃣
@govorun07
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,361subscribers
-26 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001570603040 |
|---|---|
| Type | Channel |
| Username | @govorun07 |
| Created | 29 July 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 30 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/govorun07 |
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 30 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 08:35 | 1,361 | -2 |
| 29 Oct 2026, 22:36 | 1,363 | -2 |
| 20 Oct 2026, 17:06 | 1,365 | -1 |
| 17 Oct 2026, 22:06 | 1,366 | -2 |
| 15 Oct 2026, 01:37 | 1,368 | -2 |
| 11 Oct 2026, 23:38 | 1,370 | -3 |
| 30 Sept 2026, 17:06 | 1,373 | no change |
| 27 Sept 2026, 23:01 | 1,373 | -4 |
| 18 Sept 2026, 19:21 | 1,377 | -1 |
| 14 Sept 2026, 11:19 | 1,378 | -1 |
| 5 Sept 2026, 21:16 | 1,379 | -2 |
| 1 Sept 2026, 16:13 | 1,381 | +2 |
| 29 Aug 2026, 15:12 | 1,379 | -2 |
| 23 Aug 2026, 04:26 | 1,381 | -2 |
| 16 Aug 2026, 18:05 | 1,383 | -1 |
| 13 Aug 2026, 09:16 | 1,384 | -2 |
| 10 Aug 2026, 00:29 | 1,386 | -1 |
| 6 Aug 2026, 09:43 | 1,387 | 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.
@sindika · 27,827
Telegram ranks this channel #20 of 87 here — alongside 86 others — read 10 September 2026
@streli_kazbeka · 128,443
Telegram ranks this channel #56 of 99 here — alongside 98 others — read 13 August 2026
@Kokov_Kazbek · 19,330
Telegram ranks this channel #71 of 93 here — alongside 92 others — read 2 October 2026
@patriotkbr · 30,144
Telegram ranks this channel #76 of 93 here — alongside 92 others — read 7 September 2026
@skfo_telegraph · 22,071
Telegram ranks this channel #78 of 94 here — alongside 93 others — read 21 September 2026
@kavkaz_leakbez · 30,967
Telegram ranks this channel #85 of 95 here — alongside 94 others — read 6 September 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Говоров0⃣7⃣” (@govorun07), 1,361 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/govorun07.
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.