Telegram RegisterThe public register of Telegram

Channel

𝑴𝑨𝑫 𝑭𝑹𝑬𝑬𝑫𝑶𝑴.

@Weaseley

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

41subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003658748786
TypeChannel
Username@Weaseley
Description@mad1nf0 𝑰𝑵𝑭𝑶 @stofeel_bot 𝑩𝑶𝑵𝑫 @seraphimweasley 𝑻𝑾𝑰𝑵
Created24 February 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/Weaseley

Growth

4113 Aug 2026, 18:04 — 41 subscribers13 Aug 2026, 18:15 — 41 subscribers13 Aug 2026, 18:0413 Aug 2026, 18:15
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 40–42 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 18:1541no change
13 Aug 2026, 18:0441first reading

Engagement

8 posts held, back to 24 February 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
53.7%
avg views ÷ 41 subscribers
Avg views / post
22.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 8 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 3 August 2026
Posts held8 (24 February 20263 August 2026)
Views total22
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 18:15 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
5
Links
5

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

Reaction mix

123 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53727987706793918614133.3%
custom 52266016487464187863125.2%
custom 53975770898450641223024.4%
custom 53440248090785311262117.1%

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

Measured over the 8 most recent posts we hold, published 24 February 2026 to 3 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.

Recent posts

10 Mar 2026, 23:43 UTC355 views21 reactionsread 13 August 2026
File

File, posted without a caption

custom 52266016487464187868custom 53727987706793918618custom 53975770898450641223custom 53440248090785311262

10 Mar 2026, 23:42 UTC349 views41 reactionsread 13 August 2026
Photo

🐉 🌟🌟🌟🌟🌟 🌟🌟🌟 🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🐉🐉🐉🐉🐉 #𝑻𝑹𝑰𝑪𝑲🐉🐉🐉🐉🐉 Грохочет гром. Сверкает молния в ночи. А на холме стоит безумец и кричит: "Сейчас поймаю тебя в сумку, и сверкать ты будешь в ней. Мне так хочется, чтоб стала ты моей!" 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 — 🌟 меня родилась гениальная идея…— Горящие глаза близнеца устремились к яркой вспышке, осветившей тёмные облака. — 🌟дача любит безрассудных, — улавливая мысль Фреда, он довольн

custom 537279877067939186114custom 522660164874641878611custom 539757708984506412210custom 53440248090785311266

9 Mar 2026, 01:46 UTC269 views13 reactionsread 13 August 2026
Photo

🐉 🌟🌟🌟🌟🌟🐉🌟🌟🌟 🌟🐉🌟🌟🌟🐉🌟🌟🌟🌟🌟 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🐉🐉🐉🐉🐉 #𝑻𝑹𝑰𝑪𝑲🐉🐉🐉🐉🐉 🔤🌟риходи сегодня в раздевалку Гриффиндора в семь вечера. 🐉🐉🐉🐉🐉Джордж Уизли.🔤 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 — 🌟олько не говори, что мы собрались летать в темноте… — 🌟ы собрались летать в темноте, — серьёзно подтвердил Джордж. — Но не просто летать. Я обещаю экскурсию. Самую лучшую. С комментариями.

custom 53727987706793918615custom 53440248090785311264custom 53975770898450641224

3 Mar 2026, 19:49 UTC302 views17 reactionsread 13 August 2026
Photo

🌟🌟🌟🌟🌟🌟🌟🌟🌟 🐉🐉🐉🐉🌟🌟🌟🌟🌟🌟🌟 🐉🐉🐉🐉🐉🔤 🐉🐉🌟🌟🌟🌟🌟 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 𝑨𝑵𝑶𝑵𝒀𝑴𝑶𝑼𝑺 𝑴𝑬𝑺𝑺𝑨𝑮𝑬𝑺. Черкани что-нибудь что ли. Не время для сна в такую прекрасную ночь для шалостей. 🐉🐉🐉🤩🤩🤩🤩 🐉🐉🐉🐉🤩🤩 🐉🐉🐉🐉🐉🐉🐉𝑩𝑶𝑶𝑺𝑻.

custom 52266016487464187865custom 53727987706793918615custom 53975770898450641225custom 53440248090785311262

3 Mar 2026, 19:42 UTC266 views17 reactionsread 13 August 2026
Photo

🌟🌟🌟🌟🌟🌟🌟 🐉🐉🐉🐉🐉🐉🐉🌟🌟🌟🌟 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 Даже среди вечной путаницы и суматохи пробираются яркие лучи спокойствия и умиротворения. Только все забывают, что этому ритму жизни помешаем мы с Фредом! Всего несколько условий, чтобы обрести нового друга в лице меня! Уверяю, вредилки не окажутся у тебя под подушкой. Сегодня). Коннекты будут размещены здесь. 🔗Я единственный Джордж в листе коннектов. Если желаете принять Фреда или

custom 53440248090785311266custom 53727987706793918615custom 53975770898450641224custom 52266016487464187862

3 Mar 2026, 19:20 UTC259 views14 reactionsread 13 August 2026
Photo

🐉🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🤩 𝙈𝙧. 𝙒𝙚𝙖𝙨𝙡𝙚𝙮! 𝘾𝙤𝙢𝙚 𝙩𝙤 𝙢𝙮 🤩 𝙤𝙛𝙛𝙞𝙘𝙚 𝙣𝙤𝙬! 𝙂𝙧𝙮𝙛𝙛𝙞𝙣𝙙𝙤𝙧 𝙝𝙖𝙨 🤩 𝙢𝙞𝙣𝙪𝙨 𝟏𝟓 𝙥𝙤𝙞𝙣𝙩𝙨. Наши имена знает каждый, фамилия Уизли звучит во всех разговорах. Я — Джордж Уизли. Желаешь погрузиться с головой в наши проказы? Пристегнись покрепче, здесь нет места трусливым. Правила созданы для того, чтобы их нарушать, верно? Но даже в хаосе должен быть порядок. Поэтому для удобства я сделал следующее: #𝑨𝑵𝑨𝑹𝑪𝑯𝒀

custom 52266016487464187865custom 53727987706793918614custom 53975770898450641224custom 53440248090785311261

Showing the 8 most recent of 8 posts we hold for @Weaseley. 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 — 763,302 of 1,350,102entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“𝑴𝑨𝑫 𝑭𝑹𝑬𝑬𝑫𝑶𝑴.” (@Weaseley), 41 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Weaseley.

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.