Telegram RegisterThe public register of Telegram
Telegram profile photo for RR88 PHÁT CODE NỔ HŨ - BẮN CÁ

Channel

RR88 PHÁT CODE NỔ HŨ - BẮN CÁ

@CODEFREERR88

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

45,053subscribers

+1,434 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-1002642564627
TypeChannel
Username@CODEFREERR88
Description💛𝗧𝗥𝗔𝗡𝗚 𝗖𝗛Ủ 𝗥𝗥𝟴𝟴: RR88X6.COM 💛𝐂𝐒𝐊𝐇 𝐊𝐇𝐈𝐄̂́𝐔 𝐍𝐀̣𝐈: @khieunaiRR88l 💛𝐂𝐒𝐊𝐇 Đ𝐀̣𝐈 𝐋𝐘́: @CSDL_RR88 💛𝐓𝐄𝐋𝐄 𝐂𝐒𝐊𝐇 𝟐𝟒/𝟕: @RR88CSKH247_BOT 💛𝐅𝐀𝐍𝐏𝐀𝐆𝐄 𝐑𝐑𝟖𝟖 : https://www.facebook.com/TRANGCHURR88OFFICIAL/
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/CODEFREERR88

Topic

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 9 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.

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

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@CODEFREERR88/2035 · this entry14 Jul 2026, 06:22 UTC@GIAITRIRR88_official/59346 Aug 2026, 06:04 UTC1.0023 days
@GIAITRIRR88_official/612722 Aug 2026, 12:04 UTC@CODEFREERR88/2038 · this entry22 Aug 2026, 12:05 UTC1.00under a minute
@CODEFREERR88/2104 · this entry29 Sept 2026, 13:09 UTC@GIAITRIRR88_official/66323 Oct 2026, 14:13 UTC1.004 days
@CODEFREERR88/2137 · this entry17 Oct 2026, 13:36 UTC@GIAITRIRR88_official/678717 Oct 2026, 13:46 UTC1.0010 minutes
@GIAITRIRR88_official/71278 Nov 2026, 11:59 UTC@CODEFREERR88/2196 · this entry17 Nov 2026, 12:04 UTC1.009 days
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
@GIAITRIRR88_official12 (8/8 hand-verifiable sample passed)1.002 days@GIAITRIRR88_official (8–4)

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. 7 of the 7 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 178 comparable posts for this entry, running 14 April 2026 to 17 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @CODEFREERR88 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 18 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 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.

Growth

43,55845,05344,305.57 August 202618 November 2026
62 measurements spanning 103 days, net +1,434. 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 43,334–45,277 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
18 Nov 2026, 06:4845,053+58
15 Nov 2026, 03:0844,995+59
11 Nov 2026, 22:1844,936+51
9 Nov 2026, 23:4844,885+10
8 Nov 2026, 13:4844,875+12
7 Nov 2026, 09:3444,863+8
6 Nov 2026, 07:4744,855+17
4 Nov 2026, 03:4744,838-2
2 Nov 2026, 03:1744,840+5
1 Nov 2026, 01:2844,835+16
31 Oct 2026, 02:5144,819+1
30 Oct 2026, 02:4744,818-11
29 Oct 2026, 04:0944,829-14
27 Oct 2026, 22:5944,843+25
27 Oct 2026, 00:0144,818-4
25 Oct 2026, 20:5844,822-3
24 Oct 2026, 22:3044,825-1
23 Oct 2026, 23:1944,826-8
22 Oct 2026, 23:1944,834+19
21 Oct 2026, 20:0744,815first reading

Engagement

184 posts held, back to 14 April 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 201 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.21%
avg views ÷ 45,053 subscribers
Avg views / post
1,450
61 posts measured
Reaction rate
0.278%
reactions ÷ views · ER floor
Posts in window
62
of 184 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 56 of 61 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 18 November 2026
Posts held184 (14 April 2026 – 18 November 2026)
Views total88,304
Reactions total233
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 08:26 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,540
Videos
≈279
Links
≈2,050

Lifetime counters from Telegram’s own channel header, read 18 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
20s
Average length
20s

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.

Reaction mix

1,984 reactions across 173 posts, in 6 distinct kinds. The most used accounts for 91.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,82091.7%
👌462.32%
👍432.17%
👏301.51%
🥰251.26%
🔥201.01%

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 176 of the 184 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 1,984 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 184 most recent posts we hold, published 14 April 2026 to 18 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.

Recent posts

Telegram’s own ‘edited’ marker: 8 of 62 posts held from the last 30 days (12.9%) 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).

18 Nov 2026, 06:00 UTC≈4,020 views2 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🔥 𝐇À𝐍𝐇 𝐓𝐑Ì𝐍𝐇 𝐓𝐇𝐈Ệ𝐍 𝐍𝐆𝐔𝐘Ệ𝐍 𝐂𝐇𝐈𝐀 𝐒Ẻ 𝐋𝐈𝐕𝐄𝐒𝐓𝐑𝐄𝐀𝐌 𝐓𝐑𝐈 Â𝐍 𝐍𝐆ƯỜ𝐈 𝐓𝐇Ầ𝐘 𝐕Ù𝐍𝐆 𝐂𝐀𝐎, 𝐍𝐇Ậ𝐍 𝐂𝐎𝐃𝐄 🔥 🩷🩷🩷 🔹🔸🔹🔸🔹🔸 🩷🩷🩷𝐌Ã 𝐊𝐇𝐔𝐘Ế𝐍 𝐌Ã𝐈 🩷🩷🩷 CS20-11 🔹🔸🔹🔸🔹🔸 ♥️ Nhân dịp 𝗡𝗚À𝗬 𝗡𝗛À 𝗚𝗜Á𝗢 𝗩𝗜Ệ𝗧 𝗡𝗔𝗠 🟧🟧🟧🟧🟧, 🙁😤 trân trọng lan tỏa những giá trị nhân văn thông qua hành trình thiện nguyện, gửi lời tri ân đến những người thầy, người cô thầm lặng vượt khó, mang tri thức đến trẻ em vùng cao. Mỗi sự sẻ chia là …

❤2

18 Nov 2026, 03:20 UTC245 views1 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 💥𝐍Ạ𝐏 𝐓𝐈Ề𝐍 𝐋Ầ𝐍 👌 𝐓𝐇ƯỞ𝐍𝐆 𝐋Ê𝐍 ĐẾ𝐍 🟥🟥🟥🟥🟥 Đ𝐈Ể𝐌💥 ✨✨✨ 🔹🔸🔹🔸🔹🔸 ✨✨✨✨𝐌Ã 𝐊𝐇𝐔𝐘Ế𝐍 𝐌Ã𝐈 ✨✨✨✨ NL03 ✨✨✨✨🔹🔸🔹🔸🔹🔸 📢Tiếp nối ưu đãi từ lần nạp thứ 2 , sang lần thứ 🔠, 🙁😤 tiếp tục mang đến cơ hội nhận thêm tiền thưởng hấp dẫn . ⏺𝐒Ố 𝐓𝐈Ề𝐍 𝐍Ạ𝐏 𝐓Ừ 🔠🔠🔠+ Đ𝐈Ể𝐌 ⏺𝐂Ơ 𝐇Ộ𝐈 𝐍𝐇Ậ𝐍 𝐓𝐇ƯỞ𝐍𝐆 𝐓Ớ𝐈 🟥🟥🟥🟥🟥 Đ𝐈Ể𝐌 ⏺𝐂𝐇Ỉ 𝐂Ầ𝐍 𝐇𝐎À𝐍 𝐓𝐇À𝐍𝐇 𝐱😀 𝐕Ò𝐍𝐆 𝐂ƯỢ𝐂 ❎Khuyến mãi không áp dụng đối với sản phẩm XỔ SỐ. ❎Khuyến mãi này không nhận song hành v…

❤1

18 Nov 2026, 00:03 UTC301 viewsread 18 November 2026
Video

😀😀😃😁😄😆🥹😅😂🥲☺️😃 😀😀😀😀😀😀- ĐĂNG KÍ TÀI KHOẢN TẶNG 🥵😎🔠 TRẢI NGHIỆM 👌👌👌👌👌 MÃ : KM58K 💚❤️💚❤️‍🔥💛🧡💛💚💚 🔥Tất cả các thành viên mới của 🙁😤 sau khi tải APP và đăng kí tài khoản, thành viên sẽ được nhận 🥵😎 điểm miễn phí từ hệ thống. 👾CÁCH THAM GIA : 🤠Thành viên sau khi tải APP và liên kết tài khoản thành công hội viên cần chọn ĐĂ𝗡𝗚 𝗞Í 𝗧Ạ𝗜 ĐÂ𝗬 để được nhận KHUYẾN MÃI ⭐ ĐIỀU KIỆN KHUYẾN MÃI : 😬THÀNH VIÊN MỚI TẢ…

17 Nov 2026, 14:09 UTC≈4,190 views2 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ĐÃ BẮT ĐẦU🔥 😉😉😉SĂN ❤️🫰MIỄN PHÍ 😉😉😉ANH EM ƠI, VÀO LIVE NGAY! 😉😉😉😉 🥵🥵🥵🥵 😉 😉😉😉 😉 😉😉😉🔴🔴🔴🔴 🔴🔴🔴🔴 🎁 🙁😤 mỗi ngày mở 😘 PHIÊN LIVE để 😀😀😀😀😀😀😀😀anh em hội viên cùng nhau vào săn ❤️🫰ngay thôi nào. 🔔 Mỗi ngày 0️⃣ khung giờ 😀😀😀: ⏰ 𝐋𝐈𝐕𝐄 𝐆𝐀𝐌𝐄:🔢🔢 - 🔢🔢 🌙 𝐋𝐈𝐕𝐄 𝐒𝐄𝐗: 🔢🔢 – 🔢🔢 📌 ANH EM NHỚ CANH GIỜ! Code xuất hiện là phải NHANH TAY – NHANH MẮT 🎯🔥 Đừng để vuột mất những mã code hấp dẫn!…

❤2

17 Nov 2026, 13:09 UTC466 viewsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ĐÃ BẮT ĐẦU🔥 😉😉😉SĂN ❤️🫰MIỄN PHÍ 😉😉😉ANH EM ƠI, VÀO LIVE NGAY! 😉😉😉😉 🥵🥵🥵🥵 😉 😉😉😉 😉 😉😉😉 💗💗💗 🎁 🙁😤 mỗi ngày mở 😘 PHIÊN LIVE để 😀😀😀😀😀😀😀😀anh em hội viên cùng nhau vào săn ❤️🫰ngay thôi nào. 🔔 Mỗi ngày 0️⃣ khung giờ 😀😀😀: ⏰ 𝐋𝐈𝐕𝐄 𝐆𝐀𝐌𝐄:🔢🔢 - 🔢🔢 🌙 𝐋𝐈𝐕𝐄 𝐒𝐄𝐗: 🔢🔢 – 🔢🔢 📌 ANH EM NHỚ CANH GIỜ! Code xuất hiện là phải NHANH TAY – NHANH MẮT 🎯🔥 Đừng để vuột mất những mã code hấp dẫn…

17 Nov 2026, 13:05 UTC≈1,570 viewsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 ✍️ 🤩🤩🤩🤩 ⭐⭐⭐⭐⭐🔞 — CÀNG NHÌN, CÀNG KHÓ DỨT 😟 😍😍😍😍 😍😍😍😍 Ánh mắt đầy mê hoặc.🤩 😍😍😍😍 Nụ cười nửa kín nửa hở.🥴 😍😍😍😍 Một chút ngọt ngào…🤕 😍😍😍😍 Khiến bạn không thể rời mắt 😍😍😍😍 😍😍😍😍 Đêm nay, những 🤩🤩🤩🤩 quyến rũ nhất sẽ trực tiếp lên sóng. Không khoảng cách. Không cần chờ đợi. Bạn nhìn thấy họ — và họ biết bạn đang ở đó. 🖕💃 🔥 Visual nóng bỏng 💋 Thần thái quyến rũ 👅 Những ánh nhìn đầy ẩn ý 🫦 ONLY — DÀNH CHO K…

17 Nov 2026, 12:04 UTC≈1,290 views1 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🔥 SẮP ĐẾN GIỜ LÊN SÓNG! 🔥 🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩 ➖➖➖➖➖➖ 🤩🤩🤩🤩 💗💗💗 🤩🤩🤩🤩 ⭐⭐⭐⭐⭐ 🔣 ⭐⭐⭐⭐⭐ Một buổi 🤩🤩🤩🤩🤩🤩 đặc biệt đang được chuẩn bị với hàng loạt nội dung hấp dẫn! 👀 🎁 SĂN 👌👌 TRÊN 🔴🔴 🎮 MINIGAME TƯƠNG TÁC 🎉 QUÀ TẶNG & NHỮNG BẤT NGỜ ĐẶC BIỆT 🔥Không khí sôi động, tương tác liên tục cùng 🤩🤩🤩🤩 ⏰ Đừng vào muộn! 👌👌 và minigame có thể xuất hiện trong suốt buổi LIVE — …

❤1

16 Nov 2026, 14:17 UTC≈8,930 views6 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ĐÃ BẮT ĐẦU🔥 😉😉😉SĂN ❤️🫰MIỄN PHÍ 😉😉😉ANH EM ƠI, VÀO LIVE NGAY! 😉😉😉😉 🥵🥵🥵🥵 😉 😉😉😉 😉 😉😉😉 💙💙💙💙 🎁 🙁😤 mỗi ngày mở 😘 PHIÊN LIVE để 😀😀😀😀😀😀😀😀anh em hội viên cùng nhau vào săn ❤️🫰ngay thôi nào. 🔔 Mỗi ngày 0️⃣ khung giờ 😀😀😀: ⏰ 𝐋𝐈𝐕𝐄 𝐆𝐀𝐌𝐄:🔢🔢 - 🔢🔢 🌙 𝐋𝐈𝐕𝐄 𝐒𝐄𝐗: 🔢🔢 – 🔢🔢 📌 ANH EM NHỚ CANH GIỜ! Code xuất hiện là phải NHANH TAY – NHANH MẮT 🎯🔥 Đừng để vuột mất những mã code hấp dẫ…

❤6

16 Nov 2026, 13:06 UTC≈3,900 views3 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ĐÃ BẮT ĐẦU🔥 😉😉😉SĂN ❤️🫰MIỄN PHÍ 😉😉😉ANH EM ƠI, VÀO LIVE NGAY! 😉😉😉😉 🥵🥵🥵🥵 😉 😉😉😉 😉 😉😉😉 🧩🧩🧩🧩🧩 🎁 🙁😤 mỗi ngày mở 😘 PHIÊN LIVE để 😀😀😀😀😀😀😀😀anh em hội viên cùng nhau vào săn ❤️🫰ngay thôi nào. 🔔 Mỗi ngày 0️⃣ khung giờ 😀😀😀: ⏰ 𝐋𝐈𝐕𝐄 𝐆𝐀𝐌𝐄:🔢🔢 - 🔢🔢 🌙 𝐋𝐈𝐕𝐄 𝐒𝐄𝐗: 🔢🔢 – 🔢🔢 📌 ANH EM NHỚ CANH GIỜ! Code xuất hiện là phải NHANH TAY – NHANH MẮT 🎯🔥 Đừng để vuột mất những mã code hấp d…

❤3

15 Nov 2026, 14:07 UTC≈2,380 views4 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ĐÃ BẮT ĐẦU🔥 😉😉😉SĂN ❤️🫰MIỄN PHÍ 😉😉😉ANH EM ƠI, VÀO LIVE NGAY! 😉😉😉😉 🥵🥵🥵🥵 😉 😉😉😉 😉 😉😉😉 💗💗💗💗 🎁 🙁😤 mỗi ngày mở 😘 PHIÊN LIVE để 😀😀😀😀😀😀😀😀anh em hội viên cùng nhau vào săn ❤️🫰ngay thôi nào. 🔔 Mỗi ngày 0️⃣ khung giờ 😀😀😀: ⏰ 𝐋𝐈𝐕𝐄 𝐆𝐀𝐌𝐄:🔢🔢 - 🔢🔢 🌙 𝐋𝐈𝐕𝐄 𝐒𝐄𝐗: 🔢🔢 – 🔢🔢 📌 ANH EM NHỚ CANH GIỜ! Code xuất hiện là phải NHANH TAY – NHANH MẮT 🎯🔥 Đừng để vuột mất những mã code hấp dẫn!…

❤4

15 Nov 2026, 13:05 UTC819 views2 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ĐÃ BẮT ĐẦU🔥 😉😉😉SĂN ❤️🫰MIỄN PHÍ 😉😉😉ANH EM ƠI, VÀO LIVE NGAY! 😉😉😉😉 🥵🥵🥵🥵 😉 😉😉😉 😉 😉😉😉 😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️ 🎁 🙁😤 mỗi ngày mở 😘 PHIÊN LIVE để 😀😀😀😀😀😀😀😀anh em hội viên cùng nhau vào săn ❤️🫰ngay thôi nào. 🔔 Mỗi ngày 0️⃣ khung giờ 😀😀😀: ⏰ 𝐋𝐈𝐕𝐄 𝐆𝐀𝐌𝐄:🔢🔢 - 🔢🔢 🌙 𝐋𝐈𝐕𝐄 𝐒𝐄𝐗: 🔢🔢 – 🔢🔢 📌 ANH EM NHỚ CANH GIỜ! Code xuất hiện là phải NHANH TAY – NHANH MẮT 🎯🔥 Đừng để vuột mất những mã c…

❤2

14 Nov 2026, 14:07 UTC957 views4 reactionsread 18 November 2026
Photo

😀😀😃😁😄😆🥹😅😂🥲☺️😃 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ĐÃ BẮT ĐẦU🔥 😉😉😉SĂN ❤️🫰MIỄN PHÍ 😉😉😉ANH EM ƠI, VÀO LIVE NGAY! 😉😉😉😉 🥵🥵🥵🥵 😉 😉😉😉 😉 😉😉😉 🩵🩵🩵🩵🩵 🎁 🙁😤 mỗi ngày mở 😘 PHIÊN LIVE để 😀😀😀😀😀😀😀😀anh em hội viên cùng nhau vào săn ❤️🫰ngay thôi nào. 🔔 Mỗi ngày 0️⃣ khung giờ 😀😀😀: ⏰ 𝐋𝐈𝐕𝐄 𝐆𝐀𝐌𝐄:🔢🔢 - 🔢🔢 🌙 𝐋𝐈𝐕𝐄 𝐒𝐄𝐗: 🔢🔢 – 🔢🔢 📌 ANH EM NHỚ CANH GIỜ! Code xuất hiện là phải NHANH TAY – NHANH MẮT 🎯🔥 Đừng để vuột mất những mã code hấp dẫn…

❤4

Showing the 12 most recent of 184 posts we hold for @CODEFREERR88. 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.

Posts edited after publishing

@CODEFREERR88 edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
28 August 2026
Most recent edit
31 August 2026

Forward network

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.

Mentions

Named by 1 registered channel — 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.

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.

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

“RR88 PHÁT CODE NỔ HŨ - BẮN CÁ” (@CODEFREERR88), 45,053 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/CODEFREERR88.

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.