Channel
@d770CTChannel
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
690subscribers
+670 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002665540982 |
|---|---|
| Type | Channel |
| Username | @d770CTChannel |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/d770CTChannel |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 7 Oct 2026, 19:21 | 690 | +38 |
| 26 Sept 2026, 07:18 | 652 | +98 |
| 12 Sept 2026, 10:20 | 554 | +18 |
| 3 Sept 2026, 20:16 | 536 | +514 |
| 28 Aug 2026, 10:15 | 22 | +2 |
| 27 Aug 2026, 17:45 | 20 | first reading |
13 posts held, back to 2 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 13 posts for this entry, the most recent from 25 August 2026. An engagement rate over an empty window would be a number about nothing.
已适配nowhere 协议，iOS，tvOS和Mac端可以用了，上行与下行可独立使用 TLS/TCP 或 QUIC/UDP 的加密传输协议，非私有协议，用 anywhere proxy 即可，这是一个开源的代理软件，很干净 Anywhere proxy 商店链接 兼容 VLESS通用协议，可以在其他软件上用 更新： 费用调整 Premium 等级从0.06USD/GB 降到 0.05USD/GB，降幅0.01USD/GB GIA 线路从0.10USD/GB 降到 0.08USD/GB，降幅0.02USD/GB 普通线路维持0.03USD/GB 更新： 节点命名方式改变 群组：@Route77Group 官网：https://r7.d770.org
自建按量付费机场开始公测了，本人亲手打造，从支付网关到机场面板，全部自主实现 按量使用应该更加灵活，线路价格低至 0.03USD/GB，也有精品线路 欢迎使用 访问网址👉 https://r7.d770.org 加入 交流群 你可以在 此页面 里获取自己的邀请码，他人注册后，充值的金额将永久按照比例分成给你 你可以登录后，随时查看服务器 状态 等详细信息 价格会动态调整 暂时仅支持：稳定币(EVM Chain ) 微信支付宝支付过几天才能适配使用，抱歉 更新： Premium 和GIA 线路，每GB流量费用都降低0.02美元，已经生效 以官网上的价格为主 #按量付费 #机场 #自建 #节点 #GIA #直连 #代理 #小众机场 #不限时
真有趣 V1.1.43
Coming soon V1.1.9
新机场面板即将到来，新的计费方式更加灵活，线路自主选择
Server a没有同步上，导致节点用不了，因为现在从旧站迁移到新站的过程，相关功能还没有完善，请使用其他节点吧 从数据库读取手动恢复了
🤫
若影响较大，还有套餐服务的用户将会在改版完成后获得补偿 需满足月用量超过30GB且套餐剩余时长不少于15天（会换算到日均）
⚠️目前代理服务将会进行大改版，注意节点会随时断开，请随时切换到备用服务
加入了个人博客网站，占用6MB运行内存 前往参观： https://www.d770.org
@d770_bot v8.0.0 自己的交易机器人已上线，目前刚上线，还没做实际的业务测试，后续会补齐和数据的对齐，目前运行内存是原来的1/20。自建支付网关也重新优化了，运行内存为4MB，会有 swap影响，但是影响不大
实测 server a会突破原来的带宽限制
Showing the 12 most recent of 13 posts we hold for @d770CTChannel. 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.
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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“D770’s Corner” (@d770CTChannel), 690 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/d770CTChannel.
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.