касперлайты..какието...gulp...уползаю обратно отсыпаться после работы #regretevator
custom 52602535893889296088custom 53122320352244086372

Channel
@slime13tg
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
159subscribers
+8 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002205549189 |
|---|---|
| Type | Channel |
| Username | @slime13tg |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/slime13tg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 11:17 | 159 | -4 |
| 9 Sept 2026, 06:39 | 163 | +6 |
| 1 Sept 2026, 00:06 | 157 | +7 |
| 24 Aug 2026, 01:22 | 150 | -1 |
| 8 Aug 2026, 19:46 | 151 | no change |
| 8 Aug 2026, 17:15 | 151 | first reading |
11 posts held, back to 1 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 11 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
172 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 33.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5260253589388929608 | 58 | 33.7% | |
| custom 5260629923013338676 | 51 | 29.7% | |
| custom 5260342465147185850 | 33 | 19.2% | |
| 🆒 | 12 | 6.98% | |
| custom 5312232035224408637 | 6 | 3.49% | |
| 🤓 | 5 | 2.91% | |
| custom 5260389379074960944 | 4 | 2.33% | |
| custom 5260207250986771862 | 2 | 1.16% | |
| custom 5422504912527319806 | 1 | 0.581% |
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 10 of the 11 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 172 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 1 August 2026 to 8 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.
касперлайты..какието...gulp...уползаю обратно отсыпаться после работы #regretevator
custom 52602535893889296088custom 53122320352244086372
🔡 🔡🔡🔡🔡 🔡🔡🔠🔡🔡🔡🔡🔡 🔡🔡🔡🔡 💣❤️ спасибо всем кто подписан лайкает комментит В ОБЩЕМ остается со мной я ужасно люблю каждого/ую/ых кто здесь есть правда спасибо вам огромное 🤩🤩🤩 нихуя кншн не ощущаю себя на 21 все еще чувство что я в 2018-19ом году ахахвхвххаа ну и конечно же лучший подарок художнику на др это репост его работ соу!!!!! буду очень рада ехехехе 😇😇😇😇
🆒6custom 53122320352244086373custom 54225049125273198061
Маргоша молодоша в свои лучшие годы
Кококо для @chipsik003 , @Arsa_Pivo и @mihanuu
custom 52603424651471858507custom 52602535893889296081custom 53122320352244086371
данте базилио это мой ос если че он мне сегодня снился
custom 526034246514718585022
купите мне травы я тоже буду круто рисовать, сделаю вам вторую главу, и никакого инцеста
custom 526025358938892960820custom 52603424651471858504
бляьь какой жи сука тупои фандом у 811 простите ребята я с вами не могу нахуй КАЖДЫЙ РАЗ КОНТАКТИРУЯ С ФАНБАЗОЙ ЭТОГО ПРОЕКТА Я ВСПОМИНАЮ ПОЧЕМУ Я ЭТОГО РАНЕЕ НЕ ДЕЛАЛА.
custom 526062992301333867623🤓5custom 52603893790749609444custom 52602072509867718622
это было забавно
🆒6custom 52602535893889296082
почему так мало роблокс косплееров и так много хоумстака я все еще на луке бтв
custom 52602535893889296089custom 52606299230133386767
бля я тока зашла на лук пиздец
custom 526062992301333867617
ребятки, завтра залечу на пару часиков на московский Лук маркет, к сожалению без косплеев, но намалеваная, так что увидите разноцветное уебище - это ваша художница слякочь ^^
custom 526025358938892960818custom 52606299230133386764
Showing the 11 most recent of 11 posts we hold for @slime13tg. 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 5 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“▶️ slyakoch. . . .” (@slime13tg), 159 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/slime13tg.
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.