宝宝们,今天满位,路过带关注一下,再约明天的

Channel
潮喷💦SM👠剧情📸道具
@qyr5455
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
13,490subscribers
+3,581 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002546892594 |
|---|---|
| Type | Channel |
| Username | @qyr5455 |
| Description | 福利视频 @wtr2425 约课联系 @ranran948 双向联系 @qt6857_bot |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/qyr5455 |
Topic
Adult — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 22:26 | 13,490 | +5,052 |
| 2 Nov 2026, 19:01 | 8,438 | -33 |
| 31 Oct 2026, 01:57 | 8,471 | -117 |
| 27 Oct 2026, 17:00 | 8,588 | -56 |
| 24 Oct 2026, 17:16 | 8,644 | -89 |
| 21 Oct 2026, 21:48 | 8,733 | -155 |
| 18 Oct 2026, 09:00 | 8,888 | -59 |
| 15 Oct 2026, 03:31 | 8,947 | -97 |
| 12 Oct 2026, 04:00 | 9,044 | +394 |
| 5 Oct 2026, 15:22 | 8,650 | -235 |
| 27 Sept 2026, 12:36 | 8,885 | -176 |
| 17 Sept 2026, 23:17 | 9,061 | -217 |
| 13 Sept 2026, 08:38 | 9,278 | -205 |
| 9 Sept 2026, 05:36 | 9,483 | +270 |
| 3 Sept 2026, 22:18 | 9,213 | +25 |
| 31 Aug 2026, 22:14 | 9,188 | -16 |
| 28 Aug 2026, 17:55 | 9,204 | -24 |
| 25 Aug 2026, 23:43 | 9,228 | -85 |
| 23 Aug 2026, 03:53 | 9,313 | -118 |
| 19 Aug 2026, 15:26 | 9,431 | first reading |
Engagement
69 posts held, back to 1 August 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 45 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 22.2%
- avg views ÷ 13,490 subscribers
- Avg views / post
- 3,000
- 19 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 69 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.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 69 (1 August 2026 – 5 November 2026) |
| Views total | 56,974 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 01:39 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
- 75
- Videos
- 12
- Links
- 15
Lifetime counters from Telegram’s own channel header, read 6 November 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
- 22s
- Average length
- 11s
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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
开课6点有位
宝宝们。今天满位了 预约明天位置
#南山 冉冉 @ranran948 200 优惠券*5张 领取方式:转发此条信息给老师 领取优惠券需写报告,报告区有模板:https://t.me/szzzbgq
宝宝们,今天满位,路过带关注一下,再约明天的
开课
Photo, posted without a caption
开课
宝宝们,今天满位,路过带关注一下,再约明天的
Video, posted without a caption
#南山冉冉 10月27日荣登深圳学院名师榜👑 ❤️名师榜: @sz520 ❤️聊天群: @sz1314 ❤️ 郑重承诺: 高质量/真老师/真学生/活跃社区,若您在【深圳学院】联系的老师货不对板,被骗定金,群主: @sz333 担保赔付!每月赞助万元出击费🧧 立即加入 👆 查看评价
开课
Showing the 12 most recent of 69 posts we hold for @qyr5455. 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.
Posts recorded as deleted after publishing
We recorded 7 posts on @qyr5455 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 7 August 2026
- Most recent seen missing
- 5 November 2026
- Median time before seen missing
- 25 hours
- Seen missing in the last 30 days
- 2
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 24 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.
@Szxiuchehui · 43,3734 postsLotteryBest抽奖导航
@lotterynav · 193,0643 posts深圳名师天团资源榜
@SZMSTTPD · 28,3933 posts花满楼资源频道
@hmlzyb · 29,4172 posts隔壁老王的回忆录
@lwgeo · 8,9592 posts深圳出击俱乐部认证榜
@RomanceofWindbaby · 20,3192 posts深圳三和修车大队-【嫩妹御姐资源】
@SZ_3hdsbd · 64,2632 posts深圳嫩妹茶探府【修车榜单】
@SZ_nmctf9 · 33,6722 posts深圳茶馆榜
@szcg6 · 42,7922 posts深圳枫林榜 @szflw
@szflwbd · 43,3442 posts深圳奥迪RS修车俱乐部【修车榜单】
@szxcaodi18 · 28,6892 posts深圳榨汁选妃区
@szzz_xfq · 29,5572 posts深圳【汤臣一品】精选榜
@tcypa5 · 42,6522 posts朝花夕拾频道
@ZHXSChannel · 27,5302 posts深圳800神教工兵榜
@GDPSZ · 14,1991 post深圳欢乐谷【公开榜】
@HLGGB · 24,2341 post深圳狼友公开资源
@s88888w · 31,2981 post深圳修车公开榜
@shenzhenzuiquan · 10,4741 post深圳三和修车大队【南山区】
@Sz3hdsnsq · 6,0311 post深圳三和修车大队-【选妃榜单】
@SZ_shcjzl · 39,6261 post深圳修车大队LY之声
@szlym · 10,9441 postDale
@XSJYYZ888 · 51 post深圳新世界已验证(精选榜)
@XSJZZZ888 · 28,4991 post深圳911(认证榜)
@Yuoyoutan · 101,4011 post
Names
Channels on the register whose handles appear in this channel's posts.
@jimu · 100,4506 posts深圳【皮卡丘】报告榜🅥
@PKQBG · 2,3722 posts深圳【皮卡丘】闲聊群🅥
@SZPKQ · 24,3162 posts深圳学院必吃榜
@c8028 · 2,6761 post【集美师大】深圳校区
@JMNUSZ · 6,8241 post【集美师大】深圳校区学生会
@jmsdxsh · 4,0961 postLotteryBest Bot
@LotteryBestBot · 108,7181 postLotteryBest抽奖导航
@lotterynav · 193,0641 post隔壁老王的回忆录
@lwgeo · 8,9591 post深圳修车大队
@lwheibang · 15,5411 post深圳优选娱乐榜💥
@MKKGT7 · 5,1871 post深圳学院
@sz0755 · 31,4831 post深圳【皮卡丘】公开榜🅥
@SZPKQ888 · 40,3061 post深圳学院名师榜 @sz520
@szxymsb · 50,1451 post深圳榨汁报告区
@zzddbg · 11,5891 post
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
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@qyr5455 named 1 handle 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 4 November 2026 – 4 November 2026 · confirmed gone 22 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“潮喷💦SM👠剧情📸道具” (@qyr5455), 13,490 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/qyr5455.
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.