Telegram RegisterThe public register of Telegram
Telegram profile photo for ็บข้ฆ†๐—›๐—ข๐—ก๐—š๐—จ๐—”๐—ก๏ฝœ่ฟชๆ‹œ

Channel

็บข้ฆ†๐—›๐—ข๐—ก๐—š๐—จ๐—”๐—ก๏ฝœ่ฟชๆ‹œ

@HONGUANdubai

On this record: Previous handles ยท Growth ยท Engagement ยท Posts ยท Citations ยท Cite this entry

1,316subscribers

-777 since we began measuring on 7 August 2026

Risers and fallers across the register ยท movement among entries of 1,000โ€“3,162.

Register entry

Telegram ID-1003325190818
TypeChannel
Username@HONGUANdubai
CreatedBetween 1 November 2025 and 31 March 2026 โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/HONGUANdubai

Previous handles

@HONGUANdubai was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today โ€” only that this channel no longer does.

@kuaihuolin667788
held 7 August 2026 โ€“ 7 August 2026

Growth

1,2512,0951,6737 August 2026 โ€” 2,093 subscribers7 August 2026 โ€” 2,093 subscribers8 August 2026 โ€” 2,095 subscribers11 August 2026 โ€” 2,093 subscribers15 August 2026 โ€” 1,600 subscribers17 August 2026 โ€” 1,348 subscribers20 August 2026 โ€” 1,251 subscribers24 August 2026 โ€” 1,257 subscribers28 August 2026 โ€” 1,267 subscribers28 August 2026 โ€” 1,267 subscribers29 August 2026 โ€” 1,272 subscribers1 September 2026 โ€” 1,293 subscribers4 September 2026 โ€” 1,300 subscribers10 September 2026 โ€” 1,316 subscribers1,3167 August 202610 September 2026
14 measurements spanning 33 days, net -777. 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 1,124โ€“2,222 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 05:191,316+16
4 Sept 2026, 15:581,300+7
1 Sept 2026, 04:131,293+21
29 Aug 2026, 12:251,272+5
28 Aug 2026, 13:451,267no change
28 Aug 2026, 13:301,267+10
24 Aug 2026, 00:451,257+6
20 Aug 2026, 12:231,251-97
17 Aug 2026, 21:521,348-252
15 Aug 2026, 01:381,600-493
11 Aug 2026, 19:222,093-2
8 Aug 2026, 12:372,095+2
7 Aug 2026, 20:322,093no change
7 Aug 2026, 19:182,093first reading

Engagement

10 posts held, back to 18 July 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 2 pages of Telegramโ€™s post history, 20 posts per page.

ERR ยท 30 days
81.1%
avg views รท 1,316 subscribers
Avg views / post
1,070
4 posts measured
Reaction rate
โ€”
this channel exposes no reaction counts
Posts in window
4
of 10 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.

What these figures were computed from
WindowRolling 30 days ยท latest post in window 26 August 2026
Posts held10 (18 July 2026 โ€“ 26 August 2026)
Views total4,270
Reactions totalโ€”
Forwards / commentsnot exposed by the public surface โ€” not measured, not estimated
Readings taken28 Aug 2026, 13:45 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.

Recent posts

26 Aug 2026, 13:02 UTCโ‰ˆ1,000 viewsread 28 August 2026
Photo

๐Ÿ”ฐ่ฅไธšไธญ๏ฝœ็บข้ฆ†๐—›๐—ข๐—ก๐—š๐—จ๐—”๐—ก ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ”ฐๆฌข่ฟŽๅ’จ่ฏข ๆฌข่ฟŽ้ข„็บฆ ๐Ÿ”ฐ่ฅไธšๆ—ถ้—ด17:00-05:00 ๐Ÿ”ฐๅค–้€๐Ÿ”ฐ่ฟ‡ๅคœ ๐Ÿ”ฐ่ฟ‡ๅคœ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ‘ ่”็ณปๅฎขๆœ @HONGUAN666

25 Aug 2026, 12:02 UTCโ‰ˆ1,130 viewsread 28 August 2026
Photo

๐Ÿ”ฐ ๅธŒๅธŒwell๏ฝœ๐Ÿ”ค็‰Œ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€ 02ๅนด 160 36B ็”œ็พŽ้’ๆ˜ฅๅฐๅฐค็‰ฉ ๐Ÿ˜€ A4่…ฐ๐Ÿฅข็ญทๅญ่…ฟ ็šฎ่‚คๅทจ็™ฝ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€ ๆŸฅ็œ‹็Žฏๅขƒ ๐Ÿ˜€ ๆŸฅ็œ‹ไปทๆ ผ ๐Ÿ˜€ ๐Ÿ‘ ่”็ณปๅฎขๆœ @HONGUAN666

25 Aug 2026, 11:14 UTCโ‰ˆ1,080 viewsread 28 August 2026
Photo

๐Ÿ”ฐ ๅฐ้นฟwell๏ฝœ๐Ÿ”ค็‰Œ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€ 01ๅนด 165 36E้›ช็™ฝ็บฏๅพก ๆดปๅฅฝไธ€ๆตไฝ“้ชŒ ๐Ÿ˜€ ๅทดๆŽŒ่…ฐ๐Ÿฅข็ญทๅญ่…ฟ ๅฐ็ฟ˜่‡€ๅพ…ๅฎขๅฆ‚ๅˆๆ‹่ˆฌ็ƒญๆƒ… ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€ ๆŸฅ็œ‹็Žฏๅขƒ ๐Ÿ˜€ ๆŸฅ็œ‹ไปทๆ ผ ๐Ÿ˜€ ๐Ÿ‘ ่”็ณปๅฎขๆœ @HONGUAN666

25 Aug 2026, 11:13 UTCโ‰ˆ1,060 viewsread 28 August 2026
Photo

๐Ÿ”ฐๅคš็ฑณwell ๏ฝœ๐Ÿ”ค็‰Œ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€ 99ๅนด 162 34B ็šฎ่‚ค็™ฝ็š™ ๐Ÿ˜€ ้ฃŽ้ชšๆ— ้™ ๅ…ญไน่›‡ๅป ๆธฉๆŸ”ๅ–„่งฃไบบๆ„ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€ ๆŸฅ็œ‹็Žฏๅขƒ ๐Ÿ˜€ ๆŸฅ็œ‹ไปทๆ ผ ๐Ÿ˜€ ๐Ÿ‘ ่”็ณปๅฎขๆœ @HONGUAN666

8 Aug 2026, 13:48 UTCโ‰ˆ4,160 viewsread 28 August 2026
Photo

๐Ÿ”ฐ ๅช›ๅช›well๏ฝœ๐Ÿ”ค็‰Œ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€07ๅนด /167cm/34C ๐Ÿ˜€ๅญฆ็”Ÿๅ…ผ่Œ ๅซฉ่Œๆ–ฐ็”Ÿไปฃ ๅŒๅ•†ๅœจ็บฟ ๐Ÿ˜€ๅคฉไฝฟ่„ธ่›‹ๆญ้…้ญ”้ฌผ่บซๆ ๐Ÿ˜€้ซ˜้…ๅˆๅบฆๅฎ่—ไฝ“่ดจ ๐Ÿ˜€ๅฐ‘ๅฅณๆ„Ÿๅคฉ่Šฑๆฟ ๅฏ้šๆ„้ชŒ่ฏ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€ ๆŸฅ็œ‹็Žฏๅขƒ ๐Ÿ˜€ ๆŸฅ็œ‹ไปทๆ ผ ๐Ÿ˜€ ๐Ÿ‘ ่”็ณปๅฎขๆœ @HONGUAN666

24 Jul 2026, 12:03 UTCโ‰ˆ7,240 viewsread 28 August 2026
Photo

๐Ÿ”ฐ ็”œ็”œwell๏ฝœ๐Ÿ”ค็‰Œ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€07ๅนด/167cm/34B+ ๐Ÿ˜€ๆš‘ๅ‡ๅทฅ ็œŸๆ–ฐไบบไธ‹้ข่ถ…็ดง ๅˆๆฌกไธ‹ๆตท ๐Ÿ˜€็šฎ่‚ค็™ฝ ไน–ๅทงๅฌ่ฏ ็‰น้•ฟไผšๅ“„ๅ“ฅๅ“ฅ ๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค—๐Ÿค— ๐Ÿ˜€ ๆŸฅ็œ‹็Žฏๅขƒ ๐Ÿ˜€ ๆŸฅ็œ‹ไปทๆ ผ ๐Ÿ˜€ ๐Ÿ‘ ่”็ณปๅฎขๆœ @HONGUAN666

24 Jul 2026, 11:09 UTCโ‰ˆ3,080 viewsread 7 August 2026
Photo

ๅฐๅฐwell๐Ÿ #๐Ÿ“ฑ็‰Œ ๐Ÿณ06ๅนด 166 34Bๆš‘ๅ‡ๅทฅ ็œŸๆ–ฐไบบไธ‹้ข่ถ…็ดง ๐Ÿ’—ๅˆๆฌกไธ‹ๆตท ็ป†้•ฟ่…ฟ ๅˆไน–ๅˆ็”œ ้…ๅˆๅบฆ้ซ˜ โšก๏ธ่ฏท่”็ณปๅฎขๆœ๏ผš๐Ÿ’๐Ÿป@kuaihuolin5566

22 Jul 2026, 07:38 UTCโ‰ˆ3,190 viewsread 7 August 2026
Photo

้œฒ้œฒwell๐Ÿ #๐Ÿ“ฑ็‰Œ ๐Ÿณ02ๅนด 168 34Dๆ•ๆ„Ÿไฝ“่ดจๅผ‚้ซ˜ๆฝฎ ็ดง่‡ดๆฐดๅคš ๐Ÿ’ฆ ๐Ÿ’—ๆธ…็บฏๅนฒๅ‡€ ๆดปๆณผๅผ€ๆœ— ๅˆๆ‹ๅฅณๅ‹ๆ„Ÿ ๆธฉๆŸ” ไธ”็ป†่…ป โšก๏ธ่ฏท่”็ณปๅฎขๆœ๏ผš๐Ÿ’๐Ÿป@kuaihuolin5566

18 Jul 2026, 07:38 UTCโ‰ˆ3,690 viewsread 7 August 2026
Photo

ๅ–ตๅ–ตwell๐Ÿ #๐Ÿ“ฑ็‰Œ ๐Ÿณ05ๅนด 161 34C ๆธ…็บฏๅฏ็ˆฑ ๅฆˆ็”Ÿ่„ธ ๐Ÿ’—็™ฝๅซฉ่ฏฑไบบ ็™ฝ้‡Œ้€็บขๅ…จ่บซ้›ช็™ฝ ็šฎ่‚ค็ป†่…ป โšก๏ธ่ฏท่”็ณปๅฎขๆœ๏ผš๐Ÿ’๐Ÿป@kuaihuolin5566

Showing the 10 most recent of 10 posts we hold for @HONGUANdubai. 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.

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.

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

โ€œ็บข้ฆ†๐—›๐—ข๐—ก๐—š๐—จ๐—”๐—ก๏ฝœ่ฟชๆ‹œโ€ (@HONGUANdubai), 1,316 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/HONGUANdubai.

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.