Channel
•SG•
@sogiwgh
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,359subscribers
-203 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 | -1001093543316 |
|---|---|
| Type | Channel |
| Username | @sogiwgh |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/sogiwgh |
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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 08:16 | 5,359 | -5 |
| 4 Nov 2026, 12:27 | 5,364 | -8 |
| 1 Nov 2026, 07:48 | 5,372 | -5 |
| 29 Oct 2026, 09:37 | 5,377 | -2 |
| 26 Oct 2026, 17:30 | 5,379 | -5 |
| 23 Oct 2026, 23:54 | 5,384 | -3 |
| 21 Oct 2026, 03:46 | 5,387 | -4 |
| 18 Oct 2026, 00:07 | 5,391 | -8 |
| 15 Oct 2026, 04:08 | 5,399 | -3 |
| 12 Oct 2026, 05:20 | 5,402 | -14 |
| 5 Oct 2026, 09:00 | 5,416 | -19 |
| 26 Sept 2026, 17:56 | 5,435 | -15 |
| 17 Sept 2026, 17:21 | 5,450 | -8 |
| 13 Sept 2026, 22:20 | 5,458 | -9 |
| 10 Sept 2026, 14:56 | 5,467 | -17 |
| 5 Sept 2026, 04:36 | 5,484 | -15 |
| 1 Sept 2026, 17:03 | 5,499 | -9 |
| 30 Aug 2026, 22:28 | 5,508 | no change |
| 29 Aug 2026, 15:29 | 5,508 | -8 |
| 26 Aug 2026, 10:26 | 5,516 | 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.
@Nilbhx · 94,727
Telegram ranks this channel #5 of 58 here — alongside 57 others — read 25 August 2026
@ghazallchanel · 50,752
Telegram ranks this channel #14 of 63 here — alongside 62 others — read 25 August 2026
@Absurdwolrd · 67,930
Telegram ranks this channel #21 of 71 here — alongside 70 others — read 24 August 2026
@honeyprrofficial · 42,974
Telegram ranks this channel #33 of 80 here — alongside 79 others — read 27 August 2026
@mrordibeheshti · 37,642
Telegram ranks this channel #78 of 87 here — alongside 86 others — read 31 August 2026
This channel appears in 5 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“•SG•” (@sogiwgh), 5,359 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/sogiwgh.
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.