Telegram RegisterThe public register of Telegram
Telegram profile photo for 每日大赛

Channel

每日大赛

@Main777NB

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

4,090subscribers

+144 since we began measuring on 17 August 2026

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

Register entry

Telegram ID-1003770977811
TypeChannel
Username@Main777NB
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live8 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/Main777NB

Growth

3,9464,0944,02017 August 2026 — 3,946 subscribers17 August 2026 — 3,946 subscribers20 August 2026 — 4,009 subscribers24 August 2026 — 4,028 subscribers27 August 2026 — 4,046 subscribers30 August 2026 — 4,084 subscribers2 September 2026 — 4,094 subscribers8 September 2026 — 4,090 subscribers4,09017 August 20268 September 2026
8 measurements spanning 22 days, net +144. 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 3,924–4,116 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 16:144,090-4
2 Sept 2026, 23:564,094+10
30 Aug 2026, 11:544,084+38
27 Aug 2026, 02:284,046+18
24 Aug 2026, 12:344,028+19
20 Aug 2026, 17:584,009+63
17 Aug 2026, 19:153,946no change
17 Aug 2026, 19:003,946first reading

Engagement

20 posts held, back to 13 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
23.4%
avg views ÷ 4,090 subscribers
Avg views / post
958
20 posts measured
Reaction rate
1.08%
reactions ÷ views · ER floor
Posts in window
20
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 August 2026
Posts held20 (13 August 202617 August 2026)
Views total19,153
Reactions total207
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Aug 2026, 19: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

Video runtime
2m 42s
Average length
1m 21s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

207 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 82.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍17082.1%
🍌115.31%
83.86%
🤔73.38%
😱52.42%
🌚20.966%
🔥10.483%
😁10.483%
😭10.483%
🥰10.483%

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 20 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 207 reactions 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 13 August 2026 to 17 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

17 Aug 2026, 13:46 UTC180 views10 reactionsread 17 August 2026
Forwarded from @KGNB333File

自动秒吃 自动回血 部分用户依旧玩不了 统一使用跨进程迷你世界

👍8🌚2

16 Aug 2026, 19:21 UTC744 views12 reactionsread 17 August 2026
File

●AI改编成自己配置DeepSeekAPI官方不在提供API

👍10🍌1😁1

16 Aug 2026, 17:47 UTC≈1,160 views11 reactionsread 17 August 2026
File

●新增打开工匠台 ●新增去除天空盒 ●新增自动抢红包 ●新增追踪云服玩家 ●新增恢复信誉分 ●新增第一格修理物品 ●新增云服秒吃 ●AI改编成自己配置DeepSeekAPI官方不在提供API

👍8🍌2🥰1

16 Aug 2026, 16:52 UTC780 views10 reactionsread 17 August 2026

我们可能将在8.19日进行付费模式,如果您并没有能力赞助付费项目,没有关系小梦等你们回来,希望这段公益期间你们也能喜欢我们的项目,希望没有能力的用户在这段时间大家可以找到免费替代品,也感谢愿意支持付费项目的用户

👍10

16 Aug 2026, 11:34 UTC890 views19 reactionsread 17 August 2026

梦之初/梦之喵羽的AI已经无力偿还提供免费API因为后台欠费了,后期改成请你们自己提供API使用ai

👍15🤔21😭1

16 Aug 2026, 10:17 UTC916 views12 reactionsread 17 August 2026

说我找人给钱宣传梦之喵羽的,你得看看我也没有钱给才行

👍102

15 Aug 2026, 14:46 UTC≈1,100 views11 reactionsread 17 August 2026
Video

梦之初免框架UID用法.mp4 这个需要一定的智商,还有不是适配全机型,实在不行用框架,搭配梦之初专属包就可以使用uid免框架脑残别用了看也看不会

👍11

15 Aug 2026, 14:32 UTC769 views7 reactionsread 17 August 2026
Forwarded from @KGNB333File

修复云服崩溃 Root框架用户依旧玩不了

👍6🔥1

Showing the 12 most recent of 20 posts we hold for @Main777NB. 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.

Forward network

Republished by

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“每日大赛” (@Main777NB), 4,090 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/Main777NB.

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.