Быстрее рисуй чтобы я наконец на тебя подписался 💕
custom 54633957714391566732
![Telegram profile photo for Bellory [РЕСТ]](https://cdn.tgregister.com/av/59/59e3ad89c5499094955d7b08672ec2456ce97d0612e38796222355466018c3f9.jpg)
Channel
@belloryarts
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
84subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003881128617 |
|---|---|
| Type | Channel |
| Username | @belloryarts |
| Created | Between 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/belloryarts |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 16:20 | 84 | -7 |
| 29 Aug 2026, 22:55 | 91 | -3 |
| 22 Aug 2026, 12:38 | 94 | +5 |
| 14 Aug 2026, 19:37 | 89 | +4 |
| 9 Aug 2026, 17:00 | 85 | no change |
| 7 Aug 2026, 18:48 | 85 | first reading |
19 posts held, back to 5 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
139 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 47.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463395771439156673 | 66 | 47.5% | |
| custom 5463271694128944291 | 24 | 17.3% | |
| 🍓 | 20 | 14.4% | |
| custom 5269502608187339214 | 10 | 7.19% | |
| custom 5348438459205831716 | 6 | 4.32% | |
| custom 5388692490431787798 | 6 | 4.32% | |
| custom 5462951620281144610 | 5 | 3.60% | |
| custom 5334555557242105381 | 2 | 1.44% |
Custom emoji. 7 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 are Telegram’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 17 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 139 reactions 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 5 August 2026 to 9 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 54633957714391566732
Сегодня артов не будет, я устав #щп
custom 54633957714391566731
Ленивые скетчи #sketch
custom 54633957714391566739custom 54632716941289442912custom 53886924904317877981custom 54629516202811446101
Я закончила, мне не нравится, спасибо за внимание 🌟🌟 #burningspicecookie
custom 52695026081873392147custom 54633957714391566732custom 54632716941289442911
Решила попробовать что-то серьезное. Не знаю, закончу ли. Вероятность мала, нооооо… набираемся опыта, опыт опыт #щп
custom 54633957714391566735custom 53345555572421053812custom 54629516202811446102
Я СДЕЛАЛА ЭТО
custom 54633957714391566738custom 54632716941289442912custom 52695026081873392141
Ещё одна работа на ДТИЙС!!! Спасибо! Ждём остальных и дожидаемся даты результатов. 🫵
custom 54633957714391566736
Ура тикток #underfell #alphys
🍓6custom 54633957714391566736custom 53484384592058317162
Версия с очками. Я забыла их включить на холсте(((( #underfell #alphys #sans #salphys
🍓6custom 54633957714391566735
Мяу #underfell #alphys #sans
custom 546327169412894429110custom 54633957714391566735custom 53886924904317877982
Да, если что.. шибко тяжелый фон будет доплачиваться, но там будет некритично, если что с заказчиком можно будет это обговорить.
custom 54633957714391566734custom 52695026081873392141custom 54632716941289442911
Bellory pinned a photo
Showing the 12 most recent of 19 posts we hold for @belloryarts. 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.
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.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Bellory [РЕСТ]” (@belloryarts), 84 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/belloryarts.
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.