2 measurements taken within a single day, net -1. 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 255–256 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Aug 2026, 00:43
255
-1
7 Aug 2026, 03:46
256
first reading
Engagement
20 posts held, back to 1 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
24.6%
avg views ÷ 255 subscribers
Avg views / post
62.8
11 posts measured
Reaction rate
6.22%
reactions ÷ views · ER floor
Posts in window
12
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 3 of 11 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 3 August 2026
Posts held
20 (1 July 2026 – 3 August 2026)
Views total
691
Reactions total
12
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 03:46 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
49 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 34.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🙏
17
34.7%
🆒
10
20.4%
😭
7
14.3%
😇
6
12.2%
🐳
5
10.2%
😎
4
8.16%
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 8 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 49reactions 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 1 July 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.
🐾🖤🖤🖤🖤➿#ПерсонажУходит
ㅤㅤ Нашу коллекцию покидает..
ㅤㅤ✨Чейз МакКейн из набора LEGO City Adventures.
ㅤㅤ Пока-пока! Удачи ему в новых приключениях в другом месте..
💤 🖤🖤🖤🖤➿ #рест ;;
ㅤㅤ Кажется, кое-кто нуждается в небольшом отпуске...
ㅤㅤㅤㅤ 🖤МК уходит в рест на 1 неделю.
ㅤㅤ Отдохни хорошенько, мы будем с нетерпением ждать твоего возвращения!
🌟❌😈🤩𝒯𝒲/𝒞𝒲: колбаса🤩🌟
😻 😈еужели это в самом деле...⬇️
⭐️😈🤩🤩🤩🤩😈🤩
🌟🥹 😈абыв про предрассудки и жажду крови, в этот светлый день @legoprojectsetc и @darknetlego объеденили себя узами брака, поклявшись в верной любви и в том, что до конца своих лет они не съедят друг друга!🥹🌟
💤 🖤🖤🖤🖤➿ #рест ;;
ㅤㅤ Кажется, кое-кто нуждается в небольшом отпуске...
ㅤㅤㅤㅤ 🖤Типпи Дорман уходит в рест до 13 августа.
ㅤㅤ Отдохни хорошенько, мы будем с нетерпением ждать твоего возвращения!
💤 🖤🖤🖤🖤➿ #рест ;;
ㅤㅤ Кажется, кое-кто нуждается в небольшом отпуске...
ㅤㅤㅤㅤ 🖤Ава Прентис уходит в рест до 31 июля.
ㅤㅤ Отдохни хорошенько, мы будем с нетерпением ждать твоего возвращения!
💤 🖤🖤🖤🖤➿ #рест ;;
ㅤㅤ Кажется, кое-кто нуждается в небольшом отпуске...
ㅤㅤㅤㅤ 🖤Нейси уходит в рест до 25 июля.
ㅤㅤ Отдохни хорошенько, мы будем с нетерпением ждать твоего возвращения!
Showing the 12 most recent of 20 posts we hold for @legoprojectsetc. 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 — 44,951 of 1,151,006entries 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 16 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@legoprojectsetc named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@charlotte_lp named in 2 posts, 8 August 2026 – 8 August 2026
@chasemccain_lego_projects named in 1 post, 8 August 2026 – 8 August 2026
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 8 August 2026 — this
entry's latest reading, not the date you are reading this.
“▸ 𝙇𝙀𝙂𝙊 𝙋𝙍𝙊𝙅𝙀𝘾𝙏𝙎 сетка 🌐” (@legoprojectsetc), 255 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/legoprojectsetc.
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.
