Telegram RegisterThe public register of Telegram
Telegram profile photo for это моти

Channel

это моти

@MotiSladusya

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

75subscribers

+13 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003927906236
TypeChannel
Username@MotiSladusya
CreatedBetween 1 April 2026 and 16 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 16 September 2026
On Telegramt.me/MotiSladusya

Growth

627568.58 August 2026 — 62 subscribers10 August 2026 — 62 subscribers16 August 2026 — 72 subscribers23 August 2026 — 73 subscribers30 August 2026 — 72 subscribers9 September 2026 — 75 subscribers8 August 20269 September 2026
6 measurements spanning 32 days, net +13. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 60–77 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 06:0175+3
30 Aug 2026, 13:5772-1
23 Aug 2026, 13:2373+1
16 Aug 2026, 18:2672+10
10 Aug 2026, 04:0162no change
8 Aug 2026, 08:0162first reading

Engagement

19 posts held, back to 16 July 2026the 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

258 reactions across 18 posts, in 17 distinct kinds. The most used accounts for 32.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8332.2%
custom 52897941854722597473011.6%
custom 5278731449229409608238.91%
💘238.91%
custom 5195432190611053489218.14%
custom 5413359518404860001197.36%
❤‍🔥145.43%
custom 533704610140286645893.49%
custom 542498367129782516683.10%
🐳72.71%
🫡62.33%
custom 544275253082194834351.94%
🍓41.55%
custom 527828221283011532331.16%
custom 534829578039227101410.388%
🎉10.388%
🦄10.388%

Custom emoji. 9 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 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 258 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 16 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.

Recent posts

7 Aug 2026, 21:08 UTC20 views9 reactionsread 10 August 2026

Рисули будут, езжу сейчас туда сюда,устала я конечно жоско очень, хотя хотелось бы сейчас просто сгнить в кроватке🍮🍮🍮

custom 52897941854722597479

7 Aug 2026, 20:59 UTC24 views9 reactionsread 10 August 2026

Блин, мьшечки,пишите в лс если вы отписываетесь, я так не понимаю 😭

custom 53370461014028664589

4 Aug 2026, 22:12 UTC50 views22 reactionsread 10 August 2026
Photo

Вот на морюшке сейчас отдыхаю,а у вас чо как🍮 #скетч

custom 5289794185472259747146custom 54249836712978251662

31 Jul 2026, 15:03 UTC79 views12 reactionsread 10 August 2026
Photo

Меня на большее не хвптает #реквест

❤‍🔥93

30 Jul 2026, 16:55 UTC117 views24 reactionsread 10 August 2026
Photo

Привыкаю к стилю, сделала новую постоянную ос🤩 #Ос

custom 5195432190611053489118❤‍🔥5

29 Jul 2026, 16:34 UTC94 views29 reactionsread 10 August 2026
Photo

Милейшая коллаба с мадам диви ксвииии 🍮🍮🍮 пасиба большо😀 #арт #коллаб

💘156custom 54249836712978251664custom 52897941854722597472custom 51954321906110534891custom 54427525308219483431

28 Jul 2026, 15:48 UTC73 views7 reactionsread 10 August 2026

Хочется какта стиль интереснее сделать и поэкспериментировать🐈

7

27 Jul 2026, 21:22 UTC121 views26 reactionsread 10 August 2026
Photo

Запросик да 🥺👋 #скетч #арт

12custom 51954321906110534898custom 52897941854722597474custom 52787314492294096081custom 54249836712978251661

26 Jul 2026, 17:12 UTC189 views21 reactionsread 10 August 2026
Photo

Заждались неверна д #аушка

custom 527873144922940960813🫡61custom 54249836712978251661

18 Jul 2026, 22:00 UTC125 views23 reactionsread 10 August 2026
Photo

Не плачь старфайр лпшки тебя поддержат💔 Я ЕБУ КАЧЕСТВО #Аушка

custom 5413359518404860001145custom 54427525308219483434

Showing the 12 most recent of 19 posts we hold for @MotiSladusya. 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.

Forward network

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.

Mentions

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.

Cite this entry

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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“это моти” (@MotiSladusya), 75 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/MotiSladusya.

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.