买粉的要小心 买1000一开始两天上,粉丝一直跌说会补,隔两天说还会跌不会补叫他退款,失踪不回复!我只是看到帮我➕大概500粉丝就跌,补跌!!!小心此卖粉💥💥
Signed 青璃 接单接稿 算卦 代投稿

Channel
@jiefaqunv
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,560subscribers
+69 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001679386414 |
|---|---|
| Type | Channel |
| Username | @jiefaqunv |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/jiefaqunv |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 00:37 | 6,560 | -9 |
| 12 Nov 2026, 23:21 | 6,569 | +3 |
| 9 Nov 2026, 01:51 | 6,566 | +23 |
| 5 Nov 2026, 12:16 | 6,543 | -9 |
| 2 Nov 2026, 10:46 | 6,552 | +1 |
| 30 Oct 2026, 03:15 | 6,551 | -2 |
| 27 Oct 2026, 13:56 | 6,553 | +6 |
| 24 Oct 2026, 09:36 | 6,547 | +9 |
| 21 Oct 2026, 03:57 | 6,538 | -7 |
| 11 Oct 2026, 20:17 | 6,545 | +13 |
| 5 Oct 2026, 02:37 | 6,532 | +38 |
| 26 Sept 2026, 13:17 | 6,494 | +15 |
| 17 Sept 2026, 20:59 | 6,479 | -2 |
| 13 Sept 2026, 22:36 | 6,481 | -13 |
| 10 Sept 2026, 13:19 | 6,494 | +3 |
| 5 Sept 2026, 08:17 | 6,491 | -2 |
| 1 Sept 2026, 03:04 | 6,493 | -3 |
| 29 Aug 2026, 00:26 | 6,496 | +2 |
| 26 Aug 2026, 02:02 | 6,494 | -7 |
| 22 Aug 2026, 18:45 | 6,501 | first reading |
16 posts held, back to 14 August 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 11 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 7 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 November 2026 |
|---|---|
| Posts held | 16 (14 August 2026 – 15 November 2026) |
| Views total | 11,174 |
| Reactions total | 43 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 15:52 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
43 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 51.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 22 | 51.2% | |
| 👍 | 10 | 23.3% | |
| 🤣 | 10 | 23.3% | |
| 👏 | 1 | 2.33% |
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 8 of the 16 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 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 14 August 2026 to 15 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram’s own ‘edited’ marker: 1 of 13 posts held from the last 30 days (7.69%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
买粉的要小心 买1000一开始两天上,粉丝一直跌说会补,隔两天说还会跌不会补叫他退款,失踪不回复!我只是看到帮我➕大概500粉丝就跌,补跌!!!小心此卖粉💥💥
Signed 青璃 接单接稿 算卦 代投稿
𝑽 ᐠ 𝐍𝐔𝐌 𝟐𝟔𝟕𝟒 投稿人 ᐨ 匿名 ᚘ
Signed 青璃 接单接稿 算卦 代投稿
避雷!! @ooijjjj 避雷吧各位 做视频号代发的秒结给他叫他等我通知才能删除不能提早删除作品结果过不久直接删除聊天记录+拉黑我了还把视频删了 来不及截图聊天记录 各位千万别秒结给他!!! tng名字 JEFF OOI JIE WEI 新id:@o0504o tg://openmessage?user_id=7464055473
Signed 青璃 接单接稿 算卦 代投稿
𝑽 ᐠ 𝐍𝐔𝐌 𝟐𝟔𝟕𝟑 投稿人 ᐨ @xuanqc ᚘ
Signed 青璃 接单接稿 算卦 代投稿
不要找这个 @mediatalent8 做微信扫码‼️‼️ 一开始我看很多人找他做 觉得蛮诚信的(其实是他自己开了小号帮自己宣传)后来我找他做微信扫码 一开始都挺顺利的,正常走流程 扫码然后让他们的电脑登入(开始做之前他有让我发我的tng二维码给他先⚠️)大概过了一会我的微信就收到通知 说我的微信存在风险,后来他有信息我让我重新扫码登入 这个时候我就觉得不对劲了 我快点退出他们那边的登入 然后快点拉黑了这个骗子,过了一会他找到了我的号码 就信息我威胁我,说要封我的tng 跟hack我的微信 还要找我家的地址‼️不过我的电话号码是飞机号来的 所以他们根据我的电话号码找到的那个chai siaw min我根本不认识😂 由于我前面把他的tlg拉黑了 也没想到会被威胁 所以没有截图到部分证据 只有WhatsApp的聊天记录而已 就在我以为没事了的时候 隔天我收到WeChat团队发来的一个链接 手太快点进去了 就突然被强制退出登录 …
👍10🤣3❤2👏1
Signed 青璃 接单接稿 算卦 代投稿
𝑽 ᐠ 𝐍𝐔𝐌 𝟐𝟔𝟕𝟐 投稿人 ᐨ 匿名 ᚘ
Signed 青璃 接单接稿 算卦 代投稿
避雷骗子 TNG 名叫OOI CHOOI HOON 讲是要帮我定位王者荣耀跟人脸识别,一开始跟我收RM 24讲是人脸,然后定位RM 3,前面RM 27 然后他又跟我讲又要RM 30 是中国实名认证+资料给我,然后他讲我可以上号了,我的号还是被封着还是要强制人脸识别,前前后后我被骗了 RM 57 tg://openmessage?user_id=8284493175
🤣7❤1
Signed 青璃 接单接稿 算卦 代投稿
𝑽 ᐠ 𝐍𝐔𝐌 𝟐𝟔𝟕𝟏 投稿人 ᐨ @Fukuro26 ᚘ
Signed 青璃 接单接稿 算卦 代投稿
匿名投稿 -- 骗子重出江湖了,小心点 TNG叫OOI CHOOI HOON tg://openmessage?user_id=8236719132
❤11
Signed 青璃 接单接稿 算卦 代投稿
𝑽 ᐠ 𝐍𝐔𝐌 𝟐𝟔𝟕𝟎 投稿人 ᐨ 匿名 ᚘ
Signed 青璃 接单接稿 算卦 代投稿
@IVYY0916 https://t.me/IVY0916IVY 起初是看到他的信誉群相信他的 就直接转了 后面问了很多朋友也说他🆙 转账后他就说得等到7点后 因为手机不在身边 我也等了 后面又说要到28/29号 今天都31号了我还是没等到
Signed 青璃 接单接稿 算卦 代投稿
𝑽 ᐠ 𝐍𝐔𝐌 𝟐𝟔𝟔𝟗 投稿人 ᐨ 匿名 ᚘ
Signed 青璃 接单接稿 算卦 代投稿
Showing the 12 most recent of 16 posts we hold for @jiefaqunv. 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.
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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“揭 发 群 ˖﹅” (@jiefaqunv), 6,560 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/jiefaqunv.
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.