Channel
@a303ss
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
5,864subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002163125524 |
|---|---|
| Type | Channel |
| Username | @a303ss |
| Description | Услада для ушей) Связь: @Mirotvorec07 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/a303ss |
Religion — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 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 why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @algaribaaa/284928 Jun 2025, 16:31 UTC | @a303ss/7722 · this entry28 Jun 2025, 16:31 UTC | 1.00 | under a minute |
| @a303ss/7723 · this entry1 Jul 2025, 18:44 UTC | @algaribaaa/28511 Jul 2025, 18:44 UTC | 1.00 | under a minute |
| @a303ss/7724 · this entry1 Jul 2025, 18:44 UTC | @algaribaaa/28521 Jul 2025, 18:44 UTC | 1.00 | under a minute |
| @algaribaaa/28606 Jul 2025, 19:36 UTC | @a303ss/7732 · this entry6 Jul 2025, 19:36 UTC | 1.00 | under a minute |
| @algaribaaa/28617 Jul 2025, 20:46 UTC | @a303ss/7733 · this entry7 Jul 2025, 20:46 UTC | 1.00 | under a minute |
| @algaribaaa/28627 Jul 2025, 20:46 UTC | @a303ss/7734 · this entry7 Jul 2025, 20:46 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @algaribaaa | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 27 June 2025 to 1 August 2025. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @algaribaaa. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 10:22 | 5,864 | -8 |
| 8 Aug 2026, 11:05 | 5,872 | -3 |
| 7 Aug 2026, 14:01 | 5,875 | no change |
| 7 Aug 2026, 13:58 | 5,875 | first reading |
20 posts held, back to 27 June 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof 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 20 posts for this entry, the most recent from 1 August 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
528 reactions across 20 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5222430857544880066 | 528 | 100.0% |
Custom emoji. One row above is a 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 count beside it isTelegram’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 20 of the 20 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 528reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 27 June 2025 to 1 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @a303ss. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 27 June 2025 to 1 August 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
сегодня пятница, приумножьте же салават на нашего Пророка (ﷺ) ٱللَّٰهُمَّ صَلِّ عَلَىٰ مُحَمَّدٍ وَعَلَىٰ آلِ مُحَمَّدٍ وَسَلِّم «Аллаهумма салли 'аля Мухаммадин ва 'аля али Мухаммад».»
custom 522243085754488006681
👥 : что же сделать❓у меня вообще нет настроение … 👤 : в любом положении , как бы тебе плохо не было , беги к الله.. ибо Он — твой Творец , и знает о каждой проблеме.
custom 522243085754488006659
وسوف يجتمع عندما كنت لا تتوقع. ولن تجده في المكان الذي تبحث عنه. И встретишь ты, когда не ждёшь. И обретешь не там, где ищешь.
custom 522243085754488006649
Женщина, в доме которой он жил, стала соблазнять его, заперла двери и сказала: «Иди ко мне». Он сказал: «Упаси Аллах! Ведь он — мой господин, обеспечивший мне прекрасную жизнь. Воистину, беззаконники не преуспеют». 12:23
custom 522243085754488006627
Если Мои рабы спросят тебя обо Мне, то ведь Я близок и отвечаю на зов молящегося, когда он взывает ко Мне. Пусть же они отвечают Мне и веруют в Меня, — быть может, они последуют верным путем. 2:186
custom 522243085754488006636
Quran 6:95-98 Таков Аллах! До чего же вы отвращены от истины! Он раскрывает утреннюю зарю. Он предназначил ночь для покоя, а солнце и луну — для исчисления. Таково установление Могущественного, Знающего.Он — Тот, Кто сотворил для вас звезды, чтобы вы находили по ним путь во мраках суши и моря. Мы уже разъяснили знамения для людей знающих. Он — Тот, Кто сотворил вас из одной души.
custom 522243085754488006617
👥 : что же сделать❓у меня вообще нет настроение … 👤 : в любом положении , как бы тебе плохо не было , беги к الله.. ибо Он — твой Творец , и знает о каждой проблеме.
custom 522243085754488006615
👥: ты изменился внутренне. что так исцелило тебя? 👤: лекарем недугов моего сердца была речь Аллаха.
custom 522243085754488006617
وسوف يجتمع عندما كنت لا تتوقع. ولن تجده في المكان الذي تبحث عنه. И встретишь ты, когда не ждёшь. И обретешь не там, где ищешь.
custom 522243085754488006627
👥: где можно найти счастье в этом мире? 👤: ночью. коврик для намаза. ты и Аллах. настоящее счастье начинается здесь.
custom 522243085754488006618
👥 : у меня слишком много грехов.. 👤всевышний в Къур’ане: قال إِنَّهُ كَانَ تَوَّابًا воистину , Он — принимающий покаяния.
custom 522243085754488006620
Напоминай же! По милости своего Господа ты не являешься ни прорицателем, ни одержимым. 52:29
custom 522243085754488006617
Showing the 12 most recent of 20 posts we hold for @a303ss. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 626,610 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“yasov” (@a303ss), 5,864 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/a303ss.
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.