Telegram RegisterThe public register of Telegram
Telegram profile photo for 稳健115小喇叭

Channel

稳健115小喇叭

@wenjian115laba

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

716subscribers

+144 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003896474964
TypeChannel
Username@wenjian115laba
Created19 March 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/wenjian115laba

Topic

Technology — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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

5727166447 August 2026 — 572 subscribers7 August 2026 — 572 subscribers7 August 2026 — 573 subscribers15 August 2026 — 587 subscribers23 August 2026 — 617 subscribers30 August 2026 — 645 subscribers9 September 2026 — 684 subscribers16 September 2026 — 716 subscribers7 August 202616 September 2026
8 measurements spanning 41 days, net +144. 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 550–738 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 19:57716+32
9 Sept 2026, 17:01684+39
30 Aug 2026, 18:08645+28
23 Aug 2026, 14:25617+30
15 Aug 2026, 15:42587+14
7 Aug 2026, 19:42573+1
7 Aug 2026, 05:01572no change
7 Aug 2026, 04:48572first reading

Engagement

17 posts held, back to 19 March 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 17 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

70 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3550.0%
👍2231.4%
🤡68.57%
🦄34.29%
🍾22.86%
👏11.43%
🫡11.43%

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

Measured over the 17 most recent posts we hold, published 19 March 2026 to 5 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.

Recent posts

5 Aug 2026, 01:36 UTC285 views1 reactionsread 7 August 2026

📢 emby更新通知: 1,优化了高峰时段页面加载速度,优化了搜索功能 2,限制了爆米花的一些无用请求(可以使用,但是造成压力的请求服务端自动丢弃) 3,对现有的媒体库做了合并整合 4,新增了虚拟推荐媒体库,方便群员推荐好片(个别播放器还未兼容) 5,使用方法庄达菲bot使用命令,/recommend + tmdb链接 如有问题,请反馈客服bot

❤1

2 Aug 2026, 03:59 UTC457 views2 reactionsread 7 August 2026

📢 庄达菲bot更新通知: 1,新增自助重启emby功能,私聊bot,使用命令 2,5分钟内达到10人发出申请,才会触发重启任务,重启完成后冷却一段时间,无法二次重启。 由于最新版emby有内存泄漏问题,数据库独占锁的缺点,在入库量和访问量大的情况下,容易堵塞。 上线该功能后,即使管理员不在线,用户也可以自助解决问题。请勿滥用,后台会记录申请情况。

❤2

26 Jul 2026, 03:32 UTC802 viewsread 7 August 2026

📢 庄达菲bot功能更新通知: 1,分享链接单次上传视频,数量由50调整到100; 2,未通过审核的链接,无法再上传,请审核通过后,检查是否丢失再上传; 3,上传的视频预查重,与库内相同的数量超过50%的分享,会禁止上传;

14 Jul 2026, 07:43 UTC≈2,040 views29 reactionsread 7 August 2026
Photo

理性聊聊115 302服,别再片面拉踩,客观看清115服的本质 一直以来,Emby圈子都有着心照不宣的默契:互不拉踩、良性交流。但近期频繁出现有人针对115服的片面质疑与刻意拉踩,大多言论都只抓单一缺点放大,完全忽略了115服的综合优势。借此机会,客观梳理事实,为115服正名,也希望大家摒弃片面偏见,理性看待不同服务器形态。 一、关于速度 目前争议最多的,就是115的限速。现阶段115白天限速50MB/s、晚上限速25MB/s(除非你单日传输超1T),这个速率足以流畅播放100G级原盘资源,拖拉秒加载、无掉速,完全能满足日常观影需求。 虽然115起播存在1-3秒的加载时间,但对于用户而言,这个等待完全可以接受。再加上各类115的优化项目、一些播放器的预加载功能,115服早已完美实现秒播体验。 很多人只看表面限速,根本不懂带宽和并发的成本差距。哪怕是晚上25MB限速的情况下,100人同时起播,依旧稳定1–3秒加载。反观个…

👍21🤡6❤2

14 Jul 2026, 03:00 UTC≈1,130 viewsread 7 August 2026

📢更新通知: 1,修复了隐藏“保护花朵“失效的bug,请需要的重新去bot里开关一次; 2,代建小号需要关闭的,请将小号的数字id发给庄达菲;

13 Jul 2026, 07:43 UTC990 views2 reactionsread 7 August 2026

📢通知2则: 1,调整了播放统计后台,因新旧平台数据结构差异,历史剧集的播放统计无法导入,全部丢失。 2,bot新增自查排行榜功能,使用命令如/rank 7(命令+空格+数字)查询,防止滥用,查一次消耗5币(反正币没啥用) 3, myinfo增加了更多了播放统计,服务器按钮,恢复了在线人数统计 4,开展高尺度文艺影片专项转移行动,新设栏目“保护花朵”专门存档,bot可选择隐藏栏目,方便家有孩子的可随时大屏。(欢迎发送此类影片的链接或名字给客服bot)

🍾2

8 Jul 2026, 02:43 UTC≈1,170 viewsread 7 August 2026

📢通知两则: 1,新入库b站充电视频,库里搜索关键词“充电”可看到,充电视频由上传组佛系自发上传,不接受此类求片 2,开通共享换续期的成员,有部分ck一直处于失效状态或者账号异常,后期会被标记共享异常,发现三次异常后,取消共享换续期权利。

14 Jun 2026, 13:55 UTC≈1,650 views4 reactionsread 7 August 2026

📣 积分功能试运行通知 各位大佬,为了鼓励大家共同建设和丰富我们的公共影音库,即日起上线 “资源转存审查加分” 功能测试! 虽然稳健上传组已有10多人规模,目前保持着极快的上片速度和求片反馈,但是相信各位都有不少好资源,为了鼓励大家分享,所以启动积分计划。 ✨ 积分功能介绍: 查漏补缺奖励:成功转存公共库目前缺失的优质资源、冷门神作,在转存成功后将自动触发管理员审查。 加分规则: 1,经管理人工核对资源格式合规(名称、年份、季集信息完整无污染)后,将由管理实时为贡献者派发 的积分奖励!1次有效上传记1分(同一剧集分批上传只计算一次) 2,管理发布求片资源,用户成功上传后,记2分 相关指令: 群内输入“积分”可以查询积分,回复别人信息”发积分红包 20“可发专属积分红包,”发积分红包 20 5“可发拼手气红包 积分用途:积分可用于在“积分商城”兑换虚拟物品 ⚠️ 防刷分规则(核心红线): 人工介入裁决:为防止恶性刷分、上传低…

❤4

21 May 2026, 04:35 UTC≈1,690 viewsread 7 August 2026
Video

功能更新: 1,更新播放失败的提示视频,分别为ck失效,视频无法播放,当前服务繁忙3种 2,修改车位的联系方式,新增了通过庄达菲匿名中转联系,确保对方没有私聊bot也能联系上 使用提示: 1,碰到视频无法播放的情况,请尝试更换视频版本,因为115会把某些视频判定为违规文件,导致视频无法播放,且判定完成无逻辑可言。(SB115),不过稳健115大部分视频都存在多版本,切换即可用。 2, 如果遇到当前服务繁忙,说明你的账号访问有些频繁,稳健后台自动帮你冷却处理,请稍后再试。建议多人共享的关闭预加载功能,浏览即转存,转存太频繁,115会有短时的限制。(就比如你在官方app,很频繁转存移动,官方app也会限制你,很弱智的风控机制) 3,目前115的白天限制已恢复到115MB/s,晚高峰还需继续观察。 4,目前入库的频率保持每天几百部,对于资源有好的建议,欢迎跟帖回复。

19 May 2026, 02:32 UTC≈6,160 views0 reactionsread 7 August 2026
Photo

520大促,稳健115服续期买一送一活动来啦! 前端时间经历了115官方限速+封号风波,稳健115服以独特的拼车模式,依旧保持“稳健”。 为了让更多的有/无115会员的小伙伴了解并加入,如果你有高码+直连的需求,不妨来体验。 稳健115服的520活动,即:发卡网购买520活动专属,30天续期卡(购买注册码开号后使用),直接到账60日。 购买开放于 5月19日12:00~5月21日0:00 限量52位,各位量力而行。 群组:https://t.me/wenjian115

20 Apr 2026, 05:17 UTC≈1,590 viewsread 7 August 2026

功能测试 1,更改了115分享链接方式,需先点击上传按钮,再发送链接,提高单次上传视频量到50 2,myinfo命令增加了ck和转存目录的检查,无法播放时用来自查 3,优化了后台和bot的稳定性 4,发现bug及时反馈,对于积极配合测试的,正式开服后,直接给码。

14 Apr 2026, 07:43 UTC≈1,440 views5 reactionsread 7 August 2026

功能测试 1,发送115分享链接给bot,可以自动入库,一般10分钟后库里查看 (链接格式必须是115cdn.com/s/xxxx) 2,车长才有权限上传分享 3,分享链接中视频数量超过20,则无法上传,(防止大包冲毁服务器) 4,欢迎上传优质高码,垃圾视频不要来测试

❤4🦄1

Showing the 12 most recent of 17 posts we hold for @wenjian115laba. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“稳健115小喇叭” (@wenjian115laba), 716 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/wenjian115laba.

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.