Telegram RegisterThe public register of Telegram
Telegram profile photo for 🧧 PHÁT CODE FREE 🧧

Channel

🧧 PHÁT CODE FREE 🧧

@freecode8k

2 usernames

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

31,823subscribers

-19,164 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002413269309
TypeChannel
Usernames@code8k @freecode8k
DescriptionNHẬN CODE 88K + 58K MIỄN PHÍ TẠI: 👉https://code8k.net 👈 🎁🎁🎁🎁🎁🎁🎁🎁🎁🎁🎁🎁 LIÊN HỆ: https://t.me/Nhancodefree8kbet NHÓM : https://t.me/BAOCODE8K2026
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held66
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/freecode8k

Topic

Gambling & betting — 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 90% 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 why it has no browse page of its own yet.

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 word for word 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)
Posted firstThenOverlapGap
@freecode8k/5217 · this entry5 Aug 2026, 06:37 UTC@vipcode8k/52205 Aug 2026, 06:37 UTC1.00under a minute
@freecode8k/5219 · this entry5 Aug 2026, 11:21 UTC@vipcode8k/52225 Aug 2026, 11:21 UTC1.00under a minute
@freecode8k/5224 · this entry6 Aug 2026, 07:07 UTC@vipcode8k/52276 Aug 2026, 07:07 UTC1.00under a minute
@freecode8k/5225 · this entry6 Aug 2026, 08:36 UTC@vipcode8k/52286 Aug 2026, 08:37 UTC1.00under a minute
@freecode8k/5231 · this entry7 Aug 2026, 06:46 UTC@vipcode8k/52357 Aug 2026, 06:46 UTC1.00under a minute
@freecode8k/5232 · this entry7 Aug 2026, 11:33 UTC@vipcode8k/52367 Aug 2026, 11:34 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@vipcode8k12 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (120)

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 0 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 12 comparable posts for this entry, running 5 August 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.

  • 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).

Across the whole group of 2, the earliest publisher we hold is @freecode8k — 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 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

31,82350,98741,4057 August 202619 September 2026
66 measurements spanning 43 days, net -19,164. 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 28,948–53,862 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
19 Sept 2026, 14:1831,823-26
19 Sept 2026, 00:3731,849-108
17 Sept 2026, 03:4031,957-12
16 Sept 2026, 16:1931,969-116
15 Sept 2026, 04:5732,085-1
14 Sept 2026, 17:4032,086-56
13 Sept 2026, 16:5632,142-66
13 Sept 2026, 01:3832,208-255
11 Sept 2026, 20:3832,463-65
11 Sept 2026, 04:0032,528-1,967
9 Sept 2026, 06:5634,495-6,795
8 Sept 2026, 07:3941,290-855
5 Sept 2026, 23:5542,145-395
4 Sept 2026, 23:3642,540-33
3 Sept 2026, 19:3642,573-9
3 Sept 2026, 09:3442,582-84
2 Sept 2026, 09:2642,666no change
2 Sept 2026, 06:4442,666-195
1 Sept 2026, 08:1342,861-44
1 Sept 2026, 05:1242,905first reading

Engagement

308 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 81 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.66%
avg views ÷ 31,823 subscribers
Avg views / post
527
163 posts measured
Reaction rate
7.25%
reactions ÷ views · ER floor
Posts in window
163
of 308 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 141 of 163 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 September 2026
Posts held308 (5 August 202623 September 2026)
Views total85,975
Reactions total5,920
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 19:50 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,520
Videos
783
Links
3,000

Lifetime counters from Telegram’s own channel header, read 23 September 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
16m 31s
Average length
20s

Measured directly from 50 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

8,641 reactions across 256 posts, in 21 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2,81132.5%
🔥1,38516.0%
🎉1,37715.9%
👍1,37715.9%
😁1,02111.8%
👏2863.31%
🥰1021.18%
💯690.799%
❤‍🔥600.694%
😍460.532%
🤩260.301%
🍾200.231%
🎃160.185%
👻150.174%
👎110.127%
🐳80.093%
🌚30.035%
🤔30.035%
🖕20.023%
🤣20.023%
1 further kind10.012%

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 262 of the 308 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 8,641 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 308 most recent posts we hold, published 5 August 2026 to 23 September 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.

Recent posts

23 Sept 2026, 14:14 UTC708 views58 reactionsread 23 September 2026
Video

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 xin mời quý hội viên nhấn vào phần mã 😄😄😃😄được ẩn ở bên dưới 😃😃 1w7frDUA TKNiuQyX B6JTKC36 IRipSTl4 TRg8WkK5 nXjskt14 0Gm1AwEj pXoH81W8 7yUxH74w f39OJZSK jjNXBb59 3G6pYwE9 7kma441x ylTdM85g ux0PdB44 yV2wdvkW 6VfEXOGA jjwS1LQ5 fpE4pEpE 8VVAYesI KV3UkxPA 9doSO8bJ 633m0lw2 w7BozUXS NFmQH3ko sbMY1v0Y w1wRPy

19😁15🔥9👍8🎉7

23 Sept 2026, 13:08 UTC727 views52 reactionsread 23 September 2026
Photo

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 😃 ❤️❤️❤️❤️❤️❤️: nhapcode8k.com 💥 🥲😆😗😊😁 : Click tại đây Click tại đây

15🔥11👍9😁9🎉8

23 Sept 2026, 12:12 UTC720 views55 reactionsread 23 September 2026
Video

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 xin mời quý hội viên nhấn vào phần mã 😄😄😃😄được ẩn ở bên dưới 😃😃 tdXcQcZR AzVxHCt5 5bOgYEEy ksmCGMQi 8aTaWJ2V 1Vk834d1 0yZWvGhT o0leDWe3 1v9d3XeG wRgBpW7Q ILYlIW0u jmNDMhLu EKKO1I7e xC3lMOuA oogFS18O GnZQcan3 81gcXxgw fcjsCKXd 5c2h7Hcv rmyrZTUt ubequnPG UEn5S8sS NDyntURS GR51MK44 LIv7EUsY WkeHlVcp 5pUbeA

21👍14🎉8🔥6😁6

23 Sept 2026, 11:02 UTC710 views53 reactionsread 23 September 2026
Photo

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 😃 ❤️❤️❤️❤️❤️❤️: nhapcode8k.com 💥 🥲😆😗😊😁 : Click tại đây Click tại đây

🔥16😁11🎉109👍7

23 Sept 2026, 08:30 UTC727 views55 reactionsread 23 September 2026
Video

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 xin mời quý hội viên nhấn vào phần mã 😄😄😃😄được ẩn ở bên dưới 😃😃 VpqqFQvr 8HlNxsvK aw5raXrO q3pGX78j aJnUEQ6q 3DCxLhA1 ICiGHkQl RFJZcig1 1w6tS85J 5vBAlDlT QcPzKTN4 m4oX1biP CPLLOvIE skNXjm4Y 8ZlArXr7 6Bzng9Ro zyFOapY0 nrct3b35 LLy7Uibm nDWxKUQN X1OywtbB IrTlqLfz mlUyhgap pMnpVlmJ hUFp08J4 jVaz0cO7 k264iM

13🔥12🎉11😁11👍8

23 Sept 2026, 06:46 UTC727 views54 reactionsread 23 September 2026
Video

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 xin mời quý hội viên nhấn vào phần mã 😄😄😃😄được ẩn ở bên dưới 😃😃 CExGmJEs Zt5bQefW 4PHDqZHu MUCEfwvW k5LPsoCm 7fHXBbz8 28cnvbZV xhmlYMrJ 3Mve3CDQ 8UzSZlxx O6ek9M9Y rJvH2r7A 7hUaFTrS qwYPSQVs 0a0q6gfG iOmrGqAB xrh85D9O cmsFVydT c6o6CtwS 4cbEKPGL PVTd1Nwi wwQhwywU VOW7vz3v 7irohwD4 CjnTIuz6 5mlyBivm TrDLiw

🎉1715🔥11👍8😁3

23 Sept 2026, 05:31 UTC747 views66 reactionsread 23 September 2026
Video

ANH EM TƯƠNG TÁC NHANH HƠN 60 TIM VÀ CÁC CẢM XÚC KHÁC ĐỂ MÌNH LÊN CODE CHO MỌI NGƯỜI NHÉ !!! 🌟🌟🌟

27👍15🎉9🔥9😁6

23 Sept 2026, 00:54 UTC259 views56 reactionsread 23 September 2026
Video

Video, posted without a caption

🔥16👍159🎉8😁8

22 Sept 2026, 20:02 UTC237 views56 reactionsread 23 September 2026
Photo

Photo, posted without a caption

😁16👍1413🎉9🔥4

22 Sept 2026, 14:13 UTC819 views54 reactionsread 23 September 2026
Video

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 xin mời quý hội viên nhấn vào phần mã 😄😄😃😄được ẩn ở bên dưới 😃😃 RX0bjeBb RdQVoQLa oH5imB8i dfSI4dY7 qhnqb7tI IkPEVzo5 sFNUBuxs 9VlKGg5y Gl6bhRRT TwPgFULZ NQT5I0AZ lDHWeprp Yu49bwHK vyNVJDji AgPDYoom C9dARxTg zuEGfZl2 e6yZIhGa sV22qZvt 6zoOeBqh lvTefDf3 boiW3Orq lVf8DH6t yQ1iqA6l Tuc3W0zw MxfZPgRE ZJpOoq

🎉12🔥1211😁10👍9

22 Sept 2026, 13:19 UTC736 views11 reactionsread 23 September 2026
Video

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 xin mời quý hội viên nhấn vào phần mã 😄😄😃😄được ẩn ở bên dưới 😃😃 ySjY1T8v U1Xi2W0d IPzg10S9 9ymM47LF ozhFI2T5 ebWkm2Ns TrvfcjfN EguRTgoH 7iV1bbFd flHUadCD xoWH3bIc qofcaLrv swDRQrjD xJZWAvoX zN4lrwWF rSoDP53W 2k8IaFRW uayVDbjL TgI7pXLG QJEqVyha sjIfVUVn n6ema1le 4XWYuir3 9bAnqVD7 IoGsuyD4 ZTT07296 QOVgB0

4🎉3🔥2👍1🥰1

22 Sept 2026, 12:27 UTC755 views54 reactionsread 23 September 2026
Photo

🌟 Hãy giới thiệu bạn bè cùng nhau tham gia nhận thưởng nhé!!! 🌟 Để nhận được mã😄😄😃😄 tại 🔴🟠🟡 😃 ❤️❤️❤️❤️❤️❤️: nhapcode8k.com 💥 🥲😆😗😊😁 : Click tại đây Click tại đây

😁1614🔥9👍8🎉7

Showing the 12 most recent of 308 posts we hold for @freecode8k. 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“🧧 PHÁT CODE FREE 🧧” (@freecode8k), 31,823 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/freecode8k.

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.