Channel
TWARQ_ by: MONA 🌟 كريكت cricut
@twarq
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,763subscribers
-11 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001457459572 |
|---|---|
| Type | Channel |
| Username | @twarq |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/twarq |
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 96% 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 |
|---|---|---|
| 2 Nov 2026, 15:55 | 2,763 | +2 |
| 31 Oct 2026, 00:35 | 2,761 | -2 |
| 28 Oct 2026, 05:05 | 2,763 | -4 |
| 25 Oct 2026, 06:07 | 2,767 | +2 |
| 21 Oct 2026, 19:27 | 2,765 | -2 |
| 18 Oct 2026, 11:48 | 2,767 | -3 |
| 15 Oct 2026, 16:06 | 2,770 | -3 |
| 6 Oct 2026, 03:02 | 2,773 | -4 |
| 29 Sept 2026, 04:18 | 2,777 | +7 |
| 18 Sept 2026, 23:36 | 2,770 | -1 |
| 15 Sept 2026, 00:40 | 2,771 | -5 |
| 13 Sept 2026, 01:12 | 2,776 | no change |
| 11 Sept 2026, 19:39 | 2,776 | +2 |
| 7 Sept 2026, 15:41 | 2,774 | -5 |
| 2 Sept 2026, 07:58 | 2,779 | -3 |
| 30 Aug 2026, 10:33 | 2,782 | -1 |
| 27 Aug 2026, 09:12 | 2,783 | +2 |
| 24 Aug 2026, 04:13 | 2,781 | +4 |
| 20 Aug 2026, 02:11 | 2,777 | +3 |
| 13 Aug 2026, 04:45 | 2,774 | 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.
@designtheme · 45,553
Telegram ranks this channel #12 of 62 here — alongside 61 others — read 31 August 2026
@rai1435 · 79,138
Telegram ranks this channel #20 of 65 here — alongside 64 others — read 31 August 2026
@zooz14111 · 37,285
Telegram ranks this channel #26 of 68 here — alongside 67 others — read 4 September 2026
@y1400h · 130,520
Telegram ranks this channel #79 of 92 here — alongside 91 others — read 13 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“TWARQ_ by: MONA 🌟 كريكت cricut” (@twarq), 2,763 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/twarq.
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.