Channel
U3
@miniem
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,520subscribers
-124 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001230741514 |
|---|---|
| Type | Channel |
| Username | @miniem |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/miniem |
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 15 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:46 | 2,520 | -4 |
| 4 Nov 2026, 13:19 | 2,524 | -6 |
| 1 Nov 2026, 10:26 | 2,530 | -6 |
| 29 Oct 2026, 02:29 | 2,536 | -4 |
| 26 Oct 2026, 01:46 | 2,540 | -7 |
| 23 Oct 2026, 03:57 | 2,547 | -3 |
| 20 Oct 2026, 14:39 | 2,550 | -6 |
| 17 Oct 2026, 06:08 | 2,556 | -5 |
| 14 Oct 2026, 13:00 | 2,561 | -10 |
| 11 Oct 2026, 03:17 | 2,571 | -11 |
| 4 Oct 2026, 19:20 | 2,582 | -14 |
| 25 Sept 2026, 02:02 | 2,596 | -10 |
| 16 Sept 2026, 19:38 | 2,606 | -3 |
| 14 Sept 2026, 21:12 | 2,609 | no change |
| 12 Sept 2026, 20:20 | 2,609 | -6 |
| 9 Sept 2026, 01:40 | 2,615 | -7 |
| 3 Sept 2026, 13:41 | 2,622 | -7 |
| 30 Aug 2026, 20:28 | 2,629 | -4 |
| 27 Aug 2026, 16:44 | 2,633 | -1 |
| 24 Aug 2026, 20:45 | 2,634 | 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.
@Rap3daOriginal · 157,673
Telegram ranks this channel #22 of 39 here — alongside 38 others — read 26 September 2026
@Evolmusic · 22,562
Telegram ranks this channel #45 of 62 here — alongside 61 others — read 20 September 2026
@betforward_officiall1111 · 290,298
Telegram ranks this channel #69 of 76 here — alongside 75 others — read 17 August 2026
@Free_HipHop · 32,288
Telegram ranks this channel #80 of 82 here — alongside 81 others — read 2 September 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“U3” (@miniem), 2,520 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/miniem.
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.