Channel
@mabds_art
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
62subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002158493166 |
|---|---|
| Type | Channel |
| Username | @mabds_art |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mabds_art |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 04:15 | 62 | no change |
| 8 Aug 2026, 10:04 | 62 | first reading |
19 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 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 18 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 19 (21 July 2026 – 6 August 2026) |
| Views total | 973 |
| Reactions total | 218 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 04:15 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 10 August 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.
218 reactions across 18 posts, in 3 distinct kinds. The most used accounts for 77.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5208762480607652685 | 168 | 77.1% | |
| custom 5461069075985754731 | 49 | 22.5% | |
| custom 5242519467560304803 | 1 | 0.459% |
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 18 of the 19 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 218reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 21 July 2026 to 6 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.
#art@mabds_art #Мартовский_праздник@mabds_art Раз, два, три, поворот, Еще раз! Я не знаю, наверное это какая-то аушка по мартовским, но мне почему-то кажется что песня очень ими вайбует Совершенно не понятно, какой период, потому что Холидей стала бирюзовой уже сильно позже алого Маартала, но так они лучше по цветам сочетаются
custom 520876248060765268510
🔍 Найти любимую песню!
custom 54610690759857547315
Спойлер рисующейся картинки
#text@mabds_art С днем дня, новая часть "Зеркала" https://ficbook.net/readfic/019f48ab-e038-73d2-a32a-eeb1079714f6
custom 520876248060765268510
#art@mabds_art Обычно не пощу сюда картинки с мафии, потому что без контекста они не особо понятны, но этот скетчик мне так нравится, что его, пожалуй, выложу
custom 520876248060765268514
#art@mabds_art #Warhammer #Rogue_trader #Rogue_artist Угадайте с днем чего Заказ
custom 520876248060765268519
Photo, posted without a caption
custom 520876248060765268514
Я думала артфайт все, но мне внезапно жойско отмстили
custom 54610690759857547315
#text@mabds_art Я не забросила! Продолжение "Зеркала"! https://ficbook.net/readfic/019f48ab-e038-73d2-a32a-eeb1079714f6 В этом месяце я планирую больше времени уделять текстам, нежели рисованию, но рисование конечно совсем не заброшу, у меня и мафия и ос музик челлендж, да и заказы все еще открыты, но в целом хочу устроить себе небольшой детокс
custom 52087624806076526859
Ещё немного атак для артфайта🌺 Mabd OhVivOh - - - - ✧ - - - - #artfight #artfight2026 #teammystery
custom 520876248060765268512
#art@mabds_art #Warhammer #Rogue_trader #Rogue_artist #Jae_Hedari Наконец-то успела поучаствовать в #character_weekRT йей! Не могла пройти мимо любимки 🥰
custom 520876248060765268517
Ответила на атаку от Mabd Ее демоница очень хорошенькая❤️ А у меня остался один запланированный реванш. Наверное, от двух последних атак уже не отобьюсь, но что поделать. #basic
custom 520876248060765268511
Showing the 12 most recent of 19 posts we hold for @mabds_art. 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 — 588,257 of 1,350,102entries 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Mabd's art” (@mabds_art), 62 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/mabds_art.
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.