发布时间:2024年07月10日 内容介绍: Telegram 账号官方申诉渠道 1,官网表格申诉 申诉地址:https://telegram.org/support 通过此表格描述账号登录所遇到的问题,并填写能够接收邮件的邮箱地址 ,申诉结果会通过邮件回复 2,Telegram 账号官方邮件申诉渠道 申诉邮箱地址: [email protected] 如果机器人、频道或贴纸集被禁止 ,请发送电子邮件至 [email protected]
Signed 魁拔 免费克隆自动开会员机器人

Channel
@tjgnjs
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
69subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001263457471 |
|---|---|
| Type | Channel |
| Username | @tjgnjs |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 8 October 2026 |
| On Telegram | t.me/tjgnjs |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 27 Sept 2026, 17:39 | 69 | -1 |
| 15 Sept 2026, 07:38 | 70 | -1 |
| 7 Sept 2026, 12:21 | 71 | -1 |
| 15 Aug 2026, 19:03 | 72 | -3 |
| 9 Aug 2026, 21:31 | 75 | no change |
| 7 Aug 2026, 12:52 | 75 | first reading |
20 posts held, back to 22 May 2023 — 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 20 posts for this entry, the most recent from 10 July 2024. 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.
发布时间:2024年07月10日 内容介绍: Telegram 账号官方申诉渠道 1,官网表格申诉 申诉地址:https://telegram.org/support 通过此表格描述账号登录所遇到的问题,并填写能够接收邮件的邮箱地址 ,申诉结果会通过邮件回复 2,Telegram 账号官方邮件申诉渠道 申诉邮箱地址: [email protected] 如果机器人、频道或贴纸集被禁止 ,请发送电子邮件至 [email protected]
Signed 魁拔 免费克隆自动开会员机器人
第三版 重构中。。。
Signed 魁拔 免费克隆自动开会员机器人
正在进行 第三次 机器人重构 本次会下掉一些不实用的功能
Signed 魁拔 免费克隆自动开会员机器人
各个语言包: * 中文(简体)-聪聪: tg://setlanguage?lang=zhcncc 👍 * 中文(简体)-@zh_CN: tg://setlanguage?lang=classic-zh-cn * 中文(简体)-简体: tg://setlanguage?lang=classic-zh * 中文(简体)-langCN: tg://setlanguage?lang=zhlangcn * 中文(简体)-zh-hans: tg://setlanguage?lang=zh-hans-beta * 中文(简体)-瓜体: tg://setlanguage?lang=duang-zh-cn * 中文(简体)-小哇: tg://setlanguage?lang=qingwa * 中文(简体)-江湖中文版: tg://setlanguage?lang=jianghu * 中文(简体)-: tg://setlanguage?lang=c…
Signed 魁拔
机器人 故障已处理 接下来开始逐步完善机器人计时问题 停用过期机器人保障数据稳定
Signed 魁拔
@feilvbot 我们打算在这机器人的基础上新增一个英文版本的
Signed 魁拔
#群管机器人 有使用我们群管机器人的,但是主号被注销的可以找我门拿权限。可以获得该群的控制权
Signed 魁拔
@daoka 到卡支付类交流群
Signed 魁拔
#机器人更新 更新版本控制
Signed 魁拔
#升级公告 机器人框架升级完成 多模块分开运行 提升模块的稳定 今后非必要可以不停机维护
Signed 魁拔
#机器人在群里 不处理消息 https://telegra.ph/%E6%9C%BA%E5%99%A8%E4%BA%BA-%E5%9C%A8%E7%BE%A4%E9%87%8C-%E8%A1%A5%E5%A4%84%E7%90%86%E6%B6%88%E6%81%AF-%E9%97%AE%E9%A2%98%E5%A4%84%E7%90%86-08-21
Signed 魁拔
#后台功能完善 新增计算器后台面板
Signed 魁拔
Showing the 12 most recent of 20 posts we hold for @tjgnjs. 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.
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.
@tjgnjs 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.
References a handle that is not a live channel — we have no record it ever was one.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“机器人功能介绍” (@tjgnjs), 69 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/tjgnjs.
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.