丝滑通道 联系 @u1314

Channel
大盘猪集团 @tuilu
@tuilu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
18,286subscribers
-10,639 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003392740254 |
|---|---|
| Type | Channel |
| Usernames | @dpzjt @tuilu |
| Description | 大盘猪集团|金猪引路龙腾四海 永远是你的退路 Golden Pig Leads the Way, Dragon Soars Across the Seas. Always your safe way back. @tuilu |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 112 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/tuilu |
Topic
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 22:39 | 18,286 | +17 |
| 6 Nov 2026, 10:40 | 18,269 | +47 |
| 6 Nov 2026, 01:05 | 18,222 | +26 |
| 5 Nov 2026, 11:38 | 18,196 | +27 |
| 5 Nov 2026, 00:36 | 18,169 | +88 |
| 4 Nov 2026, 08:35 | 18,081 | +80 |
| 3 Nov 2026, 23:21 | 18,001 | +35 |
| 3 Nov 2026, 06:39 | 17,966 | +1 |
| 3 Nov 2026, 02:44 | 17,965 | +39 |
| 2 Nov 2026, 08:06 | 17,926 | +28 |
| 2 Nov 2026, 00:47 | 17,898 | +18 |
| 1 Nov 2026, 08:34 | 17,880 | +20 |
| 31 Oct 2026, 23:45 | 17,860 | +54 |
| 31 Oct 2026, 10:19 | 17,806 | +7 |
| 31 Oct 2026, 01:38 | 17,799 | -38 |
| 30 Oct 2026, 13:00 | 17,837 | -3 |
| 30 Oct 2026, 00:35 | 17,840 | +30 |
| 29 Oct 2026, 11:01 | 17,810 | +53 |
| 29 Oct 2026, 02:35 | 17,757 | -35 |
| 28 Oct 2026, 09:11 | 17,792 | first reading |
Engagement
389 posts held, back to 6 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 100 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 12.8%
- avg views ÷ 18,286 subscribers
- Avg views / post
- 2,340
- 57 posts measured
- Reaction rate
- 0.068%
- reactions ÷ views · ER floor
- Posts in window
- 57
- of 389 held
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 17 of 57 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 389 (6 August 2026 – 7 November 2026) |
| Views total | 133,119 |
| Reactions total | 28 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 03:50 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.
What this channel posts
- Photos
- 562
- Videos
- 3
- Links
- 9
Lifetime counters from Telegram’s own channel header, read 7 November 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
115 reactions across 64 posts, in 10 distinct kinds. The most used accounts for 55.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 64 | 55.7% | |
| 👍 | 24 | 20.9% | |
| 💩 | 16 | 13.9% | |
| 👎 | 3 | 2.61% | |
| 🤣 | 2 | 1.74% | |
| 🤮 | 2 | 1.74% | |
| ❤🔥 | 1 | 0.87% | |
| 👌 | 1 | 0.87% | |
| 🔥 | 1 | 0.87% | |
| 🤔 | 1 | 0.87% |
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 94 of the 389 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 115 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 389 most recent posts we hold, published 6 August 2026 to 7 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.
Recent posts
Telegram’s own ‘edited’ marker: 8 of 57 posts held from the last 30 days (14.0%) 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).
有数字钱包绑卡付的 找我 @jinjv88888888
数字钱包付款有的联系 量大不罚站 @louliu678 @ke7758
常规色招 新通道 丝滑过的 直接来 帮测试 要大额 常规色招 新通道 丝滑过的 直接来 帮测试 要大额 常规色招 新通道 丝滑过的 直接来 帮测试 要大额 常规色招 新通道 丝滑过的 直接来 帮测试 要大额 @shenjiao2
抖音三合一 有的带汇率联系我 @c33445566
工商直扫 农业直扫 招商直扫 来吃肉 @jinjv88888888
盘口直招24小时在线 需要冷门下载付自己引导的 有下载付的可以联系我 可以扶持 可以配合测试 @yutianqi6
常规色料招车 独家可包车 罚站赔u 新车可扶持 @yibashou
招 信用卡分期 量大管饱 招 信用卡分期 量大管饱 招 信用卡分期 量大管饱 @shenjiao2
京东E卡核销有的来带汇率 @nb01233
贴户/群引导小荷包 有的联系 @c33445566
家庭农场充值 微信支付宝扫码付只吃信用卡这个 有的 @cc_66880 联系我
Showing the 12 most recent of 389 posts we hold for @tuilu. 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.
Posts edited after publishing
@tuilu edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 19 August 2026
- Most recent edit
- 19 August 2026
Posts recorded as deleted after publishing
We recorded 21 posts on @tuilu as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 9 August 2026
- Most recent seen missing
- 9 October 2026
- Median time before seen missing
- 16 hours
- Seen missing in the last 30 days
- 2
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@tuilu named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 7 November 2026 – 7 November 2026
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“大盘猪集团 @tuilu” (@tuilu), 18,286 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/tuilu.
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.