Channel
@dentenobots
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
660subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002426218099 |
|---|---|
| Type | Channel |
| Username | @dentenobots |
| Description | кормлю підписників лайном і не соромлюсь цього |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/dentenobots |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 02:35 | 660 | no change |
| 8 Aug 2026, 00:23 | 660 | -1 |
| 7 Aug 2026, 15:55 | 661 | first reading |
20 posts held, back to 2 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 pageof 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 (2 August 2026 – 7 August 2026) |
| Views total | 6,721 |
| Reactions total | 276 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 02:35 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 8 August 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 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.
276 reactions across 20 posts, in 16 distinct kinds. The most used accounts for 25.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 70 | 25.4% | |
| ❤ | 67 | 24.3% | |
| 🤣 | 43 | 15.6% | |
| custom 5285264489623600732 | 24 | 8.70% | |
| 🤯 | 21 | 7.61% | |
| custom 5211054459840379292 | 12 | 4.35% | |
| 🆒 | 11 | 3.99% | |
| 😱 | 8 | 2.90% | |
| custom 5253682014548145559 | 6 | 2.17% | |
| 🔥 | 4 | 1.45% | |
| custom 5269521334244745298 | 2 | 0.725% | |
| custom 5850233013249510652 | 2 | 0.725% | |
| 👎 | 2 | 0.725% | |
| 🤡 | 2 | 0.725% | |
| 🍓 | 1 | 0.362% | |
| 🗿 | 1 | 0.362% |
Custom emoji. 5 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 areTelegram’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 276reactions 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 2 August 2026 to 7 August 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.
За цей рік вони вже встигли скасувати 2 турніри, двічі перенести FiReCONTER 4 та раз перенести FiReCONTER 5 + перенести FiReBATTLE ще до анонсу
custom 52852644896236007326custom 58502330132495106522
Signed denten
До FiReLEAGUE Major лишився майже рік, а організатори вже мене бісять тим, що не можуть опублікувати деталі реєстрації для турніру, який проходитиме менше, ніж через місяць 🤪 Мужики, ви турнір на 50к провести нормально не можете й досі не можете анонсувати деталі після ДВОХ ПЕРЕНОСІВ СУКА, який вам мейджор?
🤣9
Signed denten
Незвично якось бачити rain без окулярів
❤12🍓1
Signed denten
Найкращий хайлайт моєї кіберспортивної кар'єри 😍
❤11🔥1🤡1😁1custom 52852644896236007321
Signed denten
Аж 14 українських команд наразі знаходяться в рейтингу Valve
🆒11❤2
Signed denten
Цього сезону повертаю собі мінімум 4 LVL, до речі
custom 528526448962360073211custom 52110544598403792922
Signed denten
Китайська мафія, не вбивайте мене за цей пост
🤣18custom 52110544598403792921
Signed denten
🇨🇳 19-річний YINXING, який протягом останніх двох років займається проведенням турнірів для свого рідного китайського регіону, заявив про чиїсь спроби перешкодити організації його найближчого турніру — YINXING Future Star Festival. За його словами, це вже не перший такий прецедент — протягом минулого року організатори мінімум трьох запланованих рейтингових tier-2 турніри в Китаї зіткнулися з різними перешкодами, ств…
custom 52852644896236007326❤1custom 52536820145481455591
Signed denten
Ахуєнні нікнейми у людей на KICK АдольфZ
😁27🗿1
Signed denten
зловили ментальний зв'язок
❤12custom 52695213342447452981
Signed denten
Але не здивуюся, якщо вони виграють Бласт з Юстіком та гарантують цим третій стейдж
custom 52110544598403792922
Signed denten
Насправді, це може сильно підʼєбати Віталіті, якщо вони обісруться на ПГЛ та втратять прямий слот в третю стадію Сингапуру
❤14
Signed denten
Showing the 12 most recent of 20 posts we hold for @dentenobots. 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“дентеноботоферма” (@dentenobots), 660 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/dentenobots.
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.