【麦当劳100积芬兌15w份大米】 18-21号 ⏰10点45分 在麦当劳app-底部 麦麦商城 有100积芬可兌500g新米1份 还有25积芬抽5w份兔费汉堡等 - 🌟核销时间:20-21号 每天 ⏰10:45-20:00 到店核.销
Signed Focus on sharing

Channel
@sunpojie
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
19,376subscribers
-821 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001239955639 |
|---|---|
| Type | Channel |
| Username | @sunpojie |
| Description | 👗 白菜价商品, 🐏 褥羊毛 学习资源, 👄 破解软件 电视剧, 🌊 最新线报 磁力🧲工具, 🌍 京东优惠券,淘宝优惠券 |
| Created | 16 October 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/sunpojie |
Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 86% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @open8888 | 16 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @open8888 (16–0) |
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. None of the 3 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 43 comparable posts for this entry, running 29 July 2026 to 16 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @open8888. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 18 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.
This channel is in a group of 2 registered channels linked by matching posts. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 16:51 | 19,376 | -31 |
| 15 Nov 2026, 18:47 | 19,407 | -32 |
| 12 Nov 2026, 12:09 | 19,439 | -21 |
| 10 Nov 2026, 08:41 | 19,460 | -9 |
| 8 Nov 2026, 22:55 | 19,469 | -28 |
| 7 Nov 2026, 11:45 | 19,497 | -9 |
| 6 Nov 2026, 08:46 | 19,506 | -8 |
| 5 Nov 2026, 08:47 | 19,514 | -15 |
| 4 Nov 2026, 10:27 | 19,529 | -6 |
| 3 Nov 2026, 10:48 | 19,535 | -6 |
| 2 Nov 2026, 09:04 | 19,541 | -8 |
| 1 Nov 2026, 12:04 | 19,549 | -4 |
| 31 Oct 2026, 12:56 | 19,553 | -13 |
| 30 Oct 2026, 10:08 | 19,566 | -15 |
| 29 Oct 2026, 08:48 | 19,581 | -3 |
| 28 Oct 2026, 04:01 | 19,584 | -6 |
| 27 Oct 2026, 04:57 | 19,590 | -18 |
| 26 Oct 2026, 07:04 | 19,608 | -7 |
| 25 Oct 2026, 05:36 | 19,615 | -9 |
| 24 Oct 2026, 06:08 | 19,624 | first reading |
105 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 91 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.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 105 (29 July 2026 – 18 November 2026) |
| Views total | 17,012 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 17:06 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.
Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Telegram’s own ‘edited’ marker: 0 of 31 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).
【麦当劳100积芬兌15w份大米】 18-21号 ⏰10点45分 在麦当劳app-底部 麦麦商城 有100积芬可兌500g新米1份 还有25积芬抽5w份兔费汉堡等 - 🌟核销时间:20-21号 每天 ⏰10:45-20:00 到店核.销
Signed Focus on sharing
#频道互推 #相似推荐 ------------------------------ 📢 武汉&女神 📢 天津修车驾校 📢 长春美女综合 📢 杭州资源 📢 免费资源分享频道 📢 苏州醉花间资源分享 📢 北京茶厅 📢 全球资源仓库 📢 惠州金御汇 📢 嘉兴学院资源库 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
Signed SOSO搜搜
现在就能领了 B站🆓领大会员 ⏰15日12:00 — 16日12:00 哔哩哔哩app搜:大会员 7天会员人人有份 都可以领哈
Signed Focus on sharing
周末囤水很划蒜! 怡宝555ml*24瓶💰21.9 210ml*24瓶💰 9.9 农夫山泉550ml*24瓶💰20.6 ❶一键领券 mp://KTDO8GOGucexrBE ❷再搜怡宝/农夫官方店下单👇mp://tnMxhBBXjvStoeI
Signed Focus on sharing
在 Telegram 里找内容,先打开 SOSO 搜搜。 频道、群组、帖子、贴纸都可以搜;也可以从发现页继续浏览。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1001239955639_508980131_eff7ff69
Signed SOSO搜搜
#频道互推 #相似推荐 ------------------------------ 📢 成都资源 📢 🔥🔥ZBook,|电子书📚| 小说|漫画资源||禁书分享 📢 七夜公益破解资源分享🇨🇳 📢 幻宇秘语付费资源 📢 pikpak福利姬资源合集 📢 落雾MoseCheat‑和平精英&PUBG改文件资源频道 📢 郑州·嘉宴厅 📢 PikPak 网盘资源广场 📢 【严选】扬州资源 📢 ASMR👂🏻圈圈录播精选 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
Signed SOSO搜搜
【WorkBuddy每天抢2万份星巴克】微信打开活动->11月12日~16日每天8点开始->完成3个小任务+邀请3人zhu力,领2万杯星巴克免单券👉mp://TzKd93joQAVAdww 助li不在在群里发
Signed Focus on sharing
#频道互推 #相似推荐 ------------------------------ 📢 武汉&女神 📢 天津修车驾校 📢 长春美女综合 📢 杭州资源 📢 免费资源分享频道 📢 苏州醉花间资源分享 📢 北京茶厅 📢 全球资源仓库 📢 清风DJ 狗推音乐 私人定制 📢 惠州金御汇 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
Signed SOSO搜搜
#频道互推 #相似推荐 ------------------------------ 📢 成都资源 📢 七夜公益破解资源分享🇨🇳 📢 🔥🔥ZBook,|电子书📚| 小说|漫画资源||禁书分享 📢 幻宇秘语付费资源 📢 Soul 资源频道 📢 pikpak福利姬资源合集 📢 落雾MoseCheat‑和平精英&PUBG改文件资源频道 📢 郑州·嘉宴厅 📢 【严选】扬州资源 📢 ASMR👂🏻圈圈录播精选 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
Signed SOSO搜搜
SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1001239955639_508980131_soso_25753e95
Signed SOSO搜搜
没进群的可以进群哈,好多活动来不及在这里发,好多需要在微信打开的活动 感兴趣的进哈 《不要用小号加,否则不通过哈》 - 在其他群的不要重复进入!!! ⚠️禁言 否则✈️ ,介意勿入
Signed Focus on sharing
#频道互推 #相似推荐 ------------------------------ 📢 武汉&女神 📢 天津修车驾校 📢 长春美女综合 📢 杭州资源 📢 北猫白嫖分享组🇨🇳 📢 免费资源分享频道 📢 苏州醉花间资源分享 📢 北京茶厅 📢 清风DJ 狗推音乐 私人定制 📢 惠州金御汇 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
Signed SOSO搜搜
Showing the 12 most recent of 105 posts we hold for @sunpojie. 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.
We recorded 2 posts on @sunpojie 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.
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.
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.
@sunpojie 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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.
“🔥 线报|羊毛|羊毛线报福利频道🔥” (@sunpojie), 19,376 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/sunpojie.
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.