Channel
@sugarloove
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
42subscribers
-1 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003646035463 |
|---|---|
| Type | Channel |
| Username | @sugarloove |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 12 September 2026 |
| On Telegram | t.me/sugarloove |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 22:25 | 42 | -1 |
| 13 Aug 2026, 00:30 | 43 | no change |
| 13 Aug 2026, 00:20 | 43 | first reading |
16 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 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 16 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
151 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 19.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5391065820640091016 | 30 | 19.9% | |
| custom 5906638492330367382 | 28 | 18.5% | |
| custom 5444982142834583372 | 24 | 15.9% | |
| custom 5906640644108982974 | 24 | 15.9% | |
| custom 5445399669490330155 | 17 | 11.3% | |
| custom 5235658025376718398 | 11 | 7.28% | |
| custom 5906516644108179760 | 9 | 5.96% | |
| custom 5336787823544539094 | 8 | 5.30% |
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 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 12 of the 16 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 151 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 19 July 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.
агу агу аббрэээмэа прастете реквесты пока откладываю на потом очен далеко, сейчас в приоритете заказы 🌟за 50 звезд вот што прлучилос ୨୧・┈┈┈┈・┈┈┈┈・୨୧ ♡ ~ #скетч , #коммишка
custom 54449821428345833724custom 54453996694903301553custom 53910658206400910162
кагда нибудь я стану крутой художницей и на меня подпишутся маи кумиры
custom 53367878235445390945custom 54449821428345833724custom 59066384923303673824custom 53910658206400910162
мне заплатили 65 звезд без учета тупой комиссии (ToT) мне вродэ нравица результат! это у миня давно заказали, так шо я ваши реквы рисую, не переживайте 🌟 ୨୧・┈┈┈┈・┈┈┈┈・୨୧ ♡ ~ #скетч ? , #коммишка
custom 54453996694903301555
Live stream started
Live stream scheduled for Jul 22 at 13:20
я решил добавить шляпк, т.к. перс у меня ассоциировался с хогвартсвом и всякой магией 🌟🌟 мимомомооаоаомоом я захотел попробовать новую технику на реквесте мб я с другими реквестами также проверну, ну типа буду пробовать всякое разное для покраса ୨୧・┈┈┈┈・┈┈┈┈・୨୧ ♡ ~ #скетч , #реквест
custom 539106582064009101610custom 54453996694903301552custom 59066406441089829742custom 52356580253767183981custom 59065166441081797601
а вы знали шо я веду трансляции где в реальном времени рисую ваши реквы бтв кстати я могу там и гифты просто так рисовать и доп просьбы 🌟 well я намекаю на то шо хотите штоб я проводила подобное не только в закрытом канале, а тут на основе 😳😳😳
custom 59066384923303673825custom 59065166441081797603custom 59066406441089829742
крутые пацаны. я не умею рисовать м*нов бтв кстати я люблю сш вы все канон ୨୧・┈┈┈┈・┈┈┈┈・୨୧ ♡ ~ #скетч , #реквест
custom 53910658206400910168custom 54453996694903301553custom 59066384923303673822custom 53367878235445390941custom 59065166441081797601custom 59066406441089829741
ребзи реквы временно закрыты
custom 59066406441089829744
🌟🌟 тру сигмо я думал шо умру пока это рисовала💔💔энивей ладно, коммишен за 200 зв для @pawssmisa 🤗 !! поздравьте друна заказчика с др это нежный приказ ୨୧・┈┈┈┈┈┈・┈┈┈┈┈┈・୨୧ 🍓 ~ #коммишка , #арт
custom 54449821428345833727custom 59066384923303673827custom 59066406441089829746custom 54453996694903301554custom 52356580253767183983custom 59065166441081797602custom 53367878235445390941
😒☺️
пр кароче первая кмм за 50 зв, вторая за 15 зв, третье это гифт ୨୧・┈┈┈┈・┈┈┈┈・୨୧ ♡ ~ #скетч , #коммишка
custom 52356580253767183984custom 54449821428345833723custom 59066406441089829743custom 53910658206400910162custom 59066384923303673822custom 59065166441081797601
Showing the 12 most recent of 16 posts we hold for @sugarloove. 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.
Named by 1 registered channel — 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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“``🍧 | LALAVERSE” (@sugarloove), 42 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/sugarloove.
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.