Telegram RegisterThe public register of Telegram

Channel

‌‌ ‌ ‌ ‌ ‌ ‌ ‌ 𝒥ຸ︩𝗌𝗐𝖾𖫲𝖾𝗍̈ı𝖾 ‌ ‌ ‌‌ ‌ ‌‌

@risurie

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

19subscribers

+5 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004305988099
TypeChannel
Username@risurie
Description‌ ╅─ I live like an @lovely sentence, ‌ waiting for words that never come
Created6 August 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held3
On Telegramt.me/risurie

Growth

141916.57 August 2026 — 14 subscribers8 August 2026 — 19 subscribers11 August 2026 — 19 subscribers7 August 202611 August 2026
3 measurements spanning 4 days, net +5. 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 13–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 16:3119no change
8 Aug 2026, 04:5219+5
7 Aug 2026, 20:2614first reading

Engagement

15 posts held, back to 6 August 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
855.9%
avg views ÷ 19 subscribers
Avg views / post
163
13 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
15
of 15 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held15 (6 August 202611 August 2026)
Views total2,114
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 16:31 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

Photos
9
Links
3

Lifetime counters from Telegram’s own channel header, read 11 August 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.

Recent posts

11 Aug 2026, 15:53 UTC6 viewsread 11 August 2026
Photo

ㅤㅤㅤㅤㅤ︶𝄄۪︶۫۫︶𝄄۫︶ 🪽🪽 ︶۫𝄄︶۫۫︶۪۫𝄄︶۫ 🤍 For u :3, @risurie🤍

10 Aug 2026, 16:49 UTC20 viewsread 11 August 2026

گذاشتم چک کنین اگه کسی رو نذاشتم توی بات بگه @qlirfrebot

8 Aug 2026, 13:57 UTC41 viewsread 11 August 2026
Forwarded from @vanir_oPhoto

‌ ‌ ‌ ‌ ‌ ‌ ‌  𐔥ᦅɾ ‌ ‌ ‌ ‌ ‌t.me/risurie ‌ ‌ ‌  ᥡ𑜕꩙

7 Aug 2026, 21:40 UTCviews —

‌‌ ‌ ‌ ‌ ‌ ‌ ‌ 𝒥ຸ︩𝗌𝗐𝖾𖫲𝖾𝗍̈ı𝖾 ‌ ‌ ‌‌ ‌ ‌‌ pinned a photo

7 Aug 2026, 18:46 UTC62 viewsread 11 August 2026
Forwarded from @Beatri_ce_diaryPhoto

‌ ᥒᥱᥕ ᥴһᥲᥣᥣᥱᥒgᥱ .ᐟ.ᐟ ‌𐔌˙. ◡◠̣◡ࠝᩚ◠̣݁◡◠̣◡ࠝᩚ◠̣݁◡◠̣◡ࠝᩚ◠̣◡◠̣◡ࠝᩚ◠̣݁◡◠̣◡ࠝᩚ◠̣݁◡◠̣◡ࠝᩚ◠̣◡݁◡◠̣◡ࠝᩚ◠̣݁◡◠̣ ᯓ 𝗙𝗈𝗋𝗐𝖺𝗋𝖽 𝗍𝗁︎𝗂𝗌 𝗉𝗈𝗌𝗍 𝗍𝗈 𝗒𝗈𝗎𝗋 𝗉𝗋𝖾𝗍𝗍𝗒 𝖼︎𝗁︎𝖺𝗇︎𝗇︎𝖾𝗅︎ 𝖺𝗇︎𝖽 ℬℯ𝒶𝓉𝓇𝒾𝒸ℯ 𝗐𝗂𝗅︎𝗅︎ 𝗀︎𝗂𝗏︎𝖾 𝗒𝗈𝗎 𝖺𝗇︎ 𝗔𝗹𝗶𝗲𝗻 𝘀𝘁𝗮𝗴𝗲 𝖼︎𝗁︎𝖺𝗋𝖺𝖼︎𝗍𝖾𝗋 𝖺𝗇︎𝖽 ℳ𝒾𝓏𝓊𝓂𝓎 𝗐𝗂𝗅︎𝗅︎ 𝗀︎𝗂𝗏︎𝖾 𝗒𝗈𝗎 𝗈𝗇︎𝖾 𝗈𝖿︎ 𝗍𝗁︎𝖾𝗂𝗋 𝗌𝗈𝗇︎𝗀︎𝗌 .ᐟ.ᐟ

7 Aug 2026, 06:39 UTC86 viewsread 11 August 2026
Photo

‌ ㅤ𝅼ㅤㅤ۫ㅤ‌‌𝒞ó𝑚𝑜 𝓔𝓼 𝑚𝑒 𝑝𝑟𝑒𝑔𝑢𝑛𝑡𝑎𝑠 𝑐ó𝑚𝑜 𝓔𝓼 𝑆𝑒𝑔ú𝑛 𝑚𝑖 𝑒𝑥𝑝𝑒𝑟𝑖𝑒𝑛𝑐𝑖𝑎 𝓔𝓼 𝑒𝑥𝑡𝑟𝑒𝑚𝑎𝑑𝑎𝑚𝑒𝑛𝑡𝑒 𝑐𝑟𝑢𝑒𝑙 𝓨 𝑝𝑜𝑟 𝑢𝑛 𝑠𝑒𝑔𝑢𝑛𝑑𝑜 𝑐𝑟𝑒𝑒𝑠 𝑒𝑛𝑡𝑒𝑛𝑑𝑒𝑟 𝑡𝑜𝑑𝑜 𝑒𝑠𝑡𝑒 ℎ𝑜𝑟𝑟𝑜𝑟 𝓨 𝑝𝑜𝑟 𝑢𝑛 𝑠𝑒𝑔𝑢𝑛𝑑𝑜 𝑐𝑜𝑚𝑝𝑎𝑟𝑡𝑖𝑟𝑒𝑚𝑜𝑠 𝑎𝑙𝑔𝑜 𝑡𝑢 𝓨 𝑦𝑜 𝓨 𝑒𝑠𝑒 𝑠𝑒𝑟á 𝑒𝑙 𝑡𝑖𝑒𝑚𝑝𝑜 𝑞𝑢𝑒 𝑛𝑜𝑠 𝑟𝑒𝑓𝑢𝑔𝑖𝑎𝑟𝑒𝑚𝑜𝑠 𝑈𝑛 𝑑𝑒𝑠𝑎𝑠𝑡𝑟𝑒 𝑖𝑛𝑒𝑣𝑖𝑡𝑎𝑏𝑙𝑒 ‌ 𝓔𝓼 𝑢𝑛 𝑎𝑚𝑎𝑟𝑔𝑜 𝑑𝑒𝑠𝑒𝑛𝑙𝑎𝑐𝑒 ‌ ‌ 𝓔𝓼 𝑢𝑛 𝑐𝑎𝑚𝑖𝑛𝑜 𝑎𝑙 𝑝𝑟𝑒𝑐𝑖𝑝𝑖𝑐𝑖𝑜 ‌‌ ‌ ‌𝓔𝓼 𝑒𝑙 𝑚𝑎𝑦𝑜𝑟 𝑑𝑒 𝑙𝑜𝑠 𝑑𝑒𝑙𝑖𝑟𝑖𝑜𝑠 ㅤ۪ㅤׂㅤㅤ

6 Aug 2026, 17:17 UTC76 viewsread 11 August 2026
Photo

𝑡ℎ𝑒 𝑘𝑖𝑛𝑑 𝑤ℎ𝑒𝑟𝑒 𝑦𝑜𝑢 𝑎𝑟𝑒 𝑛𝑖𝑐𝑒 𝑡𝑜 𝑚𝑒 ‌𝑏𝑢𝑡 𝑜𝑛𝑙𝑦 𝑖𝑛 𝑡ℎ𝑒 𝑒𝑣𝑒𝑛𝑖𝑛𝑔 𝑠𝑜 𝑖 𝑎𝑠𝑘, 𝑎𝑚 𝑖 𝑗𝑢𝑠𝑡 𝑑𝑟𝑒𝑎𝑚𝑖𝑛𝑔‌ ‌ 𝑦𝑜𝑢 𝑎𝑟𝑒 𝑤ℎ𝑎𝑡 𝑖 𝑐𝑜𝑢𝑙𝑑‌ 𝑏𝑒𝑙𝑖𝑒𝑣𝑒 𝑖𝑛 𝑠𝑖𝑛𝑐𝑒 𝐼 ℎ𝑎𝑣𝑒 𝑛𝑜𝑏𝑜𝑑𝑦 𝑒𝑙𝑠𝑒

Showing the 12 most recent of 15 posts we hold for @risurie. 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 — 386,642 of 1,176,251entries 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

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

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

“‌‌ ‌ ‌ ‌ ‌ ‌ ‌ 𝒥ຸ︩𝗌𝗐𝖾𖫲𝖾𝗍̈ı𝖾 ‌ ‌ ‌‌ ‌ ‌‌” (@risurie), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/risurie.

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.