大家重新进一下群,人多准备发福利了 https://t.me/+mC2JFgF0HaQyMzM0
❤1
Signed 拾柒
Channel
@APl57
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
998subscribers
+266 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003389230091 |
|---|---|
| Type | Channel |
| Username | @APl57 |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/APl57 |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 23:57 | 998 | +274 |
| 9 Sept 2026, 04:40 | 724 | -5 |
| 22 Aug 2026, 07:59 | 729 | -3 |
| 21 Aug 2026, 22:00 | 732 | no change |
| 21 Aug 2026, 21:45 | 732 | first reading |
14 posts held, back to 17 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 14 posts for this entry, the most recent from 21 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
14 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 71.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 71.4% | |
| 👎 | 2 | 14.3% | |
| 🔥 | 1 | 7.14% | |
| 🤡 | 1 | 7.14% |
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 11 of the 14 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 17 August 2026 to 21 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.
大家重新进一下群,人多准备发福利了 https://t.me/+mC2JFgF0HaQyMzM0
❤1
Signed 拾柒
难道小辞加入了神秘的光明顶组织?
❤1
Signed 拾柒
小辞已经越来越神秘了
❤2
Signed 大爱仙尊 凭谁 @pingshei
有没有兄弟需要拜师或者学习配种的可以联系我 @Yzus8
❤1
Signed 神之一手
我要去抓包短信轰炸了有没有什么野鸡台子 算了不逗你们了我要开始怠惰了先休息一段时间最近吃的太撑了
Signed 小辞(怠惰中)
@cynsantanametgalabot 重启成功每人增加10轰炸配额+多并发进程5,一秒大概可以发5条轰炸 另外提示一下无法被轰炸的账号=已经触发限制24小时发送短信 这个月我奶奶发工资了随便轰炸账号暂时不缺米😁😁😁
🤡1
Signed 小辞
每日一篇最新战绩
Signed 小辞
需要合作的联系我稳定拉人头
Signed 小辞
好撑啊今天喝可乐喝多了
❤1🔥1
Signed 小辞
📊 SOSO 搜索曝光 HJ脚本专属分享群 🔥 近7天流量表现:TOP 6% 已超过 17,732 个同期获曝光群/频道 🌐 SOSO 全站近7天:约9,475万次搜索结果展示 👁 本频道近7天曝光:4.9 K ├ 频道卡片:384 └ 频道内容:4.5 K 今日截至 17:46:1.6 K 昨日:2.3 K 过去7天趋势 08/12 63(频道 63 · 内容 0) 08/13 51(频道 51 · 内容 0) 08/14 59(频道 59 · 内容 0) 08/15 71(频道 63 · 内容 8) 08/16 780(频道 45 · 内容 735) 08/17 2.3 K(频道 59 · 内容 2.2 K) 08/18 1.6 K(频道 44 · 内容 1.5 K) 口径:频道卡片或频道内容在 SOSO 搜索结果中实际展示一次,计一次曝光;同一用户多次看到会分别计数。内容曝光自 2026-08-11 起累计。
Signed 小辞
ps: 小辞爱情通知 明天2026年8月19号 是个特别隆重的日子 七夕节 要对自己的女朋友好一点哟
❤1👎1
Signed 小辞
@cynsantanametgalabot 你们无聊的可以前往轰炸机器人投稿电报账号
👎1
Signed 小辞
Showing the 12 most recent of 14 posts we hold for @APl57. 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.
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.
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.
@APl57 named 2 handles 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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“小辞的朋友圈(冲1k)” (@APl57), 998 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/APl57.
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.