Telegram RegisterThe public register of Telegram
Telegram profile photo for 天马公告栏

Channel

天马公告栏

@DS_818

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

356subscribers

-5 since we began measuring on 9 October 2026

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

Register entry

Telegram ID-1001686634845
TypeChannel
Username@DS_818
CreatedBetween 1 December 2021 and 18 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 October 2026
Last confirmed live26 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/DS_818

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 26 October 2026 and assigned it the closest of 31 fixed categories, at 50% 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 the other topics.

Growth

356361358.59 October 2026 — 361 subscribers9 October 2026 — 361 subscribers13 October 2026 — 360 subscribers19 October 2026 — 359 subscribers26 October 2026 — 356 subscribers9 October 202626 October 2026
5 measurements spanning 17 days, net -5. 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 355–362 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Oct 2026, 13:37356-3
19 Oct 2026, 16:18359-1
13 Oct 2026, 08:56360-1
9 Oct 2026, 07:22361no change
9 Oct 2026, 06:47361first reading

Engagement

20 posts held, back to 18 January 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 7 May 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 May 2024, 17:06 UTC≈2,300 viewsread 9 October 2026

✅ 新上押公群🔥 001 小K 租咸鱼 已在天马上压1001u 上押押金:1001USDT ——————— 公群通道:https://t.me/+cXpceJoILNg2Yjk1

1 May 2024, 04:34 UTC≈3,640 viewsread 9 October 2026

一键连接代理(免费) 天马独家赞助 https://t.me/proxy?server=38.180.75.198&port=443&secret=dde6e4f78a9a19a1271af06a4dbeffba43

25 Apr 2024, 08:42 UTC≈3,360 viewsread 9 October 2026

天马担保自助导航 飞机下载 发布供需 上押规则 担保负责人 VPN加速 双向解除 解除屏蔽 钱包下载 公群列表

25 Apr 2024, 08:41 UTC≈2,160 viewsread 9 October 2026

其他类公群 —————————————————

25 Apr 2024, 08:40 UTC≈1,960 viewsread 9 October 2026

地推类公群 ——————————————————

25 Apr 2024, 08:40 UTC≈1,790 viewsread 9 October 2026

游戏类公群 —————————————————-

25 Apr 2024, 08:40 UTC≈1,680 viewsread 9 October 2026

跑分类公群 ———————————————-

25 Apr 2024, 08:40 UTC≈1,580 viewsread 9 October 2026

代发类公群 —————————————-

25 Apr 2024, 08:40 UTC≈1,460 viewsread 9 October 2026

手机口类公群 ————————————-

25 Apr 2024, 08:40 UTC≈1,440 viewsread 9 October 2026

——-担保公群收费标准以及规则如下!—— 1:上押金额必须500USDT以上 具体上押根据项目情况为准! 2:无上押费用,无月租,退押只收取 5% 的服务费,没有其他任何费用,最低50U起 ✅开群联系 负责人:@TMFZR ———————————————————- 一切公群交易结账 尽量 USDT交易! ⚠️支付宝口令。扫码,微信,银行卡交易概不负责, 原因:盗口令或转账不认的难追查! 并且减少了代付的需要,大大降低超额跑路的风险。一定一定要下载欧易⚠️ 🆘注:口令被盗问题单个客户被盗判做单方承担,多个口令被盗判公群方赔付。 ———————————————————— 1、上押金额必须500USDT以上 2、退押扣除 5% 手续费,无其他任何费用 3、退押时无纠纷可立即申请退押,申请后24小时内无纠纷立刻下发押金 4、做事规则跑分要求必须提前跟合作用户沟通好! 5、出现问题如实交代,发现弄虚作假一律发红包扣押处理! 6…

25 Apr 2024, 08:38 UTC≈1,060 viewsread 9 October 2026

解除双向 个人账号解除双向聊天限制 👉搜索 @spambot 👉点击 Start 👉点击 But I can't message non-contacts! 👉点击 No,I'll never do any of this! 👉回复 accident 约25分钟左右就恢复正常了,有些解禁时间会较长,有些需要发邮件向官方提出解封申请 解除双向

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

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

“天马公告栏” (@DS_818), 356 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/DS_818.

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.