🙌🏻
🔥1,610❤995🥰338❤🔥261👏20

Channel
@AWengallbi
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Citations · Cite this entry
1,008,527subscribers
-2,657 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001554059403 |
|---|---|
| Type | Channel |
| Username | @AWengallbi |
| Description | По рекламе: @pr_wengallbi |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/AWengallbi |
Automotive — 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 14 August 2026 and assigned it the closest of 31 fixed categories, at 87% 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.
On 20 of the 23 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0109 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /105410 Sept 2026, 20:40 UTC | 32 minutes | 14,000 → 16,300at least +2,200 | 202 → 207at most +6 | +24.1 |
| /105410 Sept 2026, 20:40 UTC | 59 minutes | 18,700 → 23,100at least +4,300 | 214 → 220at most +7 | +47.0 |
| /105410 Sept 2026, 20:40 UTC | 69 minutes | 23,100 → 31,200at least +8,000 | 220 → 228at most +9 | +87.5 |
| /105410 Sept 2026, 20:40 UTC | 59 minutes | 31,200 → 39,300at least +8,000 | 228 → 242at most +15 | +87.5 |
| /105410 Sept 2026, 20:40 UTC | 53 minutes | 39,300 → 48,100at least +8,700 | 242 → 257at most +16 | +95.1 |
| /102728 Aug 2026, 17:24 UTC | 64 minutes | 64,000 → 81,400at least +17,300 | 955 → 958at most +4 | +189.2 |
| /102728 Aug 2026, 17:24 UTC | 66 minutes | 81,400 → 131,000at least +48,600 | 958 → 962at most +5 | +531.4 |
| /102728 Aug 2026, 17:24 UTC | 63 minutes | 140,000 → 162,000at least +21,000 | 966 → 969at most +4 | +229.6 |
| /102728 Aug 2026, 17:24 UTC | 61 minutes | 175,000 → 210,000at least +34,000 | 1,009 → 1,011at most +12 | +371.8 |
| /10312 Sept 2026, 13:33 UTC | 33 minutes | 46,800 → 72,100at least +25,200 | 2,180 → 2,210at most +40 | +275.6 |
| /10312 Sept 2026, 13:33 UTC | 51 minutes | 77,700 → 111,000at least +32,300 | 2,281 → 2,325at most +54 | +353.2 |
| /10312 Sept 2026, 13:33 UTC | 69 minutes | 111,000 → 140,000at least +28,000 | 2,325 → 2,379at most +64 | +306.2 |
| /10312 Sept 2026, 13:33 UTC | 65 minutes | 178,000 → 237,000at least +58,000 | 3,301 → 3,301at most +10 | +634.2 |
| /102628 Aug 2026, 16:43 UTC | 64 minutes | 75,300 → 94,800at least +19,400 | 1,108 → 1,118at most +20 | +212.1 |
| /102628 Aug 2026, 16:43 UTC | 66 minutes | 94,800 → 132,000at least +36,200 | 1,118 → 1,123at most +15 | +395.8 |
| /102628 Aug 2026, 16:43 UTC | 64 minutes | 178,000 → 246,000at least +67,000 | 1,168 → 1,171at most +13 | +732.6 |
| /10445 Sept 2026, 15:56 UTC | 36 minutes | 84,000 → 124,000at least +39,000 | 1,841 → 1,847at most +16 | +426.5 |
| /10445 Sept 2026, 15:56 UTC | 81 minutes | 126,000 → 148,000at least +21,000 | 1,862 → 1,876at most +24 | +229.6 |
| /10445 Sept 2026, 15:56 UTC | 60 minutes | 161,000 → 192,000at least +30,000 | 1,919 → 1,938at most +29 | +328.0 |
| /10455 Sept 2026, 18:58 UTC | 60 minutes | 124,000 → 157,000at least +32,000 | 3,116 → 3,186at most +80 | +349.9 |
| /10455 Sept 2026, 18:58 UTC | 60 minutes | 171,000 → 210,000at least +38,000 | 3,587 → 3,599at most +22 | +415.5 |
| /10455 Sept 2026, 18:58 UTC | 60 minutes | 236,000 → 273,000at least +36,000 | 3,952 → 3,962at most +20 | +393.7 |
| /10488 Sept 2026, 17:14 UTC | 66 minutes | 57,600 → 88,600at least +30,900 | 849 → 927at most +79 | +337.9 |
| /10488 Sept 2026, 17:14 UTC | 60 minutes | 96,000 → 167,000at least +70,000 | 950 → 953at most +4 | +765.4 |
| /10488 Sept 2026, 17:14 UTC | 63 minutes | 177,000 → 208,000at least +30,000 | 1,005 → 1,008at most +13 | +328.0 |
| /102026 Aug 2026, 17:47 UTC | 48 minutes | 58,000 → 67,800at least +9,700 | 1,467 → 1,479at most +22 | +106.1 |
| /102026 Aug 2026, 17:47 UTC | 2.1 hours | 150,000 → 185,000at least +34,000 | 3,014 → 3,027at most +23 | +371.8 |
| /102428 Aug 2026, 16:24 UTC | 64 minutes | 79,100 → 105,000at least +24,900 | 1,083 → 1,091at most +18 | +272.3 |
| /102428 Aug 2026, 16:24 UTC | 66 minutes | 105,000 → 138,000at least +32,000 | 1,091 → 1,098at most +17 | +349.9 |
| /10392 Sept 2026, 13:59 UTC | 65 minutes | 165,000 → 203,000at least +37,000 | 3,208 → 3,219at most +21 | +404.6 |
| /10392 Sept 2026, 13:59 UTC | 45 minutes | 223,000 → 266,000at least +42,000 | 3,354 → 3,356at most +12 | +459.3 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the key view_reaction_decoupling, last confirmed 11 September 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 |
|---|---|---|
| 10 Sept 2026, 18:39 | 1,008,527 | +1,299 |
| 7 Sept 2026, 19:15 | 1,007,228 | -2,103 |
| 4 Sept 2026, 18:41 | 1,009,331 | -4,676 |
| 3 Sept 2026, 07:36 | 1,014,007 | +11,393 |
| 2 Sept 2026, 01:27 | 1,002,614 | -11,798 |
| 1 Sept 2026, 03:14 | 1,014,412 | -829 |
| 31 Aug 2026, 01:33 | 1,015,241 | +2,508 |
| 29 Aug 2026, 23:44 | 1,012,733 | +3,002 |
| 29 Aug 2026, 02:12 | 1,009,731 | -316 |
| 28 Aug 2026, 02:24 | 1,010,047 | -6,124 |
| 27 Aug 2026, 00:09 | 1,016,171 | -3,087 |
| 25 Aug 2026, 22:44 | 1,019,258 | -3,631 |
| 24 Aug 2026, 21:59 | 1,022,889 | -35,612 |
| 23 Aug 2026, 07:53 | 1,058,501 | +7,971 |
| 21 Aug 2026, 18:54 | 1,050,530 | +19,461 |
| 20 Aug 2026, 12:26 | 1,031,069 | +36,160 |
| 19 Aug 2026, 10:35 | 994,909 | -12,088 |
| 18 Aug 2026, 09:16 | 1,006,997 | -3,197 |
| 17 Aug 2026, 09:38 | 1,010,194 | +326 |
| 15 Aug 2026, 19:07 | 1,009,868 | first reading |
32 posts held, back to 13 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 58 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 10 September 2026 |
|---|---|
| Posts held | 32 (13 August 2026 – 10 September 2026) |
| Views total | 10,098,000 |
| Reactions total | 111,606 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Sept 2026, 13:06 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 11 September 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.
Measured directly from 1 video 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 23 of this channel’s own posts over the last 30 days: across 18 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 19 hours of being posted; a typical post has already reached 25.5% of its 24-hour view count within the first hour, and 44.6% within the first six; the median 24-hour reach across those posts is 195,000 views — 18.4% of this channel’s own subscriber count (90th percentile 214,300).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /105510 Sept 2026, 21:40 UTC | 1932 minutes – 15 hours old | 210,000 views ~3,224 reactions | 60 minutes: 12,012 interp. → 3.0 hours: 38,300 → 6.0 hours: 63,500 → 12 hours: 130,000still climbing at last reading | not yet at 24h | 11 hoursprovisional — final view count still climbing |
| /105410 Sept 2026, 20:40 UTC | 2035 minutes – 16 hours old | 199,000 views ~363 reactions | 60 minutes: 9,292 interp. → 3.0 hours: 18,700 → 6.0 hours: 39,300 → 12 hours: 86,900still climbing at last reading | not yet at 24h | 13 hoursprovisional — final view count still climbing |
| /105310 Sept 2026, 18:39 UTC | 2333 minutes – 18 hours old | 200,000 views ~1,092 reactions | 60 minutes: 40,847 interp. → 3.0 hours: 51,014 interp. → 6.0 hours: 97,300 → 12 hours: 117,000still climbing at last reading | not yet at 24h | 6.9 hoursprovisional — final view count still climbing |
| /105210 Sept 2026, 16:58 UTC | 264 minutes – 20 hours old | 201,000 views ~2,285 reactions | 60 minutes: 48,307 interp. → 3.0 hours: 82,253 interp. → 6.0 hours: 90,600 → 12 hours: 138,000still climbing at last reading | not yet at 24h | 7.0 hoursprovisional — final view count still climbing |
| /105110 Sept 2026, 16:58 UTC | 265 minutes – 20 hours old | 208,000 views ~3,323 reactions | 60 minutes: 48,920 interp. → 3.0 hours: 86,634 interp. → 6.0 hours: 94,800 → 12 hours: 142,000still climbing at last reading | not yet at 24h | 7.0 hoursprovisional — final view count still climbing |
| /10508 Sept 2026, 19:08 UTC | 6863 minutes – 3 days old | 312,000 views ~7,462 reactions | 3.0 hours: 50,700 → 6.0 hours: 152,000 → 12 hours: 162,000 → 24 hours: 203,000 → 2 days: 297,000views have flattened out | 203,000measured | 8.8 hours |
| /10488 Sept 2026, 17:14 UTC | 4847 minutes – 2 days old | 277,000 views ~1,090 reactions | 60 minutes: 53,471 interp. → 3.0 hours: 88,600 → 6.0 hours: 96,000 → 12 hours: 172,000 → 24 hours: 213,000 → 2 days: 273,000still climbing at last reading | 213,000measured | 6.6 hours |
| /10478 Sept 2026, 15:52 UTC | 6930 minutes – 3 days old | 322,000 views ~3,521 reactions | 60 minutes: 57,833 interp. → 3.0 hours: 101,536 interp. → 6.0 hours: 113,000 → 12 hours: 187,000 → 24 hours: 245,000 → 2 days: 307,000still climbing at last reading | 245,000measured | 8.1 hours |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
111,606 reactions across 32 posts, in 23 distinct kinds. The most used accounts for 50.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 56,843 | 50.9% | |
| 🔥 | 18,916 | 16.9% | |
| ❤🔥 | 10,725 | 9.61% | |
| 👍 | 7,954 | 7.13% | |
| 🥰 | 5,713 | 5.12% | |
| 👏 | 2,410 | 2.16% | |
| 😱 | 1,600 | 1.43% | |
| 🕊 | 1,294 | 1.16% | |
| 😢 | 1,256 | 1.13% | |
| 🤩 | 857 | 0.768% | |
| 😍 | 799 | 0.716% | |
| 💔 | 723 | 0.648% | |
| 👀 | 630 | 0.564% | |
| 😁 | 546 | 0.489% | |
| 💯 | 287 | 0.257% | |
| 🤝 | 249 | 0.223% | |
| 😎 | 241 | 0.216% | |
| 🙏 | 232 | 0.208% | |
| 🍌 | 194 | 0.174% | |
| ⚡ | 44 | 0.039% | |
| 3 further kinds | 93 | 0.083% |
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 32 of the 32 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 111,606 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 13 August 2026 to 10 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @AWengallbi. 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 32 most recent posts we hold for this entry, published 13 August 2026 to 10 September 2026. 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.
🙌🏻
🔥1,610❤995🥰338❤🔥261👏20
👉 ЛOBИ 2 ДHЯ БECПЛATHOГO VPN 🎁
❤200👍56🤩50🔥37🤝20
Блин, опять впн не работает... Знакомо?) А мне с этим впном нет🙃 📡 Обходки глушилок и белых списков 🌎 Разные локации 💻 Бесконечное количество устройств 🌐 Безлимит на трафик(обходки тоже безлимит) 💛 SAVE VPN — ЛУЧШИЙ ВПН! Попробуй бесплатно👇
❤1,020🍌31😢19💔15😁7
Красивая была 😏, а сзади легенда.
❤1,250🔥421🥰307💯273🕊34
2021, зима, нива броня )
🔥1,290❤🔥1,090❤913🕊21👏9
Video message, posted without a caption
🔥3,110❤🔥1,380❤1,220👏889👍863
Свежее фото )
❤🔥2,110❤812🥰448🔥113👍38
Это когда только Ахмед купил ее, в итоге через несколько лет на ней его остановили ГАИ, и он сел в тюрьму ☹️
❤2,590👍895😢495❤🔥112💯14
Video message, posted without a caption
❤1,220🔥493👍443😁47❤🔥24
Если тебе нужна новая аудитория в телеграме и толчок в продвижении, то эта информация для тебя 🤝 Прямо сейчас мы закрываем последние спонсорские места в гив! Дарить будем новые 18 АЙФОНЫ!🔥 🔝ГАРАНТ:от 30 000 подписчиков В прошлом гиве заявленный гарант мы перевыполнили уже в первые сутки! Каждый день на протяжении гива будут проходить активности на вовлечение аудитории, чтобы новые подписчики не просто пришли, а ус…
❤846🔥383👍340❤🔥18😁6
😲
❤2,010❤🔥1,310🥰1,150🤝229👍58
Когда Ахмед только сел, один его «товарищ» написал ему в письме: «Брат, жалко, конечно… Ты сел в тюрьму на самом пике своей карьеры. Второго такого пика у тебя уже не будет». Прошло уже немало времени, а Ахмед эту фразу помнит дословно 😄 И каждый раз говорит: «Это мы ещё посмотрим, у кого будет второй пик, а у кого - нет». Скоро эта фраза ещё очень красиво вернётся к своему автору)) Мы в ожидании…
❤4,370❤🔥482🔥413🙏232💔87
Showing the 12 most recent of 32 posts we hold for @AWengallbi. 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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“WENGALLBI” (@AWengallbi), 1,008,527 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/AWengallbi.
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.