Software piracy — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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. 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)
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
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. 16 of the 16 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 230 comparable posts for this entry, running 5 August 2026 to 13 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).
Recorded under the key clone_copy, last confirmed 14 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.
Growth
63 measurements spanning 97 days, net +2,317. 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 12,769–15,782 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)
Subscribers
Change
12 Nov 2026, 01:09
15,434
+20
10 Nov 2026, 05:49
15,414
+16
8 Nov 2026, 17:18
15,398
+12
7 Nov 2026, 07:49
15,386
+12
6 Nov 2026, 08:34
15,374
+19
5 Nov 2026, 09:17
15,355
+15
4 Nov 2026, 11:37
15,340
+31
3 Nov 2026, 10:16
15,309
+44
2 Nov 2026, 08:09
15,265
+21
1 Nov 2026, 06:36
15,244
+20
31 Oct 2026, 07:29
15,224
+105
30 Oct 2026, 09:06
15,119
+108
29 Oct 2026, 06:55
15,011
+16
28 Oct 2026, 08:05
14,995
+14
27 Oct 2026, 05:56
14,981
+13
26 Oct 2026, 06:09
14,968
+13
25 Oct 2026, 04:59
14,955
+3
24 Oct 2026, 08:27
14,952
-1
23 Oct 2026, 06:45
14,953
+8
22 Oct 2026, 09:05
14,945
first reading
Engagement
360 posts held, back to 5 August 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 73 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
11.4%
avg views ÷ 15,434 subscribers
Avg views / post
1,760
100 posts measured
Reaction rate
0.178%
reactions ÷ views · ER floor
Posts in window
102
of 360 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 82 of 100 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 14 November 2026
Posts held
360 (5 August 2026 – 14 November 2026)
Views total
176,128
Reactions total
260
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
14 Nov 2026, 19:17 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
≈1,090
Videos
≈271
Links
≈1,530
Lifetime counters from Telegram’s own channel header, read 14 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.
Video runtime
15m 59s
Average length
1m 00s
Measured directly from 16 videos 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.
Reaction mix
875 reactions across 237 posts, in 21 distinct kinds. The most used accounts for 77.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
680
77.7%
🤣
48
5.49%
😁
27
3.09%
🔥
25
2.86%
🤯
24
2.74%
👏
23
2.63%
🤡
12
1.37%
🤔
6
0.686%
👌
5
0.571%
😍
4
0.457%
😭
4
0.457%
👀
3
0.343%
😱
3
0.343%
🥴
3
0.343%
🌚
2
0.229%
🐳
1
0.114%
💋
1
0.114%
🗿
1
0.114%
😘
1
0.114%
😢
1
0.114%
1 further kind
1
0.114%
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 263 of the 360 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 875 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 360 most recent posts we hold, published 5 August 2026 to 14 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.
Telegram Stars
Stars received
5
across the posts below
Posts paid on
4
of 357 we hold a reading for · 1%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @trollersteamvn. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 360 most recent posts we hold for this entry, published 5 August 2026 to 14 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 23 of 102 posts held from the last 30 days (22.5%) 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).
💠 WQFiles - Quản lý tệp tin
📱 _kolbicz đã phát triển trình quản lý tệp tin cho iOS 27 dựa trên worse_query.
😀 Cần cài đặt bằng chứng chỉ AppGroup. Hỗ trợ iOS 26-27.x.
• Không cần jailbreak.
• Duyệt và chỉnh sửa dữ liệu ứng dụng.
• Sao lưu / khôi phục / xóa ứng dụng.
• Sao lưu qua AirDrop.
• Công cụ dọn dẹp bộ nhớ cache.
• Chỉ dành cho iOS 27 (đã thử nghiệm trên 27.0.1).
🔄 Cập nhật:
⏺️ Giao diện hoàn toàn mới, bổ su…
💠 Filza (phiên bản jailbreak)
👀 Phiên bản chính thức đã tích hợp RootHide (ẩn quyền root).
⏺ http://tigisoftware.com/repo/
⏺ Đối với người dùng RootHide, nếu bạn vẫn đang sử dụng phiên bản 4.0 hoặc các phiên bản trước của "đại ca" (ám chỉ các phiên bản không chính thức), chúng tôi khuyên bạn nên gỡ cài đặt và cài đặt phiên bản chính thức của Filza.
⏺ https://mlgm66.github.io/
⏺ Filza Crack: Mở khóa phiên bản đầy đủ…
IPA Liên Quân Trắng Dành Cho Ae Không Sài IPA Hack Mà Vẫn Muốn Đổi Giọng
đồ ăn cắp nên ko ghi nguồn nhé
CHÚ Ý ĐÂY LÀ IPA TRẮNG< NÊN TIÊM RỒI KÍ MỞ LÊN LOGIN VÀO LÀ ĂN BAN NGAY, có bypas thì tiêm vào
⬇️ iPadn 2.1.1
• Yêu cầu hệ thống tối thiểu: iOS 16.0
• Chức năng tương tự như Asspp/Dlipa (cả hai hiện đã ngừng hoạt động)
Tìm kiếm, tải xuống và cài đặt các ứng dụng bạn sở hữu trên iPhone hoặc iPad. Hỗ trợ các ứng dụng cho iPhone, iPad, Apple TV và Mac, bao gồm cả các phiên bản cũ và các ứng dụng đã bị xóa khỏi App Store.
🆕 2.1.1
Bản cập nhật này tập trung vào việc sửa lỗi và tối ưu hóa bố cục. Nó khắc phục sự cố…
Phiên bản chính thức đã có sẵn tiếng Trung.
Hỗ trợ iOS 26 đến iOS 27.3 Beta.
Đây là trình duyệt tệp, trình quản lý dữ liệu ứng dụng và trình dọn dẹp bộ nhớ cache dành cho iOS 27.
Để sử dụng, chứng chỉ cần có quyền App Groups.
🎭 Placard: Ứng dụng tương tác cho hình nền 2.0.2
Duyệt, tạo, cài đặt và quản lý hình nền tương tác PosterBoard trên iOS.
• Tương thích với iOS 26 - iOS 27.2?
• Duyệt các hình nền cộng đồng và nhập các gói .tendies.
• Tạo hình nền video từ các đoạn clip dài tối đa 12 giây.
• Xem và xóa các hình nền đã cài đặt.
🐱 Placard
GestaltX v1.0.8
Giải thích đơn giản: Thêm tính năng hỗ trợ thay đổi âm báo thông báo cho toàn bộ ứng dụng. Cần ghép nối và thu thập đường dẫn âm báo của ứng dụng tương ứng.
📱 Regitela Chế độ giám sát
⏺ Công cụ quản lý và chỉnh sửa hệ thống dành cho iOS 26 / 27, được phát triển bởi nhà phát triển ichitaso. Nó dựa trên công nghệ thoát sandbox worse_query, cho phép truy cập vào các App Group và container hệ thống mà một số ứng dụng thông thường không thể đọc được, từ đó thực hiện việc duyệt, chỉnh sửa hệ thống và thay đổi một số cài đặt thiết bị.
Chế độ giám sát (Supervised Mode): Bật hoặ…
❤2😘1
Signed 𝙈𝙞𝙣𝙞𝙊𝙣 𝙍𝙖𝙧𝙚
Showing the 12 most recent of 360 posts we hold for @trollersteamvn. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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.
Handles this channel named that no longer answer
Dead references
4
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
4
vacant every time we have ever looked
@trollersteamvn named 4 handles 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.
@wumpuscentral named in 2 posts, 6 November 2026 – 8 November 2026
@kagithu named in 1 post, 13 November 2026 – 13 November 2026
@staturnzz named in 1 post, 10 August 2026 – 10 August 2026
@pattern_f_ named in 1 post, 8 August 2026 – 8 August 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
EeveeSpotify IPAs @SpotilifeIPAs · 38,060 Telegram ranks this channel #3 of 14 here — alongside 13 others — read 20 September 2026
deb+dylib插件收集 @deb_dylib · 22,226 Telegram ranks this channel #22 of 23 here — alongside 22 others — read 21 September 2026
TestFlight Link @TestFlightLink · 22,797 Telegram ranks this channel #27 of 32 here — alongside 31 others — read 20 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Trollstore” (@trollersteamvn), 15,434 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/trollersteamvn.
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.