🤥🤥🤥🤥3月22日部分已清帐 点击下方蓝色字体跳转 🔔壹鼎集团做单公群客服😃😃 🔔壹鼎集团每日结算频道😃😃 🔔壹鼎集团24小时不禁言福利群 🔔壹鼎集团代刷要求做单细节招商频道 🔴公群在押5万U,折合人民币35万(放心做单,做单有保障) 🔴全天24小时在线开工 👉做单联系公群负责人:@o25o8 🤥🤥🤥🤥🤥🤥🤥🤥

Channel
壹鼎集团业务通知频道
@fengyezhifupd
On this record: Growth · Engagement · Posts · Citations · Cite this entry
514subscribers
-25 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002556360077 |
|---|---|
| Type | Channel |
| Username | @fengyezhifupd |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/fengyezhifupd |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 11:56 | 514 | -8 |
| 9 Sept 2026, 15:00 | 522 | -4 |
| 30 Aug 2026, 20:57 | 526 | -6 |
| 24 Aug 2026, 19:39 | 532 | -1 |
| 16 Aug 2026, 13:58 | 533 | -6 |
| 9 Aug 2026, 03:11 | 539 | no change |
| 8 Aug 2026, 07:46 | 539 | first reading |
Engagement
3 posts held, back to 22 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 3 posts for this entry, the most recent from 22 March 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Photo, posted without a caption
Photo, posted without a caption
Showing the 3 most recent of 3 posts we hold for @fengyezhifupd. 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.
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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“壹鼎集团业务通知频道” (@fengyezhifupd), 514 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/fengyezhifupd.
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.