Channel
@Ucell_Dealer
On this record: Topic · Observations · Growth · Engagement · Posts · Citations · Cite this entry
3,379subscribers
+24 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001173821102 |
|---|---|
| Type | Channel |
| Username | @Ucell_Dealer |
| Created | Between 1 March 2018 and 30 June 2021— 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 | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/Ucell_Dealer |
Other / unclassifiable — 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 98% 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.
4,840 average views per post against 3,379 subscribers — an engagement rate of 143.2%. Across the 40,483 registered channels in the same cohort — 3,163–9,999 subscribers, posting mainly in Russian — the middle half sit between 7.15% and 26.5%, with a median of 14.2%.
| Window | 30 days (13 July 2026 – 12 August 2026) |
|---|---|
| Posts measured | 20 of 20 published in the window (0 exact, 20 rounded by Telegram) |
| Views totalled | 96,750 |
| Mature posts only | 169.8% over 15 posts read at least 24h after publication |
| Subscribers | 3,379 measured 11 August 2026 |
| Cohort | b3162:rus · 40,483 channels · p10 3.46% · p25 7.15% · p50 14.2% · p75 26.5% · p90 43.8% |
| Position in cohort | 99.575th percentile · 10.1× the cohort median |
| Uncertainty | ±0.101% of the figure, from Telegram’s rounding |
| Post language | Russian · 100.0%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 key err_high, last confirmed 12 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 13:16 | 3,379 | +24 |
| 7 Aug 2026, 17:02 | 3,355 | no change |
| 7 Aug 2026, 16:52 | 3,355 | first reading |
20 posts held, back to 21 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 2 pagesof 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 August 2026 |
|---|---|
| Posts held | 20 (21 July 2026 – 7 August 2026) |
| Views total | 96,750 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:26 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.
Уважаемые дилеры! Сообщаем, что в ночь с 8 августа на 9 августа 2026 года, с 02:00 до 05:00, в системе будут проводиться плановые технические работы. В указанный период возможны временные перебои в работе системы DCRM и мобильного приложения USIM. Во время перебоев в работе систем USIM и DCRM просим вас пользоваться системой SBMS. Приносим извинения за возможные неудобства и благодарим за понимание!
Hurmatli dilerlar! Sizga shuni ma’lum qilamizki, 2026-yil 8-avgustdan 9-avgustga o‘tar kechasi, soat 02:00 dan 05:00 gacha, tizimda rejalashtirilgan texnik ishlar olib boriladi. Ushbu vaqt oralig‘ida DCRM, USIM mobil ilovasi ishlashida vaqtinchalik uzilishlar kuzatilishi mumkin. USIM va DCRM tizimlarida uzilishlar yuzaga kelgan vaqtda, SBMS tizimidan foydalanishingizni so‘raymiz. Keltirilishi mumkin bo‘lgan noqul…
Уважаемые дилеры! Сообщаем, что в ночь с 8 августа на 9 августа 2026 года, с 02:00 до 05:00, в системе будут проводиться плановые технические работы. В указанный период возможны временные перебои в работе системы DCRM и мобильного приложения USIM. Во время перебоев в работе систем USIM и DCRM просим вас пользоваться системой SBMS. Приносим извинения за возможные неудобства и благодарим за понимание!
Hurmatli dilerlar! Sizga shuni ma’lum qilamizki, 2026-yil 8-avgustdan 9-avgustga o‘tar kechasi, soat 02:00 dan 05:00 gacha, tizimda rejalashtirilgan texnik ishlar olib boriladi. Ushbu vaqt oralig‘ida DCRM, USIM mobil ilovasi ishlashida vaqtinchalik uzilishlar kuzatilishi mumkin. USIM va DCRM tizimlarida uzilishlar yuzaga kelgan vaqtda, SBMS tizimidan foydalanishingizni so‘raymiz. Keltirilishi mumkin bo‘lgan noqul…
👉 09:30 dan keyin, после 09:30👈
⚠️ HURMATLI DILERLAR! (MUHIM!!! 2026-yilning Iyul oyi mukofot puli) Sizga shuni ma’lum qilamizki, 2026-yil 4-avgust kuni, 2026-yilning Iyul oyi uchun mukofot puli haqidagi ma’lumotnoma Faktura.uz tizimiga yuklandi. Iltimos, ko’rsatilgan xizmatlar haqida ma’lumotnomani qabul qiling va ushbu ma’lumotnoma asosida hisob-varaqasini yarating. So’ng o’zingizni elektron raqamli imzoingizni qo’yib, biz…
👉16:45 dan keyin, после 16:45👈
👉10:15 dan keyin, после 10:15👈
Уважаемые дилеры! В связи с проведением технических работ в базе данных и в биллинговой системе Компании Mobiuz, операции по переносу номеров (MNP) как из Компании Mobiuz, так и в Компанию Mobiuz будут недоступны в период с 31.07.2026 17:30 до 01.08.2026 10:10. В связи с вышеизложенным, просим вас временно не открывать заявки на перенос абонентов из Компании Mobiuz. Спасибо за понимание!
Hurmatli dilerlar! Mobiuz kompaniyasining ma’lumotlar bazasi va billing tizimida texnik ishlar olib borilishi munosabati bilan 31.07.2026 17:30 dan 01.08.2026 10:10 gacha Mobiuz kompaniyasidan ham, Mobiuz kompaniyasiga ham raqamlarni ko‘chirish (MNP) operatsiyalari mavjud bo‘lmaydi. Yuqoridagilardan kelib chiqib, sizdan Mobiuz kompaniyasidan abonentlarni ko‘chirish uchun arizalarni vaqtincha ochmasligingizni so‘ray…
👉10:00 dan keyin, после 10:00👈
👉10:00 dan keyin, после 10:00👈
Showing the 12 most recent of 20 posts we hold for @Ucell_Dealer. 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.
Citation-graph rank — 192,247 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Ucell Dealer Info” (@Ucell_Dealer), 3,379 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Ucell_Dealer.
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.