Done ReadyMade Alipay Payfirst @Rurisyz

Channel
RIVIEW WORK 瑠裡
@riviewallworkrurisyz
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,125subscribers
+760 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003938078038 |
|---|---|
| Type | Channel |
| Username | @riviewallworkrurisyz |
| Created | Between 1 April 2026 and 24 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/riviewallworkrurisyz |
Topic
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 09:36 | 1,125 | -35 |
| 5 Oct 2026, 12:17 | 1,160 | -44 |
| 27 Sept 2026, 17:58 | 1,204 | -62 |
| 18 Sept 2026, 05:21 | 1,266 | -23 |
| 14 Sept 2026, 10:19 | 1,289 | -56 |
| 10 Sept 2026, 16:40 | 1,345 | -68 |
| 5 Sept 2026, 12:57 | 1,413 | +441 |
| 27 Aug 2026, 14:09 | 972 | -142 |
| 24 Aug 2026, 10:45 | 1,114 | -188 |
| 20 Aug 2026, 18:03 | 1,302 | -218 |
| 17 Aug 2026, 19:05 | 1,520 | -138 |
| 14 Aug 2026, 23:04 | 1,658 | +1,303 |
| 8 Aug 2026, 14:23 | 355 | -10 |
| 8 Aug 2026, 06:31 | 365 | no change |
| 7 Aug 2026, 19:17 | 365 | first reading |
Engagement
10 posts held, back to 24 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 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 10 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
done kyc Hackerone @rurisyz
payfirst Kyc airbnb Done Eu @Rurisyz
Payfirst kyc pst.net @Rurisyz
Channel photo updated
RIVIEW WORK 瑠裡 pinned «Please check this before proceeding with the transaction, for our mutual convenience. https://telegra.ph/Terms-of-Service---Rurisyz-07-28»
Redotpay readymade payfirst @Rurisyz
Done escrow 2Top with @g3rsh thanks @rurisyz
Payfirst kyc Coinex @Rurisyz
done payfirst sell link Otc 80+++ @Rurisyz
Showing the 10 most recent of 10 posts we hold for @riviewallworkrurisyz. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“RIVIEW WORK 瑠裡” (@riviewallworkrurisyz), 1,125 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/riviewallworkrurisyz.
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.