🔹🔹🔹🔹🔹🔹🔹🔹

Channel
️ ️
@RWSQTXX
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004435637952 |
|---|---|
| Type | Channel |
| Username | @RWSQTXX |
| Created | 28 August 2026 — measured — dated from the channel’s first post |
| First recorded | 16 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| On Telegram | t.me/RWSQTXX |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 05:23 | 3 | no change |
| 15 Sept 2026, 18:42 | 3 | +2 |
| 28 Aug 2026, 20:48 | 1 | -8 |
| 22 Aug 2026, 15:52 | 9 | +1 |
| 6 Aug 2026, 22:19 | 8 | first reading |
Engagement
6 posts held, back to 28 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.
- ERR · 30 days
- 7250.0%
- avg views ÷ 3 subscribers
- Avg views / post
- 218
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- of 6 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.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 6 (28 August 2026 – 28 August 2026) |
| Views total | 870 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Sept 2026, 05:23 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.
What this channel posts
- Videos
- 1
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 16 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 9s
- Average length
- 9s
Measured directly from 1 video 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.
Recent posts
Channel name was changed to «️𝐘𝐎𝐔 𝐓𝐇𝐈𝐍𝐊 𝐘𝐎𝐔'𝐑𝐄 𝐑𝐔𝐍𝐍𝐈𝐍𝐆 𝐅𝐑𝐎𝐌 𝐌𝐄, 𝐁𝐔𝐓 𝐘𝐎𝐔'𝐑𝐄 𝐎𝐍𝐋𝐘 𝐑𝐔𝐍𝐍𝐈𝐍𝐆 𝐈𝐍𝐓𝐎 𝐌𝐘 𝐀𝐑𝐌𝐒.»
Sticker, posted without a caption
ㅤㅤㅤ 🤩🤩🤩🤩 🎇💤🌟💼 𝐓𝐀𝐓𝐄 𝐃𝐘𝐀𝐕𝐎𝐋𝐒𝐊𝐈𝐘 𝐃𝐄𝐅𝐅:: 𝐂𝐎𝐂𝐀𝟏𝐍𝐄⛔️⛔️ 𝐀𝐑𝐂𝐇 🔔 𝐀𝐍𝐎𝐍 𝐍𝐔𝐌𝐁𝐄𝐑 :: +𝟔𝟔𝟔🙈🙈🔒 ⭐ 𝐈 𝐃𝐎𝐍'𝐓?👍 𝐁𝐄𝐋𝐎𝐍𝐆 𝐓𝐎 𝐑𝐀𝐈𝐃 𝐀𝐂𝐓𝐈𝐕𝐈𝐓𝐈𝐄𝐒 💼 𝐁𝐋𝐎𝐆 🎁 𝐂𝐑𝐔𝐒𝐇 🤎 𝐒𝐈𝐆𝐍𝐒 🧪 𝐒𝐓𝟏 𝐒𝐓𝟐 𝐒𝐓𝟑 𝐈𝐍𝐈𝐓𝐈𝐀𝐋𝐒 𝐎𝐖𝐍 𝐄𝐌𝐏𝐀𝐂𝐊 𝐏𝐑𝐎𝐅𝐈𝐋𝐄 🕷👋💀✨🎁💘🔒✈️🌟 🔥 𝐎𝐅𝐅𝐈𝐂𝐈𝐀𝐋 𝐀𝐂𝐂𝐎𝐔𝐍𝐓 𝐎𝐍𝐋𝐘
Sticker, posted without a caption
Channel created
Showing the 6 most recent of 6 posts we hold for @RWSQTXX. 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.
Mentions
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“️ ️” (@RWSQTXX), 3 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/RWSQTXX.
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.