12 Dec 2022, 12:01 UTC72 views3 reactionsread 22 August 2026
♥️亿人联系方式:【1个qq，3个频道，3个飞机】 亿人QQ：98100 频道1：防失联及所有平台待遇：@QQ98100 频道2：亿人日常更新:@yirenjituan 频道3：亿人集团资料库：@yiren199 飞机1：亿人事务：@yituandui 飞机2：亿人常用：@yiren188 全天在线 资金担保 代理扶持发展 量大合作者可安排出境办公 一站式全包
❤1👍1🔥1
Channel
富达地址
@fudadizhi1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001830929014 |
|---|---|
| Type | Channel |
| Username | @fudadizhi1 |
| Description | 亿人集团——富达娱乐第一人 |
| Created | 26 November 2022 — measured — dated from the channel’s first post |
| First recorded | 22 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/fudadizhi1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 11:45 | 4 | no change |
| 22 Aug 2026, 11:15 | 4 | first reading |
Engagement
3 posts held, back to 26 November 2022 — 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 12 December 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 22 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
5 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 40.0% | |
| 🔥 | 2 | 40.0% | |
| 👍 | 1 | 20.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 2 of the 3 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 26 November 2022 to 12 December 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
26 Nov 2022, 11:49 UTC62 views2 reactionsread 22 August 2026
拉菲系列 拉菲1， 拉菲 2014年 拉菲2， 娱乐天地 2015年 拉菲3， 万达 2016年 拉菲4， 华宇 2017年 拉菲5， 恒达 2018年 拉菲6， 顺达 2019年 拉菲7， 富达 2020年 拉菲8， 风暴 2021年 拉菲9， 门徒 2021年 拉菲10，焦点 2022年 拉菲11，辉达 2024年 拉菲12，益达 2025年 🌈 拉菲系列【发展 】🌈 🔺拉菲8风暴 1980+100+十日分红 详情 🔺拉菲9门徒 1990+50 +十日分红 详情 🔺拉菲10焦点 1980+60 +32%日红 详情 🔺拉菲11辉达 2000+50 +月分红 详情 🔥拉菲12益达 三种模式 A01 2000+40工资+50+月分红+占城10%（抽水） A02 1990…
❤1🔥1
26 Nov 2022, 08:16 UTCviews —
Channel created
Showing the 3 most recent of 3 posts we hold for @fudadizhi1. 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“富达地址” (@fudadizhi1), 4 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/fudadizhi1.
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.