Channel
Saghi
@saghisakhte
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,278subscribers
-56 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001066760126 |
|---|---|
| Type | Channel |
| Username | @saghisakhte |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/saghisakhte |
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 13 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 20:55 | 4,278 | -3 |
| 12 Sept 2026, 04:00 | 4,281 | -10 |
| 7 Sept 2026, 17:36 | 4,291 | -6 |
| 4 Sept 2026, 12:31 | 4,297 | no change |
| 3 Sept 2026, 01:58 | 4,297 | -7 |
| 30 Aug 2026, 22:26 | 4,304 | -10 |
| 28 Aug 2026, 01:55 | 4,314 | -2 |
| 24 Aug 2026, 17:25 | 4,316 | -6 |
| 20 Aug 2026, 23:14 | 4,322 | -3 |
| 17 Aug 2026, 16:26 | 4,325 | -8 |
| 14 Aug 2026, 19:58 | 4,333 | -1 |
| 13 Aug 2026, 22:06 | 4,334 | 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.
@DjAlirezA · 100,076
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 15 August 2026
@DJ_Siavash · 50,557
Telegram ranks this channel #22 of 75 here — alongside 74 others — read 25 August 2026
@boxkhabari · 51,087
Telegram ranks this channel #32 of 43 here — alongside 42 others — read 24 August 2026
@MUSiICAMi · 126,219
Telegram ranks this channel #40 of 57 here — alongside 56 others — read 13 August 2026
This channel appears in 4 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Saghi” (@saghisakhte), 4,278 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/saghisakhte.
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.