Telegram RegisterThe public register of Telegram
Telegram profile photo for The Masked Dev

Channel

The Masked Dev

@TheMasked_Dev

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,858subscribers

+1,794 since we began measuring on 25 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1004368524915
TypeChannel
Username@TheMasked_Dev
Created24 August 2026measured — dated from the channel’s first post
First recorded25 August 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/TheMasked_Dev

Topic

Gaming — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

641,9751,019.525 August 2026 — 64 subscribers26 August 2026 — 125 subscribers2 September 2026 — 873 subscribers11 September 2026 — 1,853 subscribers14 September 2026 — 1,975 subscribers19 September 2026 — 1,858 subscribers1,85825 August 202619 September 2026
6 measurements spanning 25 days, net +1,794. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 14:221,858-117
14 Sept 2026, 18:201,975+122
11 Sept 2026, 06:211,853+980
2 Sept 2026, 00:26873+748
26 Aug 2026, 01:45125+61
25 Aug 2026, 04:0064first reading

Engagement

11 posts held, back to 24 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.76%
avg views ÷ 1,858 subscribers
Avg views / post
69.9
10 posts measured
Reaction rate
12.9%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 25 August 2026
Posts held11 (24 August 202625 August 2026)
Views total699
Reactions total90
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Aug 2026, 04:00 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

90 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 28.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54065741272071880102628.9%
custom 52427268672360428962527.8%
custom 62310859912270335751516.7%
custom 53728465693704315581011.1%
custom 543149631489232933066.67%
custom 524274405999013000255.56%
custom 524265709549231984233.33%

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 are Telegram’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 10 of the 11 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 90 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 24 August 2026 to 25 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

25 Aug 2026, 03:33 UTC28 views4 reactionsread 25 August 2026

Btw, did you guys hear that Scanner upgrades in Asteroid Shiba will be limited in Season 2? 🙃 🐶 I want to create real scarcity and increase the value of the product. For example, unlocking a Level 8-10 Scanner won’t be easy - players will have to wait for limited upgrade opportunities. So if you joined in Season 1, you’re actually sitting on a pretty nice advantage. Early players got lucky 🙂

custom 52426570954923198422custom 52427440599901300021custom 54314963148923293301

25 Aug 2026, 03:25 UTC31 views5 reactionsread 25 August 2026
Photo

GM. Today we’re shipping updates for Asteroid Shiba 👀 Also, my Korean frens just brought a collab opportunity with a Korean game. Looks like Season 2 is about to get seriously spicy 🌶️ 🙃

custom 54314963148923293303custom 52427268672360428962

25 Aug 2026, 02:47 UTC47 views4 reactionsread 25 August 2026

$BTC 81k 🪐

custom 52427268672360428962custom 52426570954923198421custom 53728465693704315581

24 Aug 2026, 22:37 UTC67 views15 reactionsread 25 August 2026

🙃 By the way, for those curious about my GameFi background - some time ago, I was actively involved in helping establish Fableborne in the market, a project that’s still going strong today. Some of the marketing strategies and tactics I’m using today were actually tested and refined by me back then. Consider this a little piece of alpha about my background.

custom 53728465693704315587custom 52427268672360428964custom 52427440599901300024

24 Aug 2026, 22:28 UTC68 views8 reactionsread 25 August 2026
Photo

Shiba Alpha Base is almost ready to welcome its first guests 🍸

custom 52427268672360428966custom 54314963148923293302

24 Aug 2026, 21:43 UTC101 views17 reactionsread 25 August 2026
Photo

The dev keeps an eye on the Asteroid Shiba community chat and reads all your comments

custom 54065741272071880108custom 52427268672360428967custom 53728465693704315582

24 Aug 2026, 21:39 UTC91 views10 reactionsread 25 August 2026

That means you’ll hear about the important stuff before everyone else

custom 62310859912270335756custom 52427268672360428964

24 Aug 2026, 21:38 UTC91 views6 reactionsread 25 August 2026

There aren’t many of us here yet - but maybe that’s exactly how it should be 👀

custom 54065741272071880106

24 Aug 2026, 20:43 UTC89 views12 reactionsread 25 August 2026

I’m dropping alpha here. Who’s with me? 👀🔥

custom 540657412720718801012

24 Aug 2026, 20:39 UTC86 views9 reactionsread 25 August 2026

Behind Asteroid Shiba Building GameFi Launching trends 🦍

custom 62310859912270335759

Showing the 11 most recent of 11 posts we hold for @TheMasked_Dev. 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.

Mentions

Named by 1 registered channel — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“The Masked Dev” (@TheMasked_Dev), 1,858 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/TheMasked_Dev.

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.