кто это и что она делает в этом канале
custom 520170330242470871436custom 53705941296066140325

Channel
@rottenfrau
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
277subscribers
+2 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002376861199 |
|---|---|
| Type | Channel |
| Username | @rottenfrau |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/rottenfrau |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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 |
|---|---|---|
| 15 Sept 2026, 20:00 | 277 | -2 |
| 9 Sept 2026, 03:21 | 279 | +6 |
| 30 Aug 2026, 18:35 | 273 | -1 |
| 24 Aug 2026, 07:27 | 274 | +1 |
| 16 Aug 2026, 20:03 | 273 | -2 |
| 9 Aug 2026, 20:38 | 275 | no change |
| 9 Aug 2026, 14:16 | 275 | first reading |
13 posts held, back to 17 May 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 13 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
701 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 35.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5201703302424708714 | 250 | 35.7% | |
| custom 5283204344135576249 | 167 | 23.8% | |
| custom 5370594129606614032 | 158 | 22.5% | |
| custom 5370711627026931838 | 97 | 13.8% | |
| custom 5219753177364063402 | 15 | 2.14% | |
| custom 5292185009082364042 | 14 | 2.00% |
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 13 of the 13 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 701 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 17 May 2026 to 2 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 520170330242470871436custom 53705941296066140325
слышьте я не сдохла вот вам коленки (комишные)
custom 520170330242470871431custom 537071162702693183811custom 52832043441355762497custom 53705941296066140327
у меня сегодня день рождения. спасибо что следите за моим творчеством. буду рада репостам, всех целую, оставайтесь на линии
custom 520170330242470871452custom 528320434413557624921custom 537059412960661403214custom 53707116270269318382
лайкните пожалуйста обнову 😐
custom 528320434413557624924custom 520170330242470871410custom 53707116270269318386
любопытный кстати факт: в дурке ему долгое время больше всего не хватало бриолина (средство для укладки волос) из атрибутов своей повседневной жизни. волосы без укладки для него синоним неряшливой наружности. наверное, когда ему стало вообще плевать на бриолин и этот дискомфорт от своего внешнего вида, тогда он и начал терять остатки своего прежнего я
custom 537059412960661403218custom 52017033024247087148custom 52832043441355762496custom 53707116270269318382
с добрым утром (после инсулиновой комы) #original@rottenfrau
custom 537059412960661403234custom 528320434413557624912custom 52017033024247087149
вы теперь одеты, как черт я только раздуплилась и увидела сколько вы комментов приятных написали, спасибо 🪳
custom 520170330242470871435custom 537059412960661403213custom 52832043441355762497
причина, почему нет обнов:
custom 520170330242470871427custom 537059412960661403221custom 537071162702693183814custom 52832043441355762495
Photo, posted without a caption
custom 537059412960661403223
хайповый автопортрет который я седня в три ночи рисовала 30 мин посчу потому что обнов не было давно, чтоб вы знали что я не сдохла
custom 537071162702693183846custom 537059412960661403218custom 528320434413557624913custom 52017033024247087145
интересно, почему он так странно злобно смотрит в таком интригующем ракурсе чуть чуть сверху
custom 528320434413557624938custom 520170330242470871423custom 53707116270269318389custom 53705941296066140325
напихайте мне за воротник не знаю как вы, но тест сонди говорит мне что я вспыльчивая нарцисска с лидерскими замашками (буквально генрих)
custom 529218500908236404214custom 52017033024247087147custom 52832043441355762492
Showing the 12 most recent of 13 posts we hold for @rottenfrau. 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐑𝐎𝐓𝐓𝐄𝐍𝐅𝐑𝐀𝐔 𝟏𝟔+” (@rottenfrau), 277 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/rottenfrau.
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.