Channel
🎶سئوگی سیزلر🥀
@sevgi_sizlar
On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
5,068subscribers
-96 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 | -1001147016550 |
|---|---|
| Type | Channel |
| Username | @sevgi_sizlar |
| Created | Between 1 July 2016 and 29 February 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/sevgi_sizlar |
Topic
Music — 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 75% 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 |
|---|---|---|
| 14 Sept 2026, 17:19 | 5,068 | -4 |
| 11 Sept 2026, 04:59 | 5,072 | -12 |
| 6 Sept 2026, 11:38 | 5,084 | -5 |
| 2 Sept 2026, 09:37 | 5,089 | -9 |
| 1 Sept 2026, 12:06 | 5,098 | no change |
| 30 Aug 2026, 04:02 | 5,098 | -11 |
| 27 Aug 2026, 12:07 | 5,109 | -11 |
| 24 Aug 2026, 15:44 | 5,120 | -10 |
| 21 Aug 2026, 05:57 | 5,130 | -6 |
| 18 Aug 2026, 13:46 | 5,136 | -5 |
| 15 Aug 2026, 12:55 | 5,141 | -7 |
| 12 Aug 2026, 11:07 | 5,148 | -11 |
| 9 Aug 2026, 07:12 | 5,159 | -4 |
| 6 Aug 2026, 06:40 | 5,163 | -1 |
| 6 Aug 2026, 03:59 | 5,164 | 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
@muz_icbay · 29,863
Telegram ranks this channel #17 of 60 here — alongside 59 others — read 8 September 2026
@AHANGETORKIY · 74,100
Telegram ranks this channel #33 of 54 here — alongside 53 others — read 14 September 2026
This channel appears in 2 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“🎶سئوگی سیزلر🥀” (@sevgi_sizlar), 5,068 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/sevgi_sizlar.
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.