Channel
NIMIXE
@nimixee
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,062subscribers
-155 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001743207565 |
|---|---|
| Type | Channel |
| Username | @nimixee |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/nimixee |
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 14 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 |
|---|---|---|
| 6 Nov 2026, 18:37 | 3,062 | -7 |
| 3 Nov 2026, 20:30 | 3,069 | -8 |
| 31 Oct 2026, 16:47 | 3,077 | -8 |
| 28 Oct 2026, 18:11 | 3,085 | -7 |
| 25 Oct 2026, 16:37 | 3,092 | -7 |
| 22 Oct 2026, 15:54 | 3,099 | -6 |
| 19 Oct 2026, 06:55 | 3,105 | -1 |
| 16 Oct 2026, 13:21 | 3,106 | -1 |
| 13 Oct 2026, 11:06 | 3,107 | -18 |
| 7 Oct 2026, 02:21 | 3,125 | -13 |
| 30 Sept 2026, 08:41 | 3,138 | -25 |
| 19 Sept 2026, 13:36 | 3,163 | -9 |
| 15 Sept 2026, 02:40 | 3,172 | -2 |
| 11 Sept 2026, 11:57 | 3,174 | -14 |
| 10 Sept 2026, 00:34 | 3,188 | no change |
| 6 Sept 2026, 18:40 | 3,188 | -6 |
| 2 Sept 2026, 05:28 | 3,194 | -5 |
| 30 Aug 2026, 02:13 | 3,199 | -1 |
| 27 Aug 2026, 08:58 | 3,200 | -5 |
| 24 Aug 2026, 14:56 | 3,205 | 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.
@KamtarBemalim · 64,388
Telegram ranks this channel #4 of 54 here — alongside 53 others — read 20 August 2026
@kordDip · 44,680
Telegram ranks this channel #50 of 72 here — alongside 71 others — read 27 August 2026
@Lati_Muzic · 67,402
Telegram ranks this channel #50 of 80 here — alongside 79 others — read 20 August 2026
@raptamifon · 34,703
Telegram ranks this channel #58 of 73 here — alongside 72 others — read 1 September 2026
@alisorenax · 18,477
Telegram ranks this channel #79 of 80 here — alongside 79 others — read 5 October 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“NIMIXE” (@nimixee), 3,062 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/nimixee.
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.