Telegram RegisterThe public register of Telegram
Telegram profile photo for 优米CVV-Shop-Bot 中转频道(Relay Channel)

Channel

优米CVV-Shop-Bot 中转频道(Relay Channel)

@practicalCC

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Cite this entry

2subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003271171313
TypeChannel
Username@practicalCC
Description优米CVV-Shop-Bot 已上押哪吒,扫地僧群(Deposit Group)💬: @nzccg001, @CCSDSG01,上押的押金超过(Deposit>)6000 USDT,老板们可以放心地在 优米CVV-Shop-Bot 里购买CC(Everyone Can Confidently Purchase CC On 优米CVV-Shop-Bot) 优米CVV-Shop-Bot🤖: @YOUMICC_bot WorldCvv 优米(Customer Service): @youmicvv2
Created13 November 2025 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live20 November 2026
Measurements held2
On Telegramt.me/practicalCC

Topic

Hacking & security — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 11 November 2026 and assigned it the closest of 31 fixed categories, at 99% 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 2 other registered channels. 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
@practicalCC/18 · this entry29 Jan 2026, 10:13 UTC@empiricalCC/1829 Jan 2026, 10:13 UTC1.00under a minute
@practicalCC/19 · this entry29 Jan 2026, 10:16 UTC@empiricalCC/1929 Jan 2026, 10:16 UTC1.00under a minute
@practicalCC/20 · this entry29 Jan 2026, 10:19 UTC@empiricalCC/2029 Jan 2026, 10:19 UTC1.00under a minute
@practicalCC/21 · this entry29 Jan 2026, 10:22 UTC@empiricalCC/2129 Jan 2026, 10:22 UTC1.00under a minute
@practicalCC/22 · this entry29 Jan 2026, 10:27 UTC@empiricalCC/2229 Jan 2026, 10:27 UTC1.00under a minute
@massCCS/1829 Jan 2026, 10:13 UTC@practicalCC/18 · this entry29 Jan 2026, 10:13 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
@empiricalCC5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (5–0)
@massCCS5 (5/5 hand-verifiable sample passed)1.00under a minute@massCCS (5–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 5 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 5 comparable posts for this entry, running 29 January 2026 to 29 January 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 @massCCS. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · 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.

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

27 August 2026 — 2 subscribers14 August 2026 — 2 subscribers7 August 202614 August 2026
2 measurements spanning 6 days. 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 01:472no change
7 Aug 2026, 18:182first reading

Engagement

8 posts held, back to 13 November 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 1 page 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 8 posts for this entry, the most recent from 25 February 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

29 Jan 2026, 10:27 UTC6 viewsread 14 August 2026

优米CVV-Shop-Bot🏠: @YOUMICC_bot,WorldCvv 优米🙂:: @youmicvv2 优米CVV-Shop-Bot 是 7×24小时自助售卖CC的机器人商店,里面的CC都是纯二手CC毛料,价格低!资料全!数据多!信用足!在哪吒群扫地僧群💬都有上押🖥: @nzccg001 @CCSDSG01,哪吒群扫地僧群上押的押金超过6000 USDT!老板们可以放心地在 优米CVV-Shop-Bot 里购买CC! Youmi CVV-Shop-Bot🏠: @YOUMICC_bot, WorldCvv Youmi🙂: @youmicvv2 Youmi CVV-Shop-Bot Is A 24/7 Self-Service Robot Shop Selling CC ,All CCs Are Pure Second-Hand Raw Materials, Low Prices, Complete Informatio…

29 Jan 2026, 10:22 UTC5 viewsread 14 August 2026

优米CVV-Shop-Bot🏠: @YOUMICC_bot,WorldCvv 优米🙂: @youmicvv2 欢迎大家将我的7×24小时自助售卖CC机器人商店,飞机号,推荐给更多有需要的人! Youmi CVV-Shop-Bot🏠: @YOUMICC_bot, WorldCvv Youmi🙂: @youmicvv2 Welcome Everyone To Recommend my 24/7 Self-Service Vending CC Robot Shop (Telegram) To More people Who Need It!

29 Jan 2026, 10:19 UTC5 viewsread 14 August 2026

优米CVV-Shop-Bot🏠: @YOUMICC_bot WorldCvv 优米(Online Customer Service)🙂: @youmicvv2 已上押哪吒,扫地僧群💬(Deposit Group💬)🖥 @nzccg001, @CCSDSG01,上押的押金超过(Deposit>)6000 USDT 老板们可以放心地在 优米CVV-Shop-Bot 里购买CC(Everyone Can Confidently Purchase CC On 优米CVV-Shop-Bot) 现在有充值赠送礼金活动,详情可以咨询 WorldCvv 优米(There's Currently A Recharge Bonus Promotion. For Details, Please Contact Our Online Customer Service)

29 Jan 2026, 10:16 UTC6 viewsread 14 August 2026

优米CVV-Shop-Bot🏠: @YOUMICC_bot,在哪吒群扫地僧群都有上押💬(Already Deposited Groups💬)🖥: @nzccg001 @CCSDSG01,哪吒群扫地僧群上押的押金超过(Deposit>)6000 USDT,老板们可以放心地在 优米CVV-Shop-Bot 里购买CC(Everyone Can Confidently Purchase CC On 优米CVV-Shop-Bot)!现在有充值赠送礼金活动,详情可以咨询 WorldCvv 优米🙂: @youmicvv2(There's Currently A Recharge Bonus Promotion. For Details, Please Contact Our Online Customer Service: @youmicvv2)

29 Jan 2026, 10:13 UTC5 viewsread 14 August 2026

7×24小时自助售卖CC机器人商店(7×24 Hours CVV Self-Service Robot Store)🏠: @YOUMICC_bot,纯二手CC毛料,价格低!资料全!数据多!信用足!(&Second-Hand CC&Low Price!&Full Data!&More Data!&Good Credit)WorldCvv 优米(Online Customer Service)🙂: @youmicvv2。在哪吒群扫地僧群都有上押💬(Already Deposited Groups💬)🖥: @nzccg001 @CCSDSG01

Showing the 8 most recent of 8 posts we hold for @practicalCC. 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.

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

“优米CVV-Shop-Bot 中转频道(Relay Channel)” (@practicalCC), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/practicalCC.

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.