Channel
@bk6633
On this record: Topic ยท Observations ยท Channels linked by matching posts ยท Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Citations ยท Cite this entry
8,925subscribers
-1,487 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of 3,162โ10,000.
| Telegram ID | -1002352036043 |
|---|---|
| Type | Channel |
| Username | @bk6633 |
| Created | Between 1 September 2024 and 31 March 2025 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 40 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/bk6633 |
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 11 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 |
|---|---|---|---|
| @bk6616/341814 Aug 2026, 08:28 UTC | @bk6633/8418 ยท this entry14 Aug 2026, 08:29 UTC | 1.00 | 2 minutes |
| @bk6616/342220 Aug 2026, 21:13 UTC | @bk6633/8454 ยท this entry20 Aug 2026, 21:16 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @bk6616 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 2 minutes | @bk6616 (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. 2 of the 2 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 52 comparable posts for this entry, running 4 August 2026 to 11 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 @bk6616. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 12 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 |
|---|---|---|
| 12 Nov 2026, 06:56 | 8,925 | -165 |
| 8 Nov 2026, 12:05 | 9,090 | -143 |
| 4 Nov 2026, 23:09 | 9,233 | +29 |
| 2 Nov 2026, 06:39 | 9,204 | +47 |
| 30 Oct 2026, 01:48 | 9,157 | -76 |
| 26 Oct 2026, 23:39 | 9,233 | -62 |
| 24 Oct 2026, 07:57 | 9,295 | -52 |
| 21 Oct 2026, 01:00 | 9,347 | -47 |
| 18 Oct 2026, 07:37 | 9,394 | -87 |
| 15 Oct 2026, 02:00 | 9,481 | -161 |
| 11 Oct 2026, 11:18 | 9,642 | -265 |
| 4 Oct 2026, 23:20 | 9,907 | -113 |
| 27 Sept 2026, 19:38 | 10,020 | -1,839 |
| 17 Sept 2026, 17:17 | 11,859 | -92 |
| 15 Sept 2026, 11:56 | 11,951 | -463 |
| 13 Sept 2026, 19:57 | 12,414 | -921 |
| 12 Sept 2026, 00:01 | 13,335 | -28 |
| 9 Sept 2026, 15:00 | 13,363 | -19 |
| 6 Sept 2026, 04:59 | 13,382 | -45 |
| 4 Sept 2026, 01:56 | 13,427 | first reading |
100 posts held, back to 4 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 61 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 11 November 2026 |
|---|---|
| Posts held | 100 (4 August 2026 โ 11 November 2026) |
| Views total | 8,719 |
| Reactions total | โ |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 12 Nov 2026, 00:12 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.
Measured directly from 5 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.
6 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 3 | 50.0% | |
| ๐ | 3 | 50.0% |
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 5 of the 100 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 6 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 100 most recent posts we hold, published 4 August 2026 to 11 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โs own โeditedโ marker: 0 of 32 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).
#็ๅบๅ้ ๐ฎ็ปๅค้ข็๏ผ่ๆฟ่ฏดๅฟซๆฒกๅไบ็้ซๅ๐ฅ ๐๐ๆๅไธ็น็นๅญๅผน๏ผๆๆญป 33600ๅ #ๅญๅฐ้ฆ ็ๅป๐๐๐ไธไบฟ๏ผ โก๏ธโก๏ธ ๆญๅ่ๆฟ๏ผไธๅ๐๐๐๐๐RMB~ ๐๐๐๐๐๐๐๐๐
#็ๅบๅ้ ๐ฎ่ๆฟๆฏๆฅ็จณๅฎๆๆฌพ~ ๐ฅ ่ๆฟไปๅคฉๅๅคงๅไบ๏ผ็ดๆฅไธไธชbossๆดๅป๐๐๐๐๐ๅ๏ผ4๏ธโฃ0๏ธโฃ0๏ธโฃ0๏ธโฃไบบๆฐๅธ๏ผ๏ผไธๅทๅฐไธๅ๏ผไธ็ดๅจไธ้ฑผ ๐ฅ ่ๆฟไธๅ1๏ธโฃ5๏ธโฃ0๏ธโฃuu~๏ผๆๆฌพ2๏ธโฃ7๏ธโฃ0๏ธโฃ0๏ธโฃuu~ ๐๐๐๐๐๐๐๐๐
#็ๅบๅ้ ๐คไธไธชๅฏ่ฝๆฏๅถ็ถ๏ผไฝๅฆๆๆ่ฏดๆฅไธๆฅๅพๅคไบบ้ฝๅจไธๅไธญๅข๏ผ ๆญๅๅฆไธไฝๅคงๅฅไพๆงๆฏไปฅๅฐๅๅคง~ โ๏ธ้ช็ต่ฌ็้ๅบฆ ้ท้่ฌ็ๆๆฎต๏ผๆญๅๅคงๅฅๆดๅป๐๐๐๐๐eๆๅๆๆฌพ๐๐๐uu๏ผ๏ผ ๐๐๐๐๐๐๐
Signed ่น้ฟๆณขๅ 3Dๆ้ฑผ
#็ๅบๅ้ ๐ฐ้ฑ่ขๅญๅๆผ้ฃๅฏ๏ผๆญๅๅคงๅฅไป ็จ๐๐๐๐eๅฎๆๅๅๆดๅป๏ผๅๆถ๐๐๐๐๐eๆๅๆๆฌพ๐๐๐uu่ฐ็ไบไธ็พกๆ ~~ ๐ไปๆๅนธ่ฟๅฅณ็ฅๅฐไผ็ท้กพๆๆไธๅ็ไบบ๏ผๅคงๅฅๅๆฌพไบๆไปๅจ็งๅบไธญ๏ผ้่ฆ็่ๆฟๆปดๆปด๏ผ๏ผ ๐๐๐๐๐๐๐
Signed ่น้ฟๆณขๅ 3Dๆ้ฑผ
#็ๅบๅ้ ๐ฎ่ๆฟๆฏๆฅ็จณๅฎๆๆฌพ~ ่ๆฟ็ฌฌไธๆฌก็ฉๅฐฑๆดๅป๐๐๐๐๐ไบฟ๏ผๅคช็ไบ๏ผ๏ผ๏ผ 3๏ธโฃ0๏ธโฃ0๏ธโฃไบบๆฐๅธๆๅๆๆฌพ2๏ธโฃ6๏ธโฃ6๏ธโฃ1๏ธโฃไบบๆฐๅธ ๐๐๐ ๐๐๐๐
#็ๅบๅ้ ๐ฎ่ๆฟๆฏๆฅ็จณๅฎๆๆฌพ~ ๐ฅ่ฟไธชๅคงๅฅๅคช็้ผไบ๏ผ๏ผๅฟ่ฎฐ่ฐ็ฎๅฐ็๐๐๐๐๐ๅ๏ผ ๐ฅๆฅ็ๆข ๅผไบๅบฆๆดๅป๐๐๐๐๐๐ๅ๏ผ่ฟๆฏๅฟ่ฎฐ่ฐ็ฎๅฐ๏ผ็ดๆฅ้ๅคฑ 2๏ธโฃไธไบบๆฐๅธๅ๏ผ ๐ๅฅฝๅจๆ็ป่ๆฟๆๆฌพ3๏ธโฃ3๏ธโฃ1๏ธโฃ0๏ธโฃไบบๆฐๅธ๏ผๆดๆขๅๆฌพๅทๆฅ็ๆ๏ผ
#็ๅบๅ้ ๐ฎ่ๆฟๆฏๆฅ็จณๅฎๆๆฌพ~ ๐ฅๆ็ป่ๆฟๆ้ๆๅ ๅท๏ผ็ดๆฅ่ฎฉ่ๆฟๆ็ฝไบ๏ผไธๆก้ฑผๅฐฑ็ธไบ3๏ธโฃ0๏ธโฃ0๏ธโฃ0๏ธโฃไบบๆฐๅธ ๐ฅ่ๆฟๅๅผๅง่ฟไธไฟกไปปๆ๏ผ่ฐ็ฅ้ๆๅๆๆฌพ๐๐๐uu๏ผ~ ๅๆฌพๅท่ฟๆ๏ผ้่ฆๆๆฌพ็่ๆฟๅฟซๆฅ็งไฟกๆ
#็ๅบๅ้ ๐ฎ่ๆฟๆฏๆฅ็จณๅฎๆๆฌพ~ ๐ฅๆๆฌพๆ ้ๅค่จ๏ผ่ๆฟไธๅทไป ้5๏ธโฃๅ้๏ผๆๆฌพ4๏ธโฃ9๏ธโฃ0๏ธโฃuu~ ๐ฅ็ป่ๆฟๅฝปๅบ็ฉ็ฝไบ๏ผไธไธช๐๐๐๐็ดๆฅๆดๅป๐๐๐๐๐ๅ ๐๐๐ ๐๐๐๐
#็ๅบๅ้ ๐ฎ่ๆฟๆฏๆฅ็จณๅฎๆๆฌพ~ ๐ไปๆฅๅคๆ็ฅ็ไบๆๅท๏ผ่ๆฟๆไฝๆพๆฐด็ๅฅฝๆถๆบ~ๆดๅป๐๐๐๐๐ไบฟ๏ผ๏ผ ๐ฅ่ๆฟๅผไนไธๆก้ฑผ้ฝ็ไบ๐๐๐๐ไบบๆฐๅธ๏ผ่ฟ่ฟไธไปไน็ญ๏ผๅคงๅฎถๅฟซๆฅๆพๆๆ้ฑผ~ ๐๐๐๐๐๐๐๐
#็ๅบๅ้ ๅ็ไบ~๏ผ๐ ่ๆฟ็ๅ๐๐๐๐๐ไบฟ๏ผๆๆฌพ๐๐๐๐R~๏ผ ๐๐๐๐๐๐๐ๆธๅบๆ็ปญๆพๆฐดไธญ~๏ผ๐๐๐๐ๅๆฐ้ซ๏ผๅฎนๆ็~ ้่ฆๅๆฌพ่ดฆๅท็่ๆฟ็งไฟกๆ~๏ผ๐๐๐ ๐๐๐๐๐๐๐๐๐
#็ๅบๅ้ ๐ฎๆฏๆฅๅคงๅฅ็จณๅฎๆๆฌพ~~ ๐ฅ๐ฅ่ๆฟๅคช็ไบไธๅ๐๐๐๐๐ไบฟ ไธๅ็ดๆฅๆขๅทๅๆฌก็ๅ๐๐๐๐๐ไบฟ ไน่่ฟฝๅปๆถๅฐพไธๅ๐๐๐๐๐ไบฟโผ๏ธโผ๏ธ ๅ่ฎกๆๆฌพ๐๐๐๐๐๐๐ฐ๐ฐ๐ฐ ๐๐๐๐๐๐๐ๆธธๆๆดๆฐๅคงๆพๆฐด~๏ผ๐๐๐๐่ตทๆญฅๅๆฐ่ถ ้ซ๏ผๅฎนๆ็~ ๅคงๆฐดๆ็ปญไธญ โผ๏ธ้่ฆๅๆฌพๅท็่ๆฟ็งไฟกๆ~๏ผ๐๐๐ ๐๐๐๐๐๐๐๐๐
#็ๅบๅ้ ๐ฐ๐ฐๅผๅฑไธๆก้ฑผ ้ๅฎ่ๅฑ๏ผๆญๅๅคงๅฅๆฉไธ็ฌฌไธไธชไธๅ๏ผ๏ผ๐ฐ๐ฐ ๐่่ดๅ จๅจๆ้ด๏ผ ๐๐๐ ไบฟ็ฎๅปๆ๐๐๐๐๐ๅ #่่ฎ้็ ๅ้ฑผ่ทๅพ้ๅธ๐๐๐๐๐๐eไปทๅผ๐๐๐๐๐RMB!! ๐ๆ็ปๅๆฌกๅคงๅฅๅๆ๐๐๐๐uu็ปง็ปญๅผๅท็ปง็ปญๆดๅป~~ ๐๐๐๐๐๐๐
Signed ่น้ฟๆณขๅ 3Dๆ้ฑผ
Showing the 12 most recent of 100 posts we hold for @bk6633. 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.
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.
Named by 26 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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 12 November 2026 โ this entry's latest reading, not the date you are reading this.
โ่น้ฟ๐ๆณขๅ ๆ้ฑผ็ๅบๅ้โ (@bk6633), 8,925 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/bk6633.
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.