Telegram RegisterThe public register of Telegram

Channel

⎯᜔⎯ֺ⃞ 𝂅 𝀜𝄆𝐃᷌᪾𝖾⃛𝗂𝗍ְ𝗒 ﹫𝖶ɪ𝖺᷎𝗎𑩑𝗆ְ᷽𝖾᷁𝗅𝗅𝅬] ֦ ྀི ⁠⁠⁠ ❩⁠⁠⁠⁠𝄢⨾ֵ─፝֟‌

@wiaumell

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

649subscribers

-12 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-1002399918368
TypeChannel
Username@wiaumell
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/wiaumell

Growth

6496616557 August 2026 — 661 subscribers8 August 2026 — 661 subscribers14 August 2026 — 649 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net -12. 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 647–663 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:23649-12
8 Aug 2026, 02:35661no change
7 Aug 2026, 15:04661first reading

Engagement

20 posts held, back to 28 April 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
34.1%
avg views ÷ 649 subscribers
Avg views / post
221
10 posts measured
Reaction rate
7.25%
reactions ÷ views · ER floor
Posts in window
10
of 20 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 4 of 10 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 5 August 2026
Posts held20 (28 April 20265 August 2026)
Views total2,213
Reactions total67
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:35 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

311 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 26.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53211146374779039678226.4%
custom 54160832320451679438226.4%
custom 53483549049120661845116.4%
custom 53097974158328146244313.8%
custom 5415624722811484031247.72%
custom 5404336062698910779165.14%
custom 5348089497408009843134.18%

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

Measured over the 20 most recent posts we hold, published 28 April 2026 to 5 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @wiaumell. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 28 April 2026 to 5 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

5 Aug 2026, 18:38 UTC142 viewsread 8 August 2026

Пока Ночи нет, я напишу пост в таком формате ( клик ), но не ответ на ваш вопрос, а просто рассуждения на тему, которая мне очень интересна. Тема, конрчно, напрямую связана с флудами и ролевыми, так что думаю, что вам будет интересно ее прочесть.

5 Aug 2026, 18:31 UTC150 views4 reactionsread 8 August 2026

Короче, это пиздец, ребята У Ночи проблемы с тг, поэтому у нас никак не получается списаться нормально. У меня тоже временные проблемы с интернетом и здоровьем, поэтому тяжело, ноо хорошие новости, я завтра один зайду в какую-нибудь ролевую, скину Ночи ссылки и буду его ждать там, ну и вместе уже обзор сделаем, воттс

custom 54043360626989107794

31 Jul 2026, 15:54 UTC225 views15 reactionsread 8 August 2026

Всем привет, дорогие!! Как ваши дела? Чем занимаетесь?

custom 53097974158328146247custom 54043360626989107794custom 54160832320451679433custom 53211146374779039671

26 Jul 2026, 21:54 UTC294 views20 reactionsread 8 August 2026

🎁⨥ ⸻ #𝐖.𝐈𝖠᪱𝐔𝗠𝖤᪵𝖫𝗟 ۫ 聞 ❜❜ ㅤ۫ ֺ รั命܉⃛ 🌟 ృᰰ ⃫𝐀.𝖣̤𝖬᷏𝖨𝖭؛𝖨𝗦𝗧𝗥͠𝗔𝖳𝗜𝖮̶̌𝖭🤍𝁙ㅤ 𝐖𝗂𝖺𝗎𝗆𝖾𝗅𝗅⤿@Bot · 𝗈𝗐𝗇𝖾𝗋 𝐇е делает обзоры : На флуды по рурепу, твичу, всем фд и к-попу. Маскот : Кавех︱ он / егоᅠׄ ۪ ‌‌ ‌‌ ‌ ‌ ‛‛ 🔳 ‌ ִ 𝐍𝗂𝗀𝗁𝗍𝗂𝖾⤿@Bot · 𝖺𝖽𝗆𝗂𝗇 𝐇е делает обзоры : На флуды по всем фд. Маскот : Барбарос︱ он / егоᅠׄ ۪ ‌‌ ‌‌ ‌ ‛‛ 🔳 ‌ ִ ㅤִㅤ🤩͝ᩙ ؑ͝ ֮ㅤㅤㅤ᷼𓎆ۣ𓎆࣫ ㅤ۟ㅤㅤꢸ ꪳㅤ🌟

custom 53211146374779039677custom 53097974158328146246custom 54043360626989107796custom 54160832320451679431

26 Jul 2026, 21:54 UTC255 views28 reactionsread 8 August 2026

🎁⨥ ⸻ #𝐖.𝐈𝖠᪱𝐔𝗠𝖤᪵𝖫𝗟 ۫ 聞 ❜❜ ㅤ۫ ֺ รั命܉⃛ 🌟 ృᰰ ⃫ 𝐍.𝖠𝖵‌𝖨𝗚‌𝗔᷏𝗧؛‌𝗜𝖮‌𝖭‌🤍𝁙ㅤ ㅤׄ𑩑 𝐀‌𝖽𝗆‌᪱ ॼछׅ ▎𝐌𝗽ິ 𝗽𖦹𝗌𝗍🗝‌𝐌𝗽ິ 𝗶ṉ𝗳ᦢׁゝ︬ㅤ݃ 𝂅 ᄔㅤְㅤ 𝐁𖦹ᦢ𝗌𝗍 ✨ㅤ۫𝐁𝗈𝗍 ༶⃜🩹🩹🩹🩹 ⎯⎯ㅤִㅤ୨🤍୧ㅤִ ⎯⎯ ✚ | 🤩𝖯𝖱 𝐌᪵𝖺𝗇𐐼ׂ𝗀𝖾𝗋 ࣭. 🎁ㅤ 𓏫 𝅾𓈒 🥜 ◂ㅤ ‌ ⦇𝃚🩹 ㅤ࣭ ❛❛ 𓏢ꨭ ۭ ­­­ ­­­ࣰ ❀ܑ ­­🤩🤩 ࣪ ִ­­­ ­­­ ­­­ ✨. 𝇂💕 ‌ ‌ ‌‌ ‌‌ ‌ ‌ ‌‌ ‌‌ ‌ ‌ ‌‌ ‌‌ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ‌🌟🌟 ‌‌ ‌‌𖥔 ݁ ‌ ‌ ‌‌ ‌‌ ‌ ‌ ‌‌𓐄‌ ‌‌ 🤩 ‌ ‌‌ ‌‌ ּ ּ ‌ ‌ ‌ 𝐰 ‌ ‌ ‌‌ ‌‌ ‌ ‌ ‌‌

custom 530979741583281462410custom 53211146374779039678custom 54160832320451679438custom 54043360626989107792

5 Jul 2026, 17:34 UTC533 views45 reactionsread 8 August 2026
Photo

🦢🉆 𝔑𝔼𝖶 𝐫𝖾𝕧𝗂♱⁠⁠⁠⁠𝖾𝐰 ࣪❞ 🤩 ⑇ @Wiaumell 🎁 ᥀ 𝔓𝗈𝗂𝗇𝗍𝗌: [𝟫/10] 𝕀𝗇𝖿𝗈 🤩 𝐉𝗈𝗂𝗇 🤩𝖳𝗁𝖾𝗋𝖾 𝗂𝗌 𝗋𝖾𝗆𝗈𝗋𝗌𝖾 𝗂𝗇 𝖼𝗈𝗇𝖿𝖾𝗌𝗌𝗂𝗇𝗀 𝄒𝄒🌼🤩 ⁠⁠⁠ 𝐈𝗇𝐟𝗈 𝐂𝗁𝖺𝐧𝐧𝖾𝗅 : [𝟢𝟩/𝟣𝟢]🦷𝐀𝖼𝗍𝗂𝕧𝗂𝗍𝗒 [𝟢𝟪/𝟣𝟢] ㅤ ̣𝂅 ⃝🤩 𝂅 ̣ ℝ𝔈𝐀𝖣 𝖱𝔼𝔙𝖨𝐄𝖶ㅤ֔ ㅤ⠷ ㅤ늘ㅤㅤ݄ㅤ ❢ 𝐂𝗈𝗅𝗅𝖾𝕔𝗍𝗂𝗏𝐞 [𝟢𝟫/𝟣𝟢]🦷𝐀𝖽𝗆𝗂𝗇𝐢𝗌𝗍𝗋𝖺𝗍𝗂𝕠𝗇 [𝟢𝟨/𝟣𝟢] 🤩𝐭ɑ‌𝗀‌‌𝐬 : #review #flood 🤩 ❞ 🤩🤩 𝔗𝗁𝖾𝕣𝖾 𝗂𝗌 🤩🍼🤩 𝗇𝗈 𝖺𝗇𝗀𝖾𝗋 𝗂𝗇 𝕞𝗒 𝗌𝗈𝗎𝗅, 𝆹𝅥 𝆭 🤩🤩🤩 🤩🤩🤩 𝖿𝗈𝗋 𝖨 𝖺ຕ 𝖺 𝗀𝕠𝖽.

custom 532111463747790396713custom 534835490491206618413custom 541608323204516794313custom 54156247228114840315custom 53097974158328146241

Showing the 12 most recent of 20 posts we hold for @wiaumell. 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 — 473,074 of 1,478,351entries 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

Named by 6 registered channels — 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.

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

“⎯᜔⎯ֺ⃞ 𝂅 𝀜𝄆𝐃᷌᪾𝖾⃛𝗂𝗍ְ𝗒 ﹫𝖶ɪ𝖺᷎𝗎𑩑𝗆ְ᷽𝖾᷁𝗅𝗅𝅬] ֦ ྀི ⁠⁠⁠ ❩⁠⁠⁠⁠𝄢⨾ֵ─፝֟‌” (@wiaumell), 649 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/wiaumell.

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.