Channel
@YFYLCVIP
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
421subscribers
+121 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001355130070 |
|---|---|
| Type | Channel |
| Usernames | @yf10608 @YFYLCVIP |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/YFYLCVIP |
Gambling & betting — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @YFYLCVIP/48 · this entry3 Jul 2026, 23:22 UTC | @YFYLCC/2643 Jul 2026, 23:22 UTC | 1.00 | under a minute |
| @YFYLCC/27017 Jul 2026, 21:26 UTC | @YFYLCVIP/55 · this entry17 Jul 2026, 21:26 UTC | 1.00 | under a minute |
| @YFYLCVIP/56 · this entry21 Jul 2026, 04:08 UTC | @YFYLCC/27121 Jul 2026, 04:08 UTC | 1.00 | under a minute |
| @YFYLCVIP/59 · this entry24 Jul 2026, 09:10 UTC | @YFYLCC/27324 Jul 2026, 09:10 UTC | 1.00 | under a minute |
| @YFYLCVIP/61 · this entry24 Jul 2026, 10:43 UTC | @YFYLCC/27524 Jul 2026, 10:44 UTC | 1.00 | 72 seconds |
| @YFYLCVIP/55 · this entry17 Jul 2026, 21:26 UTC | @YFYLCC/27625 Jul 2026, 06:06 UTC | 0.85 | 7 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @YFYLCC | 6 (6/6 hand-verifiable sample passed) | 0.97 | under a minute | this entry (5–1) |
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 1 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 15 comparable posts for this entry, running 3 July 2026 to 7 August 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 @YFYLCVIP — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 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 |
|---|---|---|
| 10 Nov 2026, 17:49 | 421 | +3 |
| 6 Nov 2026, 12:15 | 418 | no change |
| 3 Nov 2026, 07:56 | 418 | +8 |
| 30 Oct 2026, 13:06 | 410 | -2 |
| 26 Oct 2026, 12:56 | 412 | +4 |
| 23 Oct 2026, 13:46 | 408 | +1 |
| 20 Oct 2026, 09:45 | 407 | -7 |
| 16 Oct 2026, 14:06 | 414 | +13 |
| 12 Oct 2026, 13:28 | 401 | +8 |
| 9 Oct 2026, 09:16 | 393 | +24 |
| 1 Oct 2026, 08:01 | 369 | +4 |
| 29 Sept 2026, 15:42 | 365 | +31 |
| 16 Sept 2026, 17:16 | 334 | +2 |
| 14 Sept 2026, 18:19 | 332 | +1 |
| 8 Sept 2026, 15:17 | 331 | -2 |
| 8 Sept 2026, 02:35 | 333 | +8 |
| 30 Aug 2026, 05:53 | 325 | no change |
| 29 Aug 2026, 20:03 | 325 | +11 |
| 23 Aug 2026, 02:13 | 314 | -2 |
| 22 Aug 2026, 10:06 | 316 | first reading |
16 posts held, back to 3 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 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
26 reactions across 10 posts, in 2 distinct kinds. The most used accounts for 92.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 92.3% | |
| 🖕 | 2 | 7.69% |
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 15 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 26 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 3 July 2026 to 7 August 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.
💸💸💸💸💸💸💸💸 周末狂欢流水双重加赠！ 盈丰娱乐每逢周六、周日投注【电子、棋牌、捕鱼】当日有效投注3000起，次日即可申请高达1️⃣8️⃣8️⃣8️⃣🔤流水加赠奖金！周末娱乐福利多，祝大家周末愉快~盈利多多！ 每日首次存款赠送1️⃣0️⃣🔤 （仅限电子、捕鱼游戏） 提款要求：（本金+彩金）3倍流水 笔笔存款赠送5️⃣🔤 （仅限电子、捕鱼游戏） 提款要求：（本金+彩金）两倍流水 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤4🖕2
💸💸💸💸💸💸💸💸 近期高爆游戏 JDB 花开富贵 恭喜老板~ 投注1️⃣0️⃣🔤 狂爆2️⃣4️⃣2️⃣3️⃣ 倍 再次喜提2️⃣4️⃣0️⃣0️⃣0️⃣🔤 大放洪水猛猛爆~~~ 🎉🎉🎉 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
💸💸💸💸💸💸💸💸 近期高爆游戏 JDB 聚宝盆 恭喜老板~ 充值2️⃣0️⃣0️⃣🔤 狂爆3️⃣5️⃣3️⃣2️⃣5️⃣🔤 喜提5️⃣0️⃣0️⃣0️⃣0️⃣🔤 大放洪水猛猛爆~~~ 🎉🎉🎉 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤1
💸💸💸💸💸💸💸💸 近期高爆游戏 JDB 聚宝盆 恭喜老板~ 投注7️⃣🔤2️⃣🔤 狂爆1️⃣5️⃣1️⃣5️⃣ 倍 喜提1️⃣1️⃣0️⃣0️⃣0️⃣🔤 大放洪水猛猛爆~~~ 🎉🎉🎉 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤1
💸💸💸💸💸💸💸💸 周末狂欢流水双重加赠！ 盈丰娱乐每逢周六、周日投注【电子、棋牌、捕鱼】当日有效投注3000起，次日即可申请高达1️⃣8️⃣8️⃣8️⃣🔤流水加赠奖金！周末娱乐福利多，祝大家周末愉快~盈利多多！ 每日首次存款赠送1️⃣0️⃣🔤 （仅限电子、捕鱼游戏） 提款要求：（本金+彩金）3倍流水 笔笔存款赠送5️⃣🔤 （仅限电子、捕鱼游戏） 提款要求：（本金+彩金）两倍流水 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤2
💸💸💸💸💸💸💸💸 尊敬的盈丰娱乐全体会员： 您好！ 由于平台的信誉品牌影响力日益壮大，近期针对同行恶意利用我司盈丰娱乐在东南亚多年经营的信誉及品牌影响力，进行1:1套用我司logo及名称开设假冒杀猪台经营。在此声明，我司并没有开设任何第二平台，请各大客户擦亮眼睛，以免上当受骗。 但凡任何利用特邀彩金等优惠方式进行营销均为诈骗，我司所有活动均在平台活动页展示。 我司官方客服、财务飞机号，均可在平台内进行核对，以免被冒充的假官方人员诈骗。 谨记我司官方人员不会向任何会员索要账号密码，以及接收任何款项【包括打赏】存款，取款均在平台内进行。 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤3
💸💸💸💸💸💸💸💸 周末狂欢流水双重加赠！ 盈丰娱乐每逢周六、周日投注【电子、棋牌、捕鱼】当日有效投注3000起，次日即可申请高达1️⃣8️⃣8️⃣8️⃣🔤流水加赠奖金！周末娱乐福利多，祝大家周末愉快~盈利多多！ 每日首次存款赠送1️⃣0️⃣🔤 （仅限电子、捕鱼游戏） 提款要求：（本金+彩金）3倍流水 笔笔存款赠送5️⃣🔤 （仅限电子、捕鱼游戏） 提款要求：（本金+彩金）两倍流水 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤3
💸💸💸💸💸💸💸💸 近期高爆游戏 PG 麻将胡了2 狂爆1️⃣7️⃣7️⃣0️⃣ 倍 精彩回放 最后时刻逆风翻盘 只要余额不归0 一切皆有可能 大放洪水猛猛爆~~~ 🎉🎉🎉 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤1
💸💸💸💸💸💸💸💸 近期高爆游戏 PG 麻将胡了2 恭喜老板~ 充值1️⃣0️⃣0️⃣0️⃣🔤 投注1️⃣0️⃣🔤 狂爆1️⃣7️⃣7️⃣0️⃣ 倍 喜提1️⃣7️⃣0️⃣0️⃣0️⃣🔤 大放洪水猛猛爆~~~ 🎉🎉🎉 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
💸💸💸💸💸💸💸💸 近期高爆游戏 FC 大过年路路发 恭喜老板~ 充值6️⃣6️⃣🔤 投注3️⃣🔤 狂爆6️⃣0️⃣0️⃣0️⃣ 倍 喜提1️⃣8️⃣0️⃣0️⃣0️⃣🔤 大放洪水猛猛爆~~~ 🎉🎉🎉 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤2
💸💸💸💸💸💸💸💸 周末狂欢流水双重加赠！ 盈丰娱乐每逢周六、周日投注【电子、棋牌、捕鱼】当日有效投注3000起，次日即可申请高达1️⃣8️⃣8️⃣8️⃣🔤流水加赠奖金！周末娱乐福利多，祝大家周末愉快~盈利多多！ 每日首次存款赠送1️⃣0️⃣🔤 （仅限电子、捕鱼游戏） 提款要求：（本金+彩金）3倍流水 笔笔存款赠送5️⃣🔤 （仅限电子、捕鱼游戏） 提款要求：（本金+彩金）两倍流水 📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱📱📱 官方网站： WWW.YFYLC.TOP 唯一客服：@kf10608 唯一财务：@kefu199 TG投注机器人：@U1bot
❤4
盈丰娱乐【官方频道】 pinned a photo
Showing the 12 most recent of 16 posts we hold for @YFYLCVIP. 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 9 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.
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.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“盈丰娱乐【官方频道】” (@YFYLCVIP), 421 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/YFYLCVIP.
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.