Channel
@XayrliKunlar
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
30,803subscribers
-53 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001467442952 |
|---|---|
| Type | Channel |
| Username | @XayrliKunlar |
| Description | Ассалому алейкум Бу ерда сиз кунлик табриклардан бахраманд бўласиз🌸☺️ Биздан узоқлашманг🤗 Реклама учун:👉 @Tabobatadmin |
| Created | 2 July 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/XayrliKunlar |
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 10 August 2026 and assigned it the closest of 31 fixed categories, at 69% 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.
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 |
|---|---|---|---|
| @XayrliKunlar/13282 · this entry27 Jul 2026, 23:27 UTC | @juma_tabriklari_muborak/1012627 Jul 2026, 23:27 UTC | 1.00 | under a minute |
| @XayrliKunlar/13283 · this entry28 Jul 2026, 01:29 UTC | @juma_tabriklari_muborak/1012728 Jul 2026, 01:29 UTC | 1.00 | under a minute |
| @XayrliKunlar/13284 · this entry28 Jul 2026, 23:19 UTC | @juma_tabriklari_muborak/1012928 Jul 2026, 23:19 UTC | 1.00 | under a minute |
| @XayrliKunlar/13286 · this entry30 Jul 2026, 01:29 UTC | @juma_tabriklari_muborak/1013230 Jul 2026, 01:29 UTC | 1.00 | under a minute |
| @XayrliKunlar/13288 · this entry30 Jul 2026, 23:29 UTC | @juma_tabriklari_muborak/1013530 Jul 2026, 23:29 UTC | 1.00 | under a minute |
| @XayrliKunlar/13296 · this entry3 Aug 2026, 23:29 UTC | @juma_tabriklari_muborak/101473 Aug 2026, 23:29 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @juma_tabriklari_muborak | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @juma_tabriklari_muborak (17–1) |
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. 2 of the 17 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 22 comparable posts for this entry, running 27 July 2026 to 7 August 2026. 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 @juma_tabriklari_muborak. That is a statement about our reading window, not a claim of authorship.
79,600 average views per post against 30,747 subscribers — an engagement rate of 258.9%. Across the 580 registered channels in the same cohort — 10,078–31,578 subscribers, posting mainly in Belarusian — the middle half sit between 7.25% and 28.7%, with a median of 15.3%.
| Window | 30 days (6 October 2026 – 5 November 2026) |
|---|---|
| Posts measured | 55 of 55 published in the window (0 exact, 55 rounded by Telegram) |
| Views totalled | 4,378,300 |
| Mature posts only | 259.8% over 54 posts read at least 24h after publication |
| Subscribers | 30,747 measured 5 November 2026 |
| Cohort | b10000:bel · 580 channels · p10 3.14% · p25 7.25% · p50 15.3% · p75 28.7% · p90 53.1% |
| Position in cohort | 99.827th percentile · 17.0× the cohort median |
| Uncertainty | ±0.097% of the figure, from Telegram’s rounding |
| Post language | Belarusian · 96.3% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the keys clone_copy · err_high, last confirmed 5 November 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 |
|---|---|---|
| 7 Nov 2026, 02:08 | 30,803 | +25 |
| 5 Nov 2026, 23:16 | 30,778 | +31 |
| 5 Nov 2026, 00:19 | 30,747 | -20 |
| 3 Nov 2026, 23:37 | 30,767 | -8 |
| 3 Nov 2026, 01:46 | 30,775 | -9 |
| 2 Nov 2026, 04:08 | 30,784 | -27 |
| 1 Nov 2026, 04:30 | 30,811 | -46 |
| 31 Oct 2026, 02:50 | 30,857 | +11 |
| 30 Oct 2026, 00:59 | 30,846 | +3 |
| 28 Oct 2026, 23:09 | 30,843 | -12 |
| 27 Oct 2026, 23:49 | 30,855 | -3 |
| 27 Oct 2026, 00:38 | 30,858 | +11 |
| 25 Oct 2026, 22:50 | 30,847 | -19 |
| 24 Oct 2026, 21:19 | 30,866 | -21 |
| 23 Oct 2026, 02:37 | 30,887 | +15 |
| 22 Oct 2026, 03:16 | 30,872 | +30 |
| 20 Oct 2026, 21:01 | 30,842 | +4 |
| 18 Oct 2026, 19:07 | 30,838 | -6 |
| 17 Oct 2026, 18:48 | 30,844 | +8 |
| 16 Oct 2026, 15:16 | 30,836 | first reading |
220 posts held, back to 27 July 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 159 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 220 (27 July 2026 – 7 November 2026) |
| Views total | 4,147,320 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 22:59 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 7 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 211 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Telegram’s own ‘edited’ marker: 0 of 54 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
☀️ ХАЙРЛИ ТОНГ! 🌱 Ассалому алайкум! Шанба тонги муборак бўлсин! Бугунги бошланаётган янги кунингиз файзли ва барокатли бўлсин! Сиз ва яқинларингизни яхши кайфият асло тарк этмасин! 👉 @Xayrlikunlar
🇺🇿 ЎЗБЕКИСТОН Ҳалқ табобати ассотсиатсияси Аъзоси Мухиддин Табиб қуйидаги ўз #хизматларини таклиф қилади❗️ ✅ Ревматизм ✅ Полиартрит ✅ Остеохондроз ✅ Грижа ✅ Оёқ оғриши ✅ Оёқ совуқотиши ✅ Уйқусизлик ✅ Варикоз ✅ Гайморит ✅ Эпилепсия ✅ Простата ✅ Тумов Йўтал ✅ Ичак касаллиги ✅ Ўпка ✅ Юрак ✅ Буйрак Ўт ✅ Ошқозон ✅ Геморрой ✅ Семизлик ✅ Қон босими ✅ Тошмалар ✅ Псориаз ✅ Қулоқ шанғиллаши ✅ ЗОБ ✅ Кўриш кучи пастлиги ✅ Имму…
#ХАЙРЛИ_ТОНГ 🌤🍋Aссалому алайкум. Шанба тонги муборак бўлсин! 💛 Сизга оилавий хотиржамлик, тани соғлик, хайрли амалларга тўла ва дуолар мустажоб бўлувчи лаҳзаларга бой яна жуда кўп субҳи содиқлар тилаймиз. 🩷Янги кунингиз файзли ва барокатли ўтсин 🤲Барчамизга кавсар сувларидан ичишлик насиб қилсин! 👉 @XayrliKunlar
#ЖУМА_МУБОРАК ✨Азиз яқиним муборак Жуманинг файзи барокати сизга бўлсин 🌙Энг яқин инсоним кириб келган “Жума” куни муборак бўлсин. ЯҚИНЛАРИНГИЗНИ БИРИНЧИЛАРДАН БЎЛИБ ТАБРИКЛАНГ 👉 @XayrliKunlar
🕋 Umraga borish endi yanada qulay! Safar Travel sizga davomiyligi, narxi va qulayliklari bilan farqlanuvchi Umra paketlarini taklif etadi. Safar davomida siz uchun: ✈️ Qulay aviaqatnovlar va transfer xizmatlari 👥 Tajribali guruh rahbarlari hamrohligi 🩺 Madina va Makkada shifokorlar xizmati 📞 Batafsil ma’lumot uchun: +998 78 150 22 66 +998 78 555 22 66
#Жума_Муборак Ассалому алайкум • "Ж" онингиз соғ, • "У" мрингиз узоқ • "М" артабангиз улуғ • "А" йёмингиз қутлуғ бўлсин 🌙 Жума айёмингиз муборак бўлсин! 👉 @Xayrlikunlar Уланинг☑️ 👉 https://t.me/joinchat/bqb1CGbAzuM4OWEy
#Жума_муборак 🌸💫🍃ЖУМА МУБОРАК!🍃💫🌸 🌙 Энг яқин инсоним, ЖУМА муборак бўлсин!🤲 Бугун шундай Жума бўлсинки: Афв этилмаган БАНДА; Қабул бўлмаган ДУО; Даф бўлмаган БАЛО; Шифо топмаган ХАСТА; Ҳузур топмаган ҚАЛБ; АЛЛОҲ демаган ТИЛ қолмасин! Қадрдонларни биринчилардан бўлиб табрикланг🤲👇 👉 @XayrliKunlar
🍂 ХАЙРЛИ ТОНГ! 🍂 Ассалому алайкум! Пайшанба тонги муборак бўлсин! Бугунги бошланаётган янги кунингиз файзли ва барокатли бўлсин! Сиз ва яқинларингизни яхши кайфият асло тарк этмасин! 👉 @XayrliKunlar
🍂 ХАЙРЛИ ТОНГ! 🍂 Ассалому алайкум! Чоршанба тонги муборак бўлсин! Бугунги бошланаётган янги кунингиз файзли ва барокатли бўлсин! Сиз ва яқинларингизни яхши кайфият асло тарк этмасин! 👉 @XayrliKunlar
#Хайрли_тонг 🌧 Ассалому алайкум! Сешанба тонги муборак бўлсин Бугунги бошланаётган янги кунингиз файзли ва барокатли бўлсин! Сиз ва яқинларингизни яхши кайфият тарк этмасин! 👉 @XayrliKunlar
#ХАЙРЛИ_ТОНГ ☀️ 🌱 Aссалому алайкум. Душанба куни муборак бўлсин 😊 Соғ–саломат уйғотган Роббимизга ҳамдлар бўлсин! Бошланган янги кун барчага омадли келсин! @Xayrlikunlar ☑️ 👉 https://t.me/joinchat/bqb1CGbAzuM4OWEy
#Хайрли_тонг ☀️ Ассалому алайкум! Якшанба тонги муборак бўлсин🤗 Бугунги бошланаётган янги кунингиз файзли ва барокатли бўлсин! Сиз ва яқинларингизни яхши кайфият тарк этмасин! Яқинларни янги тонг билан соғ-саломат уйғонгани билан табрикланг. @Xayrlikunlar ☑️ 👉 https://t.me/joinchat/bqb1CGbAzuM4OWEy
Showing the 12 most recent of 220 posts we hold for @XayrliKunlar. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 33 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Хайрли Тонг 💐 Xayrli Tong” (@XayrliKunlar), 30,803 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/XayrliKunlar.
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.