Telegram RegisterThe public register of Telegram
Telegram profile photo for Scale system

Channel

Scale system

@scalesystem

On this record: Growth · Engagement · Posts · Cite this entry

343subscribers

-2 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-1001123737809
TypeChannel
Username@scalesystem
CreatedBetween 1 June 2017 and 31 October 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live24 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/scalesystem

Growth

3433453447 August 2026 — 345 subscribers8 August 2026 — 345 subscribers24 August 2026 — 343 subscribers7 August 202624 August 2026
3 measurements spanning 17 days, net -2. 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 343–345 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 20:26343-2
8 Aug 2026, 06:50345no change
7 Aug 2026, 23:25345first reading

Engagement

20 posts held, back to 10 September 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 26 November 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

26 Nov 2021, 07:29 UTC≈1,620 viewsread 8 August 2026

https://github.com/0voice/learning_mind_map 2021年【思维导图】盒子,C/C++,Golang,Linux,云原生,数据库,DPDK,音视频开发,TCP/IP,数据结构,计算机原理等

21 Nov 2021, 06:45 UTC≈1,210 viewsread 8 August 2026

https://itnext.io/kubernetes-essential-tools-2021-def12e84c572 Kubernetes 小工具集锦

21 Nov 2021, 04:17 UTC955 viewsread 8 August 2026

https://did.baidu.com/ 百度实现的去中心化身份认证设计文档

16 Oct 2021, 10:08 UTC≈1,040 viewsread 8 August 2026

https://www.36dianping.com/ 最近在调研外呼中心系统,但是不知道市面上有哪些成熟的解决方案。恰好遇到了这个站点,解决了收集市面上产品的问题

15 Oct 2021, 23:31 UTC787 viewsread 8 August 2026

最好的工程师能在逻辑和感性中间找到一个平衡,良好的设计源于对技术和心理的理解,毕竟我们是在为人写程序。

15 Oct 2021, 02:19 UTC739 viewsread 8 August 2026

Esbuild – An extremely fast JavaScript bundler https://news.ycombinator.com/item?id=28860713 在前端经常看到一些xx 比 xx性能更好,速度更快的工具。这篇HN的讨论比推荐的功能更有趣。让我知道选择是不只能从一点出发。

15 Oct 2021, 02:07 UTC679 viewsread 8 August 2026

https://rancherdesktop.io/ Kubernetes and container management on the desktop

8 Oct 2021, 06:16 UTC764 viewsread 8 August 2026

https://github.com/xiaoxiaojx/blog 深入NodeJS Libuv源码实现

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

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

“Scale system” (@scalesystem), 343 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/scalesystem.

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.