Channel
@taida_idle
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Declared links · Cite this entry
90subscribers
+2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001662682407 |
|---|---|
| Type | Channel |
| Username | @taida_idle |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/taida_idle |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 02:57 | 90 | +2 |
| 9 Aug 2026, 15:30 | 88 | no change |
| 8 Aug 2026, 11:05 | 88 | first reading |
13 posts held, back to 19 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 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. It is computed over the 11 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 13 (19 July 2026 – 7 August 2026) |
| Views total | 1,656 |
| Reactions total | 42 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 15:30 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.
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.
42 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 64.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5371092341517983825 | 27 | 64.3% | |
| custom 5370594129606614032 | 13 | 31.0% | |
| custom 5370740287343702328 | 2 | 4.76% |
Custom emoji. Every 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 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 11 of the 13 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 42reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 19 July 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.
В случае если у вас какие-то гифтики там не знаю.... 😙 но тгшка еще не придумала уведомлений на упоминания в других каналах, отправляйте их в лс канальчика, я завтра буду с интернетиком (надеюсь(я сейчас сижу с алкашами около сельского магазина)), всех зарепостчу 😙
custom 53707402873437023281
🌟 Сегодня у моего любимого дружбана День рождения. Призываю вас спуститься в комменты и написать пару приятных слов. 😊 #art #digitalart #BlooPo
custom 53705941296066140323custom 53707402873437023281
Я тебя сейчас зацелую бро Я тебя сейчас зацелую
custom 53705941296066140322
Так же информация для тех, кто ждет коммишки Я пропал не потому что я разгилдяй разводила, а потому что уехал на отдых к бести на дачу, а у меня тут не то, что интернета, даже сети нет, мне вот сейчас она раздала, чтобы я отписался об этом и деньрожденный постик сделал Так что как только приеду обратно в город, все всем раздам, но все равно можете меня ссаными тряпками избить если хотите 🤔
custom 53710923415179838253
❌❌🤍🦷🤍 Сегодня мне поставили две двойки 😔 Вашему админу сегодня ударило по голове днем рождением, так чтоооооо жесть 😔 Самый клевый подарок художнику - это репостик его картинок, будет очень приятненько 🌺 Спасибо всем тем, кто следит за мной уже долгое время, и тем, кто нашел меня совсем недавно, я вас всех очень ценю ребятки вы у меня крутые самые 😙 ❌🍡🩹🐰🍡🩹
custom 53710923415179838257
😃ПРОДЛЕНИЕ ПРЕДЗАКАЗОВ И РОЗЫГРЫША! 😈 Хотим сообщить, что в связи с проявленным интересом, а так же предстоящими наикрутейшими дополнениями зина - было принято решение продлить предзаказы, и, закономерно, и розыгрыша! 😏 УСПЕЙТЕ ДО 31 АВГУСТА СДЕЛАТЬ ПРЕДЗАКАЗ! 😏 💖А ДО 10 АВГУСТА - ПОУЧАСТВОВАТЬ В РОЗЫГРЫШЕ!💖 #JSaB_zine #JSaB #JustShapesAndBeats_zine
custom 53705941296066140323
❌🔵🔵🔵 Пока я коплю ульту давайте я вас послушаю вдруг чо интересное у вас про меня придумалось 😋 #interactive
custom 53705941296066140321
Спрос закончился, видимо Закрываю лавочку 👆👆👆 Буду всем отдавать в порядке очереди, всем спасибо за коммишечки и репосты, вы очень меня выручаете 🤲
custom 53710923415179838253
Ребята У меня произошла страшилка пугалка, я остался с голой жопой до конца месяца Поэтому в срочном порядке наберу неограниченное количество слотов такого формата по 500 за персонажа Доп. перс +50% за каждого Фд/ОС без перегрузов по дизайну Фон онли одноцвет/несложный Прочие уточнения лично, я добавлю к посту, если это что-то важное и я забыл Дедлайн в порядке очереди и так же будет уточняться лично, в зависимости …
custom 53710923415179838257
❌❌🤍🦷🤍 Три дня потел над этой хуйней но оно того стоит вроде 😐 В комментах будет ссылка на то же самое, но на ютубчике, приятно будет получить огромную гору лайков ❌🍡🩹🐰🍡🩹 #animation #oc #bryce #jeremy
custom 53710923415179838255
😁 РОЗЫГРЫШ 😁 Чтобы поучаствовать в розыгрыше зина(+подарки) необходимо: ‣ Быть подписанным на ТГК зина; ‣ Репостнуть пост в свой тгк/нескольким друзьям; ‣ Написать в комментариях к ЭТОМУ ПОСТУ порядковый номер и приложить скриншот репоста; ‣ Ожидайте итоги по окончании предзаказов. Доставка набора в случае выигрыша бесплатная. Если вы уже заказали данный набор и выиграли, мы вернем вам средства за набор. 😈😈😈 СОДЕР…
#dobrosashik_art #fan_art —————— - Коммишка для @tideidle Спасибо за щуку
custom 53705941296066140324custom 53710923415179838252
Showing the 12 most recent of 13 posts we hold for @taida_idle. 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 — 154,942 of 1,481,502entries 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.
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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association— we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“ŦIDE idle.” (@taida_idle), 90 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/taida_idle.
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.