сладуська моя
custom 526067449618395759068custom 525822644642959732664custom 524900960123122469129custom 525850662432618464613custom 54250124733485195741

Channel
@adellisha
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
8,992subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001638156211 |
|---|---|
| Type | Channel |
| Username | @adellisha |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/adellisha |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 45% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 21:20 | 8,992 | +9 |
| 13 Sept 2026, 05:20 | 8,983 | +1 |
| 9 Sept 2026, 17:16 | 8,982 | +41 |
| 3 Sept 2026, 22:57 | 8,941 | +9 |
| 31 Aug 2026, 09:27 | 8,932 | +40 |
| 28 Aug 2026, 00:43 | 8,892 | +2 |
| 24 Aug 2026, 14:54 | 8,890 | -18 |
| 21 Aug 2026, 08:58 | 8,908 | -8 |
| 18 Aug 2026, 12:36 | 8,916 | -21 |
| 15 Aug 2026, 20:49 | 8,937 | -29 |
| 12 Aug 2026, 05:37 | 8,966 | -20 |
| 9 Aug 2026, 14:21 | 8,986 | -3 |
| 7 Aug 2026, 00:17 | 8,989 | -1 |
| 6 Aug 2026, 22:45 | 8,990 | no change |
| 6 Aug 2026, 22:38 | 8,990 | first reading |
63 posts held, back to 31 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 34 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 63 (31 July 2026 – 28 August 2026) |
| Views total | 28,010 |
| Reactions total | 1,114 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 17:06 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 4 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.
12,377 reactions across 63 posts, in 5 distinct kinds. The most used accounts for 39.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5258226446429597326 | 4,875 | 39.4% | |
| custom 5249009601231224691 | 2,694 | 21.8% | |
| custom 5258506624326184646 | 1,837 | 14.8% | |
| custom 5425012473348519574 | 1,613 | 13.0% | |
| custom 5260674496183957590 | 1,358 | 11.0% |
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 63 of the 63 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 12,377 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 63 most recent posts we hold, published 31 July 2026 to 28 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 526067449618395759068custom 525822644642959732664custom 524900960123122469129custom 525850662432618464613custom 54250124733485195741
https://www.instagram.com/p/DcdNrwTDJmI/?igsi=MWp4MmU3cThwNDVkdA== закинула, жду актив!!!
custom 526067449618395759039custom 525822644642959732611custom 52585066243261846469
могер
custom 525850662432618464659custom 52582264464295973264custom 52606744961839575904custom 52490096012312246911
……..
custom 525850662432618464649custom 52606744961839575908custom 52582264464295973266custom 52490096012312246912
Video message, posted without a caption
custom 525850662432618464649custom 524900960123122469115custom 54250124733485195747custom 52582264464295973265custom 52606744961839575905
(я еще не ложилась как обычно)
custom 542501247334851957484custom 525822644642959732643custom 524900960123122469131custom 52585066243261846466custom 52606744961839575905
доброе утро 💅🏻
custom 525850662432618464696custom 525822644642959732669custom 526067449618395759040custom 524900960123122469112custom 54250124733485195744
ОЙ КАКИЕ ТАМ ФОТКИ ЖДУТ ВАС АААААА
custom 5258226446429597326161custom 526067449618395759061custom 524900960123122469148custom 52585066243261846466
не делаем вид что я всех забайтила снова встречать со мной рассвет ибо мне лень было ехать домой
custom 524900960123122469189custom 525822644642959732661custom 525850662432618464631custom 52606744961839575907custom 54250124733485195743
Video message, posted without a caption
custom 5258226446429597326115custom 524900960123122469143custom 526067449618395759034custom 54250124733485195744
так лучше
custom 5425012473348519574146custom 526067449618395759081custom 525850662432618464657custom 525822644642959732628custom 524900960123122469110
👀
custom 5249009601231224691130custom 525822644642959732672custom 542501247334851957450custom 526067449618395759016custom 52585066243261846464
Showing the 12 most recent of 63 posts we hold for @adellisha. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
кто от куда?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 63 most recent posts we hold, published 31 July 2026 to 28 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“adelish” (@adellisha), 8,992 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/adellisha.
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.