Telegram RegisterThe public register of Telegram

Channel

ragdolll83

@ragdolll83

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

228subscribers

+0 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-1002111069761
TypeChannel
Username@ragdolll83
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/ragdolll83

Growth

2288 Aug 2026, 13:30 — 228 subscribers8 Aug 2026, 14:38 — 228 subscribers8 Aug 2026, 13:308 Aug 2026, 14:38
2 measurements taken within a single day. 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 227–229 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 14:38228no change
8 Aug 2026, 13:30228first reading

Engagement

16 posts held, back to 15 June 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
85.6%
avg views ÷ 228 subscribers
Avg views / post
195
14 posts measured
Reaction rate
2.78%
reactions ÷ views · ER floor
Posts in window
14
of 16 held

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. It is computed over the 13 of 14 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 20 July 2026
Posts held16 (15 June 202620 July 2026)
Views total2,733
Reactions total71
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 13:30 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.

Reaction mix

85 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 74.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6374.1%
💅67.06%
🤣55.88%
🍾44.71%
💩44.71%
😱33.53%

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 16 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 85reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 15 June 2026 to 20 July 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

20 Jul 2026, 22:10 UTC195 views1 reactionsread 8 August 2026
Video message

Video message, posted without a caption

💩1

Signed pytexx

20 Jul 2026, 20:36 UTC200 views9 reactionsread 8 August 2026
Photo

это мои фанаты дурак

💅63

Signed pytexx

20 Jul 2026, 19:59 UTC194 views9 reactionsread 8 August 2026
Photo

мои фанатки тоже подшарили🥰🥰🥰

🤣54

Signed Magumi

19 Jul 2026, 20:04 UTC203 views4 reactionsread 8 August 2026
Video message

Video message, posted without a caption

4

Signed pytexx

18 Jul 2026, 23:03 UTC203 views3 reactionsread 8 August 2026
Voice message

Voice message, posted without a caption

3

Signed pytexx

18 Jul 2026, 22:30 UTC196 views3 reactionsread 8 August 2026
Video message

Video message, posted without a caption

3

Signed pytexx

18 Jul 2026, 22:18 UTC190 views3 reactionsread 8 August 2026
Video message

Video message, posted without a caption

3

Signed pytexx

18 Jul 2026, 21:47 UTC185 views2 reactionsread 8 August 2026
Voice message

Voice message, posted without a caption

2

Signed pytexx

18 Jul 2026, 21:04 UTC183 views2 reactionsread 8 August 2026
Video message

Video message, posted without a caption

2

Signed pytexx

18 Jul 2026, 20:48 UTC183 viewsread 8 August 2026

https://t.me/pavelT52 попросили продвинуть канал, простите за рекламу

Signed Magumi

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

Citation-graph rank

Citation-graph rank — 1,093,780 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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.

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

“ragdolll83” (@ragdolll83), 228 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ragdolll83.

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.