Пиздунья совсем чуть-чуть🤣 ну ребят ну выходные были слишком охуенными
custom 53527447995752235541

Channel
@devisxoxo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
254subscribers
+36 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001502340469 |
|---|---|
| Type | Channel |
| Username | @devisxoxo |
| Created | Between 1 July 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/devisxoxo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 23:55 | 254 | +18 |
| 11 Sept 2026, 04:38 | 236 | +5 |
| 24 Aug 2026, 20:48 | 231 | +8 |
| 18 Aug 2026, 06:52 | 223 | +6 |
| 11 Aug 2026, 06:31 | 217 | -1 |
| 10 Aug 2026, 06:45 | 218 | no change |
| 10 Aug 2026, 06:31 | 218 | first reading |
15 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 15 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
252 reactions across 15 posts, in 11 distinct kinds. The most used accounts for 22.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5470175909891836636 | 57 | 22.6% | |
| custom 5195288416580816878 | 30 | 11.9% | |
| 😭 | 25 | 9.92% | |
| custom 5305400649221957862 | 24 | 9.52% | |
| custom 5438387478249611626 | 24 | 9.52% | |
| custom 5404684066719044666 | 20 | 7.94% | |
| custom 5215362870384013458 | 19 | 7.54% | |
| 🔥 | 17 | 6.75% | |
| custom 5352744799575223554 | 16 | 6.35% | |
| custom 5447126194803749877 | 12 | 4.76% | |
| custom 5470172478212965199 | 8 | 3.17% |
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 15 of the 15 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 252 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 1 August 2026 to 10 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 53527447995752235541
Hange Zoe | WIP | И такое бывает 🔥 #рисовакаю
custom 530540064922195786215custom 51952884165808168783custom 52153628703840134582custom 54046840667190446661
🥹🥹🥹
custom 54701759098918366369custom 54701724782129651997custom 54471261948037498774😭1custom 52153628703840134581custom 53527447995752235541
Levihan | Childhood friends — Time flies, huh? For LeviHan Week day 5 #рисовакаю
🔥11custom 54471261948037498778😭4custom 52153628703840134582custom 54383874782496116261custom 54701724782129651991
New art “Childhood friends” coming today🕺 Глава мб тоже камин тудэй, но чета меня там опять попёрло понесло, так что уверенности в тудэй нет🤣 #сомнительныемысли
custom 54701759098918366367custom 54383874782496116263
Levihan | WIP | Childhood friends Group sobbing on three!!!🥹 For LHW idk what day #рисовакаю
custom 521536287038401345814😭5custom 54701759098918366363
Леви, моргни, если тебя держат в заложниках хештег высокоеискусство друзьядетства
custom 535274479957522355410custom 54701759098918366364
Фарлан Чёрч это типа Фарлан церковь?....🧠 почему я додумалась до этого только сейчас... Вечером будет эскиз чего-либо. Глава пишется #сомнительныемысли
custom 540468406671904466611custom 51952884165808168787custom 53054006492219578625
Время зашкварных историй. Ситуация: есть тренажерный зал (далее тз). Работает тренер мужлан и, как оказалось, на протяжении долгого времени скидывает свои гениталии девушкам-подопечным. Среди них есть несовершеннолетние девочки(!). Ситуация всплывает, коллективное заявление в полицию, проводится проверка. Что делает руководство тз? НАНИМАЕТ ТРЕНЕРУ АДВОКАТА ЗА СВОЙ СЧЕТ. Главный руководитель – ЖЕНЩИНА, обвиняет во …
custom 543838747824961162612
ДИЧАЙШИЕ приятности🥹🥹🥹 I know some people have my art as their wallpaper, but I can't find those messages🥹 All the love my babies xx🥹🫶🏻 #приятности
custom 547017590989183663611🔥5custom 51952884165808168782custom 54046840667190446661
Хотите – верьте, хотите – нет… на этой неделе глава Коротышки 😇 #сомнительныемысли #Коротышка
custom 54701759098918366368custom 53054006492219578624
Levihan | Death by Love For LHW Enemies to Lovers🗡️ #рисовакаю
custom 547017590989183663614custom 54383874782496116268custom 54046840667190446664custom 51952884165808168782
Showing the 12 most recent of 15 posts we hold for @devisxoxo. 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.
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.
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.
“Зашкварные истории” (@devisxoxo), 254 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/devisxoxo.
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.