Channel
@yuanma588
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,613subscribers
-587 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001749790489 |
|---|---|
| Type | Channel |
| Username | @yuanma588 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/yuanma588 |
Software piracy — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 |
|---|---|---|
| 6 Oct 2026, 22:37 | 1,613 | -8 |
| 29 Sept 2026, 23:39 | 1,621 | -19 |
| 19 Sept 2026, 13:18 | 1,640 | -8 |
| 14 Sept 2026, 15:39 | 1,648 | -2 |
| 10 Sept 2026, 22:17 | 1,650 | -59 |
| 5 Sept 2026, 22:37 | 1,709 | -44 |
| 2 Sept 2026, 02:08 | 1,753 | -47 |
| 30 Aug 2026, 12:03 | 1,800 | -35 |
| 27 Aug 2026, 12:43 | 1,835 | -74 |
| 24 Aug 2026, 11:17 | 1,909 | -104 |
| 20 Aug 2026, 10:06 | 2,013 | -66 |
| 17 Aug 2026, 15:17 | 2,079 | -89 |
| 14 Aug 2026, 01:56 | 2,168 | -27 |
| 11 Aug 2026, 02:02 | 2,195 | -4 |
| 8 Aug 2026, 00:01 | 2,199 | -1 |
| 7 Aug 2026, 10:01 | 2,200 | no change |
| 7 Aug 2026, 09:55 | 2,200 | first reading |
4 posts held, back to 21 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 4 posts for this entry, the most recent from 26 August 2025. An engagement rate over an empty window would be a number about nothing.
源码名称： [ 四国语言外汇盘口源码 ] 源码简介： 最新拿下一套四国语言外汇盘口源码 ， 前端VUE自适应、后端thinkphp， 时间盘、区块链、外汇盘、贵金属， “买涨、买跌”都在后台可控制。 持续更新源码的第四年。 [本频道温馨提示：] 源码都是经过技术测试上传到频道的 单独购买源码无技术支持！ 如果你技术不错是同行单独购买源码无任何问题！ 如果你对搭建一知半解 请购买搭建服务！ 需要的联系唯一客服： @ymw588 @ymw588 @ymw588
Photo, posted without a caption
源码名称： [ 多国语言彩票28系统源码 ] 源码简介： 最新拿下一套多国语言彩票28系统源码 ， 前端用html开发、后端是PHP写的， 时时彩、幸运飞艇、极速赛车、28彩， 澳洲5、澳洲10、加拿大28、比特28。 持续更新源码的第四年。 [本频道温馨提示：] 源码都是经过技术测试上传到频道的 单独购买源码无技术支持！ 如果你技术不错是同行单独购买源码无任何问题！ 如果你对搭建一知半解 请购买搭建服务！ 需要的联系唯一客服： @ymw588 @ymw588 @ymw588
Photo, posted without a caption
Signed 网站搭建
Showing the 4 most recent of 4 posts we hold for @yuanma588. 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“平台搭建 | 精品源码 | 软件开发 |” (@yuanma588), 1,613 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/yuanma588.
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.