Telegram RegisterThe public register of Telegram
Telegram profile photo for MB66 - KHO GIF

Channel

MB66 - KHO GIF

@gifmb66

2 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

50,540subscribers

-958 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-1002649488775
TypeChannel
Usernames@gifmb66 @mb666
Description𝐀𝐍 𝐓𝐎À𝐍 - 𝐁Ả𝐎 𝐌Ậ𝐓 - 𝐍Ạ𝐏 𝐑Ú𝐓 𝐍𝐇𝐀𝐍𝐇 𝐂𝐇Ó𝐍𝐆 ✅𝐋𝐢𝐧𝐤 : https://mb66b.com ✅𝐊ê𝐧𝐡 𝐭𝐢𝐧 𝐭ứ𝐜: https://mb66e.asia/cskh/kenhtele ✅𝐊ê𝐧𝐡 𝐠𝐢ả𝐢 𝐭𝐫í: https://mb66e.asia/cskh/kenhtele1 ✅𝐓ả𝐢 𝐚𝐩𝐩: https://mb66e.asia/daily/taiapp
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 September 2026
Measurements held64
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/gifmb66

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

Growth

28,64751,49840,072.550,5407 August 202618 September 2026
64 measurements spanning 42 days, net -958. 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 25,219–54,926 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
18 Sept 2026, 22:3950,540+20,611
18 Sept 2026, 20:5829,929-20,651
16 Sept 2026, 17:3850,580+20,742
16 Sept 2026, 09:1629,838-20,779
14 Sept 2026, 18:2050,617+20,895
14 Sept 2026, 17:1729,722+48
13 Sept 2026, 04:1529,674-20,973
13 Sept 2026, 04:0050,647-40
11 Sept 2026, 09:1950,687+21,135
11 Sept 2026, 06:1729,552-21,182
8 Sept 2026, 15:1750,734+21,272
8 Sept 2026, 11:2129,462-21,354
5 Sept 2026, 11:1650,816+21,485
5 Sept 2026, 02:5929,331-21,527
3 Sept 2026, 15:3750,858+21,663
3 Sept 2026, 06:1429,195-21,697
2 Sept 2026, 05:3450,892+21,790
2 Sept 2026, 01:1629,102+20
1 Sept 2026, 03:4329,082-21,827
1 Sept 2026, 02:0450,909first reading

Engagement

54 posts held, back to 4 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 91 pages 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 54 posts for this entry, the most recent from 22 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
664
Videos
238
Links
737

Lifetime counters from Telegram’s own channel header, read 22 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
19s
Average length
10s

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

88 reactions across 34 posts, in 11 distinct kinds. The most used accounts for 42.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3742.0%
😁3337.5%
👍55.68%
🤣55.68%
👏22.27%
🍌11.14%
🎄11.14%
😍11.14%
😢11.14%
🤔11.14%
🤪11.14%

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 34 of the 54 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 88 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 54 most recent posts we hold, published 4 August 2026 to 22 August 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

22 Aug 2026, 16:40 UTC≈1,100 views8 reactionsread 22 September 2026
Video

@MB66 @FREECODE #MB66 #FUNNY #GIF

8

22 Aug 2026, 16:20 UTC≈1,030 views2 reactionsread 22 September 2026
Video

@MB66 @FREECODE #MB66 #FUNNY #GIF

👏2

22 Aug 2026, 15:58 UTC784 views5 reactionsread 22 September 2026
Video

@MB66 @FREECODE #MB66 #FUNNY #GIF

🤣21🍌1🎄1

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

@gifmb66 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
8 August 2026
Most recent edit
9 August 2026

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.

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

“MB66 - KHO GIF” (@gifmb66), 50,540 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/gifmb66.

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.