Channel
Story_editoorr
@story_editoorrr
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,333subscribers
-141 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001992949507 |
|---|---|
| Type | Channel |
| Username | @story_editoorrr |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/story_editoorrr |
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 |
|---|---|---|
| 16 Sept 2026, 08:36 | 4,333 | -24 |
| 12 Sept 2026, 23:16 | 4,357 | -19 |
| 8 Sept 2026, 14:38 | 4,376 | -24 |
| 3 Sept 2026, 22:29 | 4,400 | no change |
| 3 Sept 2026, 12:55 | 4,400 | -12 |
| 31 Aug 2026, 02:47 | 4,412 | -6 |
| 27 Aug 2026, 20:42 | 4,418 | -13 |
| 25 Aug 2026, 02:45 | 4,431 | -28 |
| 21 Aug 2026, 14:58 | 4,459 | -5 |
| 18 Aug 2026, 15:23 | 4,464 | -3 |
| 15 Aug 2026, 17:33 | 4,467 | -7 |
| 14 Aug 2026, 19:01 | 4,474 | 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.
@manisa_photographer · 42,273
Telegram ranks this channel #17 of 57 here — alongside 56 others — read 29 August 2026
@maryaamidea · 44,376
Telegram ranks this channel #34 of 56 here — alongside 55 others — read 1 September 2026
@jangi2711 · 112,353
Telegram ranks this channel #68 of 86 here — alongside 85 others — read 14 August 2026
This channel appears in 3 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Story_editoorr” (@story_editoorrr), 4,333 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/story_editoorrr.
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.