Telegram RegisterThe public register of Telegram
Telegram profile photo for 七宝18岁

Channel

七宝18岁

@weeeerewrtttty

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

307subscribers

+0 since we began measuring on 26 September 2026

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

Register entry

Telegram ID-1004427913797
TypeChannel
Username@weeeerewrtttty
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 September 2026
Last confirmed live26 September 2026
Measurements held2
On Telegramt.me/weeeerewrtttty

Growth

30726 Sept 2026, 21:47 — 307 subscribers26 Sept 2026, 22:22 — 307 subscribers26 Sept 2026, 21:4726 Sept 2026, 22:22
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 306–308 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 22:22307no change
26 Sept 2026, 21:47307first reading

Engagement

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

ERR · 30 days
82.1%
avg views ÷ 307 subscribers
Avg views / post
252
10 posts measured
Reaction rate
0.166%
reactions ÷ views · ER floor
Posts in window
10
of 10 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 4 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 September 2026
Posts held10 (25 September 2026 – 26 September 2026)
Views total2,522
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 22:22 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
50
Videos
19
Links
15

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

Video runtime
12s
Average length
6s

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

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.0%

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

Measured over the 10 most recent posts we hold, published 25 September 2026 to 26 September 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

26 Sept 2026, 05:58 UTC243 viewsread 26 September 2026
Forwarded from @yishuxuey

@#报告模板 【所属群组】东莞学生会 【所在地区】虎门 【老师艺名】七宝 【联系方式】@bgghjgffgjjhg 【验证留名】ggujhg 【验证日期】9+25 【上课价位】600 【人照几分】10 【服务过程】是朋友推荐的,今天有空,马上约好时间 进门第一眼看到就喜欢,皮白.细腰,完全是女朋友感,在陪我洗干净身体之后,这双长腿简直让我欲罢不能的节奏,我们两个人抱在一起,皮肤的接触碰把我下半身刺激到了最大限度,进入老师最温暖的那个地方,很舒服很爽,熊很挺拔,奶头很小,很粉,当看3点粉的逼逼立刻瞄准洞口一插到底,加大力度使劲抽插,听着老师娇滴滴的呻吟声让荷尔蒙猛冲,感觉瞬间好有征服欲,让人想要好好疼爱一番,下面超紧,水也很多,妹子被我干软了,好久没有这种感觉了,妹子身材很好,皮肤滑嫩,水特别多,给人一种飘飘欲仙的感觉,下次一定还来 支持匿名报告,匿名需要花费200积分隐藏ID。(积分多此举是为了避免恶意刷好评或者差评…

26 Sept 2026, 04:47 UTC221 views1 reactionsread 26 September 2026
Photo

#虎门 七宝 600一 1200二 电报: @bgghjgffgjjhg 频道: https://t.me/weeeerewrtttty 双向:@vggjgdfuujbnggukbot 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

❤1

26 Sept 2026, 04:40 UTC257 viewsread 26 September 2026

哥哥们,我上了这几天班。大家都喜欢。劝我接受舌吻。妹妹豁出去了。来吧。现在开始,我可以舌吻。

25 Sept 2026, 07:03 UTC348 views0 reactionsread 26 September 2026
Forwarded from @yishuxuey

@#报告模板 【所属群组】东莞学生会 【所在地区】虎门 【老师艺名】七宝 【联系方式】@bgghjgffgjjhg 【验证留名】cvbbbnn 【验证日期】9-24 【上课价位】600 【人照几分】10 【服务过程】 提前约好小姐姐按时到达地,位置好找,直接上楼小姐姐老师留着门。看见小姐姐身材相当不错,说话温柔,带我进浴室,陪洗,从上到下老师都给我洗的很认真,比较爱干净的老师。洗好老师还给用一次性毛巾给我擦干。来到床上老师给我正反面来了个遍。想要的服务都很不错,🐍的…

25 Sept 2026, 05:05 UTC298 viewsread 26 September 2026
Photo

#虎门 七宝 600一 1200二 电报: @bgghjgffgjjhg 频道: https://t.me/weeeerewrtttty 双向:@vggjgdfuujbnggukbot 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

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

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.

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.

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

“七宝18岁” (@weeeerewrtttty), 307 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/weeeerewrtttty.

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.