头课

Channel
羊羊的朋友圈
@qeds55
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
295subscribers
+254 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004332028324 |
|---|---|
| Type | Channel |
| Username | @qeds55 |
| Created | 1 August 2026 — measured — dated from the channel’s first post |
| First recorded | 28 August 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/qeds55 |
Topic
Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Oct 2026, 05:51 | 295 | -8 |
| 11 Oct 2026, 22:18 | 303 | +2 |
| 30 Sept 2026, 15:41 | 301 | +70 |
| 12 Sept 2026, 09:39 | 231 | +20 |
| 4 Sept 2026, 15:00 | 211 | +95 |
| 28 Aug 2026, 21:05 | 116 | +75 |
| 28 Aug 2026, 08:45 | 41 | first reading |
Engagement
16 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 35s
- Average length
- 18s
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
https://t.me/sz_papapa777/4286
🎰 龙华羊羊半价 📮 参与条件: 🎫 加入-羊羊的朋友圈 🎫 加入-深圳嫩妹修车团【轮播群】 🎫 加入-深圳嫩妹修车团【报告】 🎫 加入-深圳嫩妹修车团【榜单】 🎫 加入-深圳嫩妹修车团【免费上榜】 🎁 奖品内容: 💰️ 单p半价优惠券 × 1 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月31日 16时06分00秒
🎰 龙华羊羊半价 📮 参与条件: 🎫 加入-羊羊的朋友圈 🎫 加入-深圳修车军团【轮播群】 🎫 加入-深圳修车军团【验证榜单】 🎫 加入-深圳修车军团【修车报告】 🎫 加入-深圳修车军团【免费上榜】 🎁 奖品内容: 💰️ P半价优惠券 × 1 ⚠️ 抽奖说明: 三天后开奖 需要填写出击报告 半价有效期5天 中奖者请尽快兑奖 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月31日 12时33分00秒
🎉 龙华羊羊五折券抽奖 🎁 奖品清单 • p五折券 https://t.me/Sz2TB/7501 × 1 • 1000淘金币 × 1 🛡️ 参与条件 • 加入 深圳淘宝修车团 • 加入 羊羊的朋友圈 • 加入 深圳淘宝修车团(备用) • 加入 深圳淘宝修车收集录 • 加入 深圳淘宝精选轮播 • 必须设置用户名 🔮 祝福加持 • 祝福消耗:10淘金币 • 祝福上限:无上限次 • 祝福一次增加一个抽奖号,提高中奖率 • 幸运值祝福:支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-31 14:00:00 📜 抽奖说明 中奖不可买卖,五折券有效期五天,过期回收群里积分兑换。 ✨ 愿命运之剑指引你们前行,直至胜利之光照耀每一个人。
Photo, posted without a caption
有宝宝来的嘛
Channel name was changed to «羊羊的朋友圈»
开课了
下课了
Channel name was changed to «小七的朋友圈»
头课哦 看哪位宝宝先来
Showing the 12 most recent of 16 posts we hold for @qeds55. 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 7 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.
Names
Channels on the register whose handles appear in this channel's posts.
@lotterynav · 187,2392 posts深圳嫩妹修车团【榜单】
@sz_papapa777 · 45,4562 posts阿瓦隆通知站
@AvalonNote · 1,7941 post深圳修车军团【修车报告】
@shenzhen_xcbg · 11,8321 post深圳修车军团【验证榜单】
@shenzhen_xcjt · 53,8511 post深圳淘宝修车收集录
@Sz2TB · 25,2761 post深圳淘宝精选轮播
@Sz3TB · 7,4101 post深圳淘宝修车团(备用)
@SZ4TB · 5,3371 post深圳修车军团【轮播群】
@SZ_juntuanlb · 15,1211 post深圳嫩妹修车团【报告】
@sz_papapa666 · 9,7901 post深圳嫩妹修车团【免费上榜】
@sz_papapa888 · 33,8451 post深圳嫩妹修车团【轮播群】
@sznmxiuche · 10,0861 post深圳修车军团【免费上榜】
@SZxiuche_jt · 44,8871 post深圳淘宝修车团
@xiuchegbdd · 35,1151 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.
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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“羊羊的朋友圈” (@qeds55), 295 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/qeds55.
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.