已恢复

Channel
头家筛料 @TouJia
@toujia
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6,610subscribers
+2,420 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002083874511 |
|---|---|
| Type | Channel |
| Usernames | @toujia @toujia007 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/toujia |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 12 Nov 2026, 16:01 | 6,610 | -12 |
| 12 Nov 2026, 08:09 | 6,622 | +301 |
| 8 Nov 2026, 15:47 | 6,321 | no change |
| 8 Nov 2026, 13:45 | 6,321 | +370 |
| 5 Nov 2026, 15:49 | 5,951 | +20 |
| 5 Nov 2026, 02:01 | 5,931 | +326 |
| 2 Nov 2026, 11:58 | 5,605 | no change |
| 2 Nov 2026, 10:18 | 5,605 | +65 |
| 30 Oct 2026, 05:58 | 5,540 | -3 |
| 30 Oct 2026, 04:21 | 5,543 | +59 |
| 27 Oct 2026, 11:17 | 5,484 | -2 |
| 27 Oct 2026, 01:59 | 5,486 | +24 |
| 24 Oct 2026, 13:56 | 5,462 | -3 |
| 24 Oct 2026, 08:57 | 5,465 | +185 |
| 21 Oct 2026, 14:06 | 5,280 | +20 |
| 20 Oct 2026, 23:30 | 5,260 | +69 |
| 18 Oct 2026, 09:08 | 5,191 | +13 |
| 17 Oct 2026, 23:19 | 5,178 | +102 |
| 15 Oct 2026, 04:18 | 5,076 | +12 |
| 14 Oct 2026, 12:35 | 5,064 | first reading |
Engagement
24 posts held, back to 11 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.48%
- avg views ÷ 6,610 subscribers
- Avg views / post
- 363
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 24 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.
| Window | Rolling 30 days · latest post in window 22 October 2026 |
|---|---|
| Posts held | 24 (11 September 2025 – 22 October 2026) |
| Views total | 725 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 02:05 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.
Reaction mix
28 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 85.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 85.7% | |
| 👎 | 2 | 7.14% | |
| 🥰 | 2 | 7.14% |
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 12 of the 24 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 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 11 September 2025 to 22 October 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: 0 of 2 posts held from the last 30 days (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).
头家系统维护升级,请勿走空,预计升级时间10个小时,请各位老板们注意‼️‼️‼️,升级完成第一时间告知,届时将带给老板们更好的产品体验。🙆♂️🙆♂️🙆♂️🙆♂️
欢度国庆,㊗️头家各位老板们,开开心心🥰发家致富🌈🌈🌈
天涯共此时,千里共婵娟,中秋佳节祝 头家各位老板们,阖家欢乐 ,中秋快乐🎉🎉🎉🎉
端午安康,头家祝各位端午节HAPPY 。🙆♂️🙆♂️🙆♂️
头家祝各位老板们劳动节快乐❗️❗️❗️
‼️‼️‼️通知,TG年龄筛选渠道暂时维护,头家已加急处理,请老板们耐心等候。
❤1
‼️‼️ Ws升级成功,现已开放,因市场调整WS开通价格调整为万0.85。
‼️‼️‼️目前,Ws 渠道因官方升级调整,现WS调整升级,头家已加急处理,请老板们耐心等候。
头家祝愿各位老板元宵佳节快乐🎉幸福安康
❤1
👍头家筛料祝:除夕除夕,除去烦恼,迎接希望;守岁守岁,守住好运,岁岁平安;迎新迎新,迎来快乐,万象更新;祈福祈福,祈祷送福,祝福添福。除夕快乐!
2026,㊗️各位老板大顺大发,大吉大利!!!
❤5🥰1
Showing the 12 most recent of 24 posts we hold for @toujia. 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.
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
@toujia 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 6 posts, 8 August 2026 – 9 August 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“头家筛料 @TouJia” (@toujia), 6,610 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/toujia.
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.