Channel
CŘãŽy🙃Mãtĥ
@Cra6ymath
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,639subscribers
-2 since we began measuring on 10 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001428543784 |
|---|---|
| Type | Channel |
| Username | @Cra6ymath |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/Cra6ymath |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 1 Nov 2026, 19:08 | 3,639 | -3 |
| 29 Oct 2026, 18:40 | 3,642 | -1 |
| 27 Oct 2026, 01:49 | 3,643 | -4 |
| 21 Oct 2026, 14:51 | 3,647 | -2 |
| 18 Oct 2026, 11:36 | 3,649 | +1 |
| 15 Oct 2026, 11:35 | 3,648 | +1 |
| 12 Oct 2026, 04:20 | 3,647 | +4 |
| 5 Oct 2026, 09:57 | 3,643 | -4 |
| 26 Sept 2026, 23:18 | 3,647 | +7 |
| 15 Sept 2026, 13:57 | 3,640 | -9 |
| 12 Sept 2026, 00:59 | 3,649 | +8 |
| 10 Sept 2026, 13:28 | 3,641 | no change |
| 10 Sept 2026, 08:17 | 3,641 | 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.
@engeslamemam · 24,154
Telegram ranks this channel #2 of 48 here — alongside 47 others — read 19 September 2026
@ashrafgaber83 · 32,965
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 10 September 2026
@math_books02 · 19,602
Telegram ranks this channel #12 of 65 here — alongside 64 others — read 30 September 2026
@mozkra4all · 20,234
Telegram ranks this channel #17 of 77 here — alongside 76 others — read 30 September 2026
@yallanzaker4a · 21,400
Telegram ranks this channel #17 of 60 here — alongside 59 others — read 25 September 2026
@yallanzaker5a · 21,009
Telegram ranks this channel #18 of 67 here — alongside 66 others — read 26 September 2026
This channel appears in 6 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“CŘãŽy🙃Mãtĥ” (@Cra6ymath), 3,639 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/Cra6ymath.
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.