Channel
Steno Vibes™
@Steno_Dictations
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,174subscribers
+8 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001387876683 |
|---|---|
| Type | Channel |
| Username | @Steno_Dictations |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/Steno_Dictations |
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 |
|---|---|---|
| 3 Nov 2026, 16:26 | 5,174 | +8 |
| 22 Oct 2026, 21:19 | 5,166 | -4 |
| 20 Oct 2026, 04:55 | 5,170 | +1 |
| 17 Oct 2026, 00:41 | 5,169 | +6 |
| 13 Oct 2026, 20:58 | 5,163 | -2 |
| 8 Oct 2026, 02:16 | 5,165 | -1 |
| 1 Oct 2026, 13:37 | 5,166 | +9 |
| 16 Sept 2026, 13:19 | 5,157 | -8 |
| 12 Sept 2026, 13:57 | 5,165 | -1 |
| 8 Sept 2026, 20:39 | 5,166 | +16 |
| 3 Sept 2026, 22:38 | 5,150 | +6 |
| 31 Aug 2026, 23:24 | 5,144 | no change |
| 31 Aug 2026, 15:08 | 5,144 | -3 |
| 29 Aug 2026, 00:36 | 5,147 | -3 |
| 25 Aug 2026, 15:58 | 5,150 | -7 |
| 22 Aug 2026, 23:04 | 5,157 | -6 |
| 16 Aug 2026, 16:24 | 5,163 | -4 |
| 13 Aug 2026, 10:16 | 5,167 | +1 |
| 12 Aug 2026, 13:15 | 5,166 | 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.
@ApniPariksha · 24,695
Telegram ranks this channel #1 of 58 here — alongside 57 others — read 15 September 2026
@STENO_SSC · 21,900
Telegram ranks this channel #4 of 51 here — alongside 50 others — read 23 September 2026
@seekerasjob · 92,534
Telegram ranks this channel #88 of 88 here — alongside 87 others — read 16 August 2026
@amansrv · 171,964
Telegram ranks this channel #88 of 89 here — alongside 88 others — read 12 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Steno Vibes™” (@Steno_Dictations), 5,174 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/Steno_Dictations.
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.