Channel
@jinfu666bot
On this record: Growth · Engagement · Posts · Citations · Cite this entry
8subscribers
-1 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003847899153 |
|---|---|
| Type | Channel |
| Username | @jinfu666bot |
| Created | 4 March 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 4 September 2026 |
| On Telegram | t.me/jinfu666bot |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 14:05 | 8 | -1 |
| 12 Aug 2026, 13:17 | 9 | no change |
| 11 Aug 2026, 14:45 | 9 | first reading |
5 posts held, back to 4 March 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 5 posts for this entry, the most recent from 17 July 2026. An engagement rate over an empty window would be a number about nothing.
💯市场平台官方招商经理 重点项目合作如下 -------------------------------------------------------- 💎天系列11【运达】待遇升级 ➡️点击查看详细介绍 【彩票体育真人电子棋牌】vip反水自动到账 注册链接： https://s.ydwefef2602.com/Register/4nRLuB6A6F 💎赢咖系列 【瑞丰】➡️点击查看详细介绍 综合娱乐（彩票，哈希游戏，区块链游戏，TG骰子，真人，电子，棋牌，体育，捕鱼，影音） 注册链接： https://888.rfyule28.com/reg/AOQ6VF 💎大众系列 汇众娱乐➡️点击查看详细介绍 多种类区块链哈希衍生游戏 出款秒到 支持多币种游戏 转账哈希实时返奖 注册链接: https://pc.hz11.vip/reg/vveenp 💎拉菲系列第１３个平台－泰达娱乐 开放注册：2026/8/3…
金富骰子/金富电子 pinned a photo
金富游戏 👉点这里开始游戏 集电子/真人/捕鱼🐠PC28等多种游戏类型！24*7客服服务-百万U出款秒到，活动多多！老板们放心玩，放心赢，放心取。
金富游戏 👉点这里开始游戏 集电子/真人/捕鱼🐠PC28等多种游戏类型！24*7客服服务-百万U出款秒到，活动多多！老板们放心玩，放心赢，放心取。
Channel created
Showing the 5 most recent of 5 posts we hold for @jinfu666bot. 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“金富骰子/金富电子” (@jinfu666bot), 8 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/jinfu666bot.
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.