Telegram RegisterThe public register of Telegram

Channel

明日🌀战记

@SZMRZJ

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

2,424subscribers

-12 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002612318029
TypeChannel
Username@SZMRZJ
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/SZMRZJ

Growth

2,4242,4362,4308 August 2026 — 2,436 subscribers8 August 2026 — 2,433 subscribers11 August 2026 — 2,428 subscribers15 August 2026 — 2,424 subscribers8 August 202615 August 2026
4 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 2,422–2,438 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 02:072,424-4
11 Aug 2026, 18:542,428-5
8 Aug 2026, 21:312,433-3
8 Aug 2026, 09:312,436first reading

Engagement

12 posts held, back to 24 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
30.2%
avg views ÷ 2,424 subscribers
Avg views / post
731
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 12 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 31 July 2026
Posts held12 (24 April 202631 July 2026)
Views total731
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 09:31 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
1m 54s
Average length
19s

Measured directly from 6 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

22 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 6181382928870674035836.4%
836.4%
👎418.2%
custom 521561858414689330414.55%
💩14.55%

Custom emoji. 2 of the rows above are 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 8 of the 12 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 22reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 24 April 2026 to 31 July 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

31 Jul 2026, 05:12 UTC731 viewsread 8 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_8186592298

1 Jul 2026, 05:08 UTC≈1,030 viewsread 8 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_8186592298

9 Jun 2026, 12:26 UTC≈1,310 views4 reactionsread 8 August 2026
Photo

那绰约的身姿,仅是背影便足以让人心驰神往。 只可惜,转身去,再不返,无归期。

👎2custom 61813829288706740352

5 Jun 2026, 14:58 UTC≈1,430 views4 reactionsread 8 August 2026
Photo

———— 奈雪 @aiwoganwo520 人照8.5分,淡妆,颜值耐看,07嫩妹,御萝类型,身高168这样,c奶子,屁股又大又翘,个子高骨架大,感觉不算胖有点肉感,正常肤色,抽烟的,胳膊有纹身。 战记侃车: 来到熟悉的地方,进门第一印象就是房间有点暗,妹妹穿着睡衣,真人没有频道照片那么惊艳,淡妆偏素颜,耐看类型,有点含蓄,轻声细语的,礼貌性给我拿了瓶水,聊了一会感觉性格挺好的,御萝音,话题挺多的,妹妹是广州人,说从小受环境因素却不会讲粤语但听得懂,一起抽了根烟聊了将近十分钟才开始,简单陪洗,到床上侧着身子聊骚话调情,口活深喉舔蛋,大腿内侧边舔边亲,挺舒服的,蛇管饱,一直伸出舌头要蛇吻,女上小菜鸡,敏感体易高潮,时不时身体抽搐,屌感还不错的,反馈夹着轻微的声音,不是很激烈但很真实,后入很爽,蜜桃臀,桩了半小时,最后实在干不动了,自个儿手打出嘢,情绪价值到位,没催没嫌弃,体验感满意,不足之处腿毛没脱干净有点扎,屁股略有生长纹,

3💩1

3 Jun 2026, 14:49 UTC≈1,450 viewsread 8 August 2026
Photo

———— 小甜 @T2002TRH 人照9分,真人比照片更自然好看一点,网红脸科技感十足,妆容打扮非常精致,皮肤偏白娇嫩,体高165左右,身材苗条筷子腿,C罩杯屁股翘,抽电子烟,腿部背部都有纹身。 战记侃车: 临时起意约的她,进门后野王小甜递瓶水给我,课室挺干净宽敞,ins风格,她很自然的打了招呼,像是老熟人一样跟我对话了几句,毫无违和感,给人一种很融洽的氛围,嫩妹的脸蛋,性格偏御姐,性格非常好,脱光后全身很纤细,皮肤嫩白,臀部有疤应该抽过脂,乳头粉嫩,奶子含有高科技,手感还行不算差,陪洗后穿上丝袜制服,口活很专业,舒服到我挑不出毛病,有舌吻69,小烧逼很粉嫩也很湿润,女上可以直接秒人,还好我瞬间憋住了换姿势,随便操盘,全程骚叫不断,又爸爸又老公又哥哥,让我同时担任多个角色艹她,情趣价值就非常到位的,事后给我上了一会政治课,受益良多,果然是吃鸡巴多过我吃饭。

23 May 2026, 15:39 UTC≈2,210 viewsread 8 August 2026

———— 乐宝 @lebaoa 人照8/9分左右,真人脸偏圆润点,淡妆,颜值因人而异,个人觉得还可以,身高应该不到160,小只马有肉感不胖,c奶子手感柔软,奶头确实很粉红,身体正常肤色,有点小肚子,有纹身不抽烟。 战记侃车: 听说上岸了,之前约的,开得少,确实很难才约上,好不容易约上后来到熟悉的地方(生态科技园),课室两房一厅环境干净宽敞,缺点洗澡房巨小,要是阿叔肥点的话两人挤不进去,洗澡挺仔细,有水中萧,穿上制服,有深喉舔蛋吸蛋,非常有技巧,很舒服,意想不到的居然是大蟒蛇,主动怼出舌头,能蛇到窒息那种,腹部有纹身,覆盖着一道长疤,基本看不出来,用手能感受到,做爱给到很好的反馈,女上很会,下面水很润,配合度很好,后入爽歪歪,臀部肉感足,总体验很是可以的,话唠,态度性格不错的妹子,身上略有风尘味。

20 May 2026, 18:39 UTC≈1,720 views4 reactionsread 8 August 2026
Photo

人间纵有百媚千红,唯独你是情之所钟,乌啄啄兮乌啄啄,爱你是假的,日你才是真的。

custom 61813829288706740354

12 May 2026, 15:42 UTC≈3,240 views4 reactionsread 8 August 2026

———— 小君君 @junjun1269 人照8/9分吧,脸蛋圆润的,淡妆,看起来很娇嫩,身高160打下,身材微坦,肉感足,d大奶,腰粗屁股大,黄皮,肚子三层肉,无纹身。 战记侃车: 听说是萝莉嫩妹,拿了张工兵券就预约妹妹了,果然不出意料,当工兵确实不好,提前到达,直接原地罚站一节课时间,楼下喂饱蚊子后才遥控上房间,环境还行,有点儿乱,妹妹穿着花裙子,穿在她那微坦的身躯并不惊艳,进来后招呼都没有打,还没有坐下来直接问我先付钱,刚付好说她自己洗过了直接叫我自己去洗!在楼下罚站就已经很委屈了,上到来这服务态度,令我更憋屈了,洗好上床就口了几下就带套女上,无蛇无69,屌感还行,奶子挺大的,一只手抓不完,之后换了好几个姿势,反馈一般,全程那个脸一直扭到另一边去,也不知道看啥,委屈的桩了半小时,最后选择后入出水算了,总之毫无欲望与情绪价值。

3custom 52156185841468933041

10 May 2026, 08:18 UTC≈2,840 views2 reactionsread 8 August 2026
Video

———— 沙沙 @hghyge 人照8分,妆容打扮还可以,御姐类型,车模身材,身高有170以上,大长腿,B奶子,正常肤色,人工白虎。 战记侃车: 身穿一套长裙,老师现实并没有照片那么光滑,较粗糙,偏成熟,感觉是少妇,课室在万科,课室单间,环境挺好,隔音还行,洗澡房有点小,老师态度是真的非常好,有耐心会聊天,温柔御姐,服务不差事,该有都有,前后都有陪洗,蛇吻六九,口活舒服还舔蛋吸蛋,会的都会,配合度高,后入体验感觉最好,敏感水多,屌感好。

👎2

7 May 2026, 07:14 UTC≈1,980 views2 reactionsread 8 August 2026
Video

每一次的升华,都是对美好的不懈追求。

custom 61813829288706740352

4 May 2026, 07:56 UTC≈2,080 views2 reactionsread 8 August 2026
Photo

每一次的见面,每一次的交融,都是爱的升华。

2

24 Apr 2026, 16:06 UTC≈2,570 views0 reactionsread 8 August 2026
Photo

桩了小骚桐40分钟,完事后还请我喝奶茶~~~ 真的炒鸡好一个妹妹。

Showing the 12 most recent of 12 posts we hold for @SZMRZJ. 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 — 1,346,678 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.

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

“明日🌀战记” (@SZMRZJ), 2,424 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/SZMRZJ.

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.