26 Mar 2026, 08:08 UTC38 viewsread 9 August 2026
Photo
长期出三方聊天软件 Teams 支持定制 支持修改短域名 按月付费 售后稳定
Channel
『号商铺』平平安安🐍
@ZF168888888
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
74subscribers
-5 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 | -1002070041460 |
|---|---|
| Type | Channel |
| Username | @ZF168888888 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/ZF168888888 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 04:45 | 74 | -2 |
| 24 Aug 2026, 06:44 | 76 | -2 |
| 15 Aug 2026, 19:38 | 78 | -1 |
| 9 Aug 2026, 19:45 | 79 | no change |
| 7 Aug 2026, 15:41 | 79 | first reading |
Engagement
18 posts held, back to 16 February 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 18 posts for this entry, the most recent from 26 March 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 7s
- Average length
- 7s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
23 Mar 2026, 09:34 UTC41 viewsread 9 August 2026
美卡支付宝假护照现货 可支付 稳定不掉实名不限制 可以屯号打循环 接码时间60天 客户反馈 美卡支付宝 比国内稳定，价格实惠
15 Mar 2026, 10:44 UTC47 viewsread 9 August 2026
给老婆打款，给家人打款，给女朋友打款， 微信，支付宝大额，小额代转代付 纯白， 欢迎中介盘口对接
10 Mar 2026, 15:07 UTC50 viewsread 9 August 2026
Photo
企业独苗，懂得来，贵
10 Mar 2026, 11:12 UTC38 viewsread 9 August 2026
Photo
喜马拉雅实名号，可挑男女，精聊打粉必备，有直播间功能，热门app 售后：关注不上包换，链接卡暂时封控，实卡接码，留卡15天，包永久找回，二次免费
10 Mar 2026, 03:17 UTC24 viewsread 9 August 2026
老品上市：香港普通护照1-9年vs卡 多功能 基本可以无限解封 基本不死 亲测挂5分钟静养🉑➕20多人 🉑扫码🉑爱思或62数据可短信 价格全网最低（懂得来）
8 Mar 2026, 15:45 UTC27 viewsread 9 August 2026
国内3-4月绑卡实名，支付冻结，收藏带资料，国内无视，可进企业。 国内2白（地区山东） 扫码登录
7 Mar 2026, 15:31 UTC26 viewsread 9 August 2026
微信+设备【寄快递】 项目停止-500台小米8（运行6）带v 国内精养原机年护照sm，可接粉被加（包能加人） (建群) 原机出售-有量来谈-国内包邮 库存：1w+ ❤️❤️❤️❤️❤️
6 Mar 2026, 15:47 UTC28 viewsread 9 August 2026
靠谱微博平安 接全世界 微博今天现货 基本10年老白号 信用分420+ 信用分450+ 信用分 500+ 信用分 570+ 信用分600+ 信用分 620+ 信用分650+ 黄v 财经 军事认证 黄v 650+信用分 黄v 各种博主 万粉号 建千人粉丝群 微博 达人 包登入 包找回 微博 全新 老号 各种信用分都有 所有类型 包登入 包找回 代开所有vip svip 无顾虑，售后直接爽快不墨迹 微博找靠谱平安
6 Mar 2026, 15:47 UTC22 viewsread 9 August 2026
邮箱老号 手机直登 无视IP 手里有一批 需要来拿 包登录 包当天问题售后
6 Mar 2026, 15:46 UTC22 viewsread 9 August 2026
国卡百粉实名小红书 可解二次 可解二次 可解二次 解封在线时间长 速度快 包登录 包永久找回
6 Mar 2026, 15:46 UTC22 viewsread 9 August 2026
大量出港卡小红书SM+专业.店铺号 新老都有。代SM小红书 店铺号
Showing the 12 most recent of 18 posts we hold for @ZF168888888. 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.
Citation-graph rank
Citation-graph rank — 1,031,176 of 1,630,085 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“『号商铺』平平安安🐍” (@ZF168888888), 74 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/ZF168888888.
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.