Telegram RegisterThe public register of Telegram
Telegram profile photo for 目录福利频道

Channel

目录福利频道

@mulufuli

On this record: Topic · Observations · Channels linked by matching posts · 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

16,787subscribers

+5,471 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002755239295
TypeChannel
Username@mulufuli
Description这里汇总了目录群的所有福利。
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/mulufuli

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@laoahihaixuan/2644213 Aug 2026, 13:12 UTC@mulufuli/1169 · this entry13 Aug 2026, 13:12 UTC1.00under a minute
@laoahihaixuan/2655515 Aug 2026, 10:32 UTC@mulufuli/1176 · this entry15 Aug 2026, 10:32 UTC1.00under a minute
@laoahihaixuan/2743329 Aug 2026, 15:28 UTC@mulufuli/1239 · this entry29 Aug 2026, 15:28 UTC1.00under a minute
@laoahihaixuan/2748230 Aug 2026, 04:45 UTC@mulufuli/1241 · this entry30 Aug 2026, 04:45 UTC1.00under a minute
@mulufuli/1254 · this entry1 Sept 2026, 09:13 UTC@laoahihaixuan/276361 Sept 2026, 09:13 UTC1.00under a minute
@mulufuli/1259 · this entry1 Sept 2026, 16:30 UTC@laoahihaixuan/276581 Sept 2026, 16:30 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@laoahihaixuan25 (8/8 hand-verifiable sample passed)1.00under a minute@laoahihaixuan (22–3)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 22 of the 22 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 87 comparable posts for this entry, running 29 July 2026 to 15 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @laoahihaixuan. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

11,17118,59114,88116,7876 August 202614 November 2026
65 measurements spanning 100 days, net +5,471. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 10,058–19,704 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
14 Nov 2026, 17:5116,787-53
11 Nov 2026, 14:5616,840-64
9 Nov 2026, 17:4016,904-271
8 Nov 2026, 09:0117,175-122
7 Nov 2026, 06:3017,297-75
6 Nov 2026, 03:0617,372-42
5 Nov 2026, 03:5817,414-37
4 Nov 2026, 05:3817,451+279
3 Nov 2026, 07:1917,172+494
2 Nov 2026, 07:3616,678+44
1 Nov 2026, 10:3016,634-14
31 Oct 2026, 12:2816,648-278
30 Oct 2026, 09:4616,926-242
29 Oct 2026, 10:4917,168-373
28 Oct 2026, 12:1617,541-573
27 Oct 2026, 10:0118,114-277
26 Oct 2026, 07:5018,391-73
25 Oct 2026, 04:3718,464+45
24 Oct 2026, 05:1118,419+26
23 Oct 2026, 01:5018,393first reading

Engagement

130 posts held, back to 29 July 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 81 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.61%
avg views ÷ 16,787 subscribers
Avg views / post
941
36 posts measured
Reaction rate
0.127%
reactions ÷ views · ER floor
Posts in window
48
of 130 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 19 of 36 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held130 (29 July 2026 – 17 November 2026)
Views total33,888
Reactions total24
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 06:33 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
500
Links
487

Lifetime counters from Telegram’s own channel header, read 17 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

43 reactions across 32 posts, in 2 distinct kinds. The most used accounts for 81.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3581.4%
💩818.6%

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 40 of the 130 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 130 most recent posts we hold, published 29 July 2026 to 17 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: 3 of 48 posts held from the last 30 days (6.25%) 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).

17 Nov 2026, 06:18 UTC23 viewsread 17 November 2026
Photo

🎰 饭饭的目录榜单回馈抽奖🎟️ 📮 抽奖条件: 🎫 加入-🍚 🎫 加入-上海目录老师榜单🧾 🎫 加入-目录福利频道 🎫 加入-上海开课目录群🧾 🎁 奖品内容: 200元优惠券 × 3 💡 活动说明: 中奖者机器人🤖会自动通知领取。 榜单评价链接🔗跳转https://t.me/laoahihaixuan/32118 领取福利以后请给出老师的真实长篇评价,不写的取消后续抽奖资格,本福利,🈲买卖,转赠则需提前征得老师的同意,奖品有效期一周。 奖品使用请联系老师: @tuangyuan0819 📅 开奖日期:(UTC+8) 2026年11月18日 14时16分35秒

15 Nov 2026, 05:06 UTC579 viewsread 17 November 2026
Photo

娜娜 B套餐优惠 原价2300pp现特价1200 原价夜课4000现特惠价2500 定金预约 活动日期11月15日到11月17日 老师电报号: @aaa199988aa @danaihelen 双向机器人: @hzmary_bot 老师频道: @danainana @putuodanai

14 Nov 2026, 10:21 UTC716 viewsread 17 November 2026
Photo

🎰 沐橙的目录榜单回馈抽奖🎟️ 📮 抽奖条件: 🎫 加入-🫦沐橙 🎫 加入-上海目录老师榜单🧾 🎫 加入-目录福利频道 🎫 加入-上海开课目录群🧾 🎁 奖品内容: P半价(500) × 1 💡 活动说明: 中奖者机器人🤖会自动通知领取。 榜单评价链接🔗跳转https://t.me/laoahihaixuan/33347 领取福利以后请给出老师的真实长篇评价,不写的取消后续抽奖资格,本福利,🈲买卖,转赠则需提前征得老师的同意,奖品有效期一周。 奖品使用请联系老师: @Mu_0017 📅 开奖日期:(UTC+8) 2026年11月17日 18时18分08秒

13 Nov 2026, 14:42 UTC165 viewsread 13 November 2026
Photo

💐💐💐开奖了💐💐💐 昕彤的目录榜单回馈抽奖🎟️ 开奖了! 本期总参与人数: 56 1- 🥱 获得:P300元优惠券 2- 临舟 获得:P300元优惠券 3- Angel 获得:P300元优惠券 4- 咪咕 获得:PP300元优惠券 5- 小H是个摄影师 获得:PP300元优惠券 6- Driver KAKA 获得:PP300元优惠券 谨祝中奖用户大吉大利万事顺意

13 Nov 2026, 03:36 UTC585 views0 reactionsread 14 November 2026
Photo

娜娜 B套餐优惠 原价2300pp现半价1200 原价夜课4000现特惠价2000 定金预约 活动日期11月13日到11月15日 老师电报号: @aaa199988aa @danaihelen 双向机器人: @hzmary_bot 老师频道: @danainana @putuodanai

12 Nov 2026, 04:29 UTC960 views1 reactionsread 17 November 2026
Photo

目录群宠粉福利🎉 (定期放送) 苏舟舟 原价: 900p 50min 1600pp 750min 💥福利价: p200元优惠券 (二个名额,先到先得,) 💥福利暗号:目录群推荐 联系老师: @shuzhouzhou123 老师资料:https://t.me/laoahihaixuan/31900 ⚠️拿了福利的群友必须给反馈,长短没有要求。不可和其它优惠叠加使用。 感谢老师主动提供的福利,点击查看往期所有福利 目录福利频道 🔥如果有需要主动提供福利的老师,请联系群主 老墨 欢迎各位老师主动报名 🔥一键添加目录榜单所有群

❤1

12 Nov 2026, 04:28 UTC796 views1 reactionsread 17 November 2026
Photo

目录群宠粉福利🎉 (定期放送) 宋薇薇 原价: 1600p 50min 3000pp 80min 💥福利价: 200元优惠券 (持续三天,每天前两名,先到先得,) 💥福利暗号:目录群推荐 联系老师: @sweiwei2006 老师资料:https://t.me/laoahihaixuan/32393 ⚠️拿了福利的群友必须给反馈,长短没有要求。不可和其它优惠叠加使用。 感谢老师主动提供的福利,点击查看往期所有福利 目录福利频道 🔥如果有需要主动提供福利的老师,请联系群主 老墨 欢迎各位老师主动报名 🔥一键添加目录榜单所有群

❤1

11 Nov 2026, 12:56 UTC430 viewsread 12 November 2026
Photo

娜娜 B套餐优惠 原价2300pp现半价1200 原价夜课4000现特惠价2000 定金预约 活动日期11月11日到11月13日 老师电报号: @aaa199988aa @danaihelen 双向机器人: @hzmary_bot 老师频道: @danainana @putuodanai

11 Nov 2026, 11:51 UTC785 viewsread 17 November 2026
Photo

目录群宠粉福利🎉 (定期放送) 鹅宝 原价: 2800/p 60min 5500/pp 100min 💥福利价: 200元优惠券×3 300元优惠券×1 (名额有限,先到先得) 💥福利暗号:目录群推荐 联系老师: @tieguodunda_e 老师资料:https://t.me/laoahihaixuan/32854 ⚠️拿了福利的群友必须给反馈,长短没有要求。不可和其它优惠叠加使用。 感谢老师主动提供的福利,点击查看往期所有福利 目录福利频道 🔥如果有需要主动提供福利的老师,请联系群主 老墨 欢迎各位老师主动报名 🔥一键添加目录榜单所有群

Showing the 12 most recent of 130 posts we hold for @mulufuli. 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

@mulufuli 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
15 November 2026
Most recent edit
15 November 2026

Posts recorded as deleted after publishing

We recorded 18 posts on @mulufuli 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
8 August 2026
Most recent seen missing
5 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
4

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 18 registered channels — 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.

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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“目录福利频道” (@mulufuli), 16,787 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/mulufuli.

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.