Channel
@degchurauylash
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
255subscribers
+5 since we began measuring on 19 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001813989775 |
|---|---|
| Type | Channel |
| Username | @degchurauylash |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 4 November 2026 |
| On Telegram | t.me/degchurauylash |
Religion — 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 6 October 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 05:50 | 255 | -1 |
| 22 Oct 2026, 03:34 | 256 | +2 |
| 14 Oct 2026, 07:39 | 254 | -2 |
| 6 Oct 2026, 14:41 | 256 | +1 |
| 25 Sept 2026, 17:21 | 255 | +5 |
| 19 Sept 2026, 09:22 | 250 | first reading |
19 posts held, back to 23 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 18 September 2026. An engagement rate over an empty window would be a number about nothing.
131 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 33.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 44 | 33.6% | |
| custom 5980791510717699147 | 34 | 26.0% | |
| custom 5273769288828723641 | 27 | 20.6% | |
| custom 5273893142800638358 | 17 | 13.0% | |
| custom 5220039162056422898 | 9 | 6.87% |
Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 19 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 131 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 23 August 2026 to 18 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Суру Мульк перед сном не забываем.)) От Ибн Мас’уда (да будет доволен им Аллах) сообщается, что посланник Аллаха (мир ему и благословение Аллаха) сказал: «Сура “Власть” является защитой от мучения могилы». Абу аш-Шейх, Абу Ну’айм, Ибн Мардауайх. Хадис достоверный. См. «Сахих аль-джами’» 3643.
❤1custom 52737692888287236411custom 52738931428006383581custom 59807915107176991471
🎶
❤2custom 59807915107176991472custom 52737692888287236411
🤍
custom 59807915107176991472❤1custom 52737692888287236411
— и остаётся внутри тебя то, что не исправить и о чём не рассказать.
custom 52200391620564228985custom 52737692888287236411custom 52738931428006383581
🖇Увереннее всего чувствует себя в мире, среди людей, тот, кто предпочитает тихо и одиноко заниматься своим делом и ограничивает себя узким кругом.
❤4custom 52737692888287236412custom 59807915107176991471
Если Аллах коснётся тебя вредом (бедой, болезнью, бедностью…), то никто, кроме Него, не избавит тебя от этого. Если же Он пожелает одарить тебя благом (здоровьем, богатством, благополучием…), то никто не отвратит (от тебя) Его милости. Он одаряет этим (благом) того из Своих рабов, кого пожелает. Он — Прощающий, Милующий». [10:107].
❤2custom 52737692888287236412custom 59807915107176991472
Photo, posted without a caption
custom 59807915107176991473❤2custom 52737692888287236411
Знай, что польза и вред — лишь во власти Аллаха! 🤩Всевышний сказал:
❤2custom 59807915107176991472custom 52737692888287236411
Photo, posted without a caption
custom 52738931428006383583custom 59807915107176991473custom 52737692888287236412
Как же прекрасно, когда есть такие друзья 🥹💔
custom 59807915107176991474custom 52738931428006383583❤1
бывает, встретишь человека, а он с первого дня тебе — как семья.🤍
❤3custom 52737692888287236413custom 59807915107176991472
🖇
custom 52737692888287236414custom 52738931428006383583custom 59807915107176991471
Showing the 12 most recent of 19 posts we hold for @degchurauylash. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“𝓡𝓸𝓭𝓷𝓸𝓮” (@degchurauylash), 255 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/degchurauylash.
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.