Telegram RegisterThe public register of Telegram
Telegram profile photo for ❤️‍🔥惠州公开榜单❤️‍🔥

Channel

❤️‍🔥惠州公开榜单❤️‍🔥

@jkjkz257

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

19,968subscribers

+137 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002370602738
TypeChannel
Username@jkjkz257
Description交流群:https://t.me/tontok235 联系群主: @ABCmrdbot
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 live18 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/jkjkz257

Growth

19,83119,97219,901.57 August 2026 — 19,831 subscribers7 August 2026 — 19,831 subscribers8 August 2026 — 19,838 subscribers9 August 2026 — 19,841 subscribers10 August 2026 — 19,852 subscribers11 August 2026 — 19,877 subscribers12 August 2026 — 19,882 subscribers14 August 2026 — 19,902 subscribers15 August 2026 — 19,938 subscribers17 August 2026 — 19,972 subscribers18 August 2026 — 19,968 subscribers19,9687 August 202618 August 2026
11 measurements spanning 11 days, net +137. 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 19,810–19,993 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 08:4819,968-4
17 Aug 2026, 10:5319,972+34
15 Aug 2026, 19:4519,938+36
14 Aug 2026, 08:0719,902+20
12 Aug 2026, 06:2319,882+5
11 Aug 2026, 08:2619,877+25
10 Aug 2026, 07:4019,852+11
9 Aug 2026, 08:2119,841+3
8 Aug 2026, 05:4119,838+7
7 Aug 2026, 16:1519,831no change
7 Aug 2026, 16:0419,831first reading

Engagement

74 posts held, back to 7 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 27 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
3.55%
avg views ÷ 19,968 subscribers
Avg views / post
709
74 posts measured
Reaction rate
0.19%
reactions ÷ views · ER floor
Posts in window
74
of 74 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 40 of 74 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 August 2026
Posts held74 (7 August 202618 August 2026)
Views total52,430
Reactions total57
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 16:04 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
729
Videos
219
Links
222

Lifetime counters from Telegram’s own channel header, read 18 August 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
9m 39s
Average length
12s

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

57 reactions across 30 posts, in 5 distinct kinds. The most used accounts for 68.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3968.4%
👎610.5%
💩610.5%
🤮58.77%
😁11.75%

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

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

18 Aug 2026, 13:07 UTC246 views0 reactionsread 18 August 2026
Photo

花名:#Jennie 坐标:#江北 车费:#5p/10pp 服务内容:鸳鸯浴,猫式吹箫,花式调情,丝袜,性感情趣衣,高跟,活泼,有高档课室🏠 标签:#调情 私聊:@jinnie921 频道:https://t.me/jinnie778899

18 Aug 2026, 13:00 UTC450 views0 reactionsread 18 August 2026
Photo

花名:#萧萧 坐标:#江北 车费:#7p/13pp 服务内容:柔式,莞式蒙眼阴毛扫全身,🙈🙈服务内容:帝王享受 花式口爆 高山流水 69品鲍👅真毒龙 漫游 😍冰🔥横着口竖着口 指划 胸推 丝袜 服务严格把控 标签:#69 #毒龙 #口爆 私聊:@asd88673 频道:https://t.me/df1988124

18 Aug 2026, 07:45 UTC701 views3 reactionsread 18 August 2026
Photo

花名:#小狸 坐标:#河南岸 车费:#4p/8pp 服务内容:鸳鸯浴 无套口 调情 激情爱爱 标签:#嫩妹 #洗吹做 私聊:@bxjdbdjduud 频道:https://t.me/xmudbd

3

18 Aug 2026, 06:33 UTC884 viewsread 18 August 2026
Photo

花名:#百合 坐标:#河南岸 车费:#8p/15pp 服务内容:无套吹潇、无套口爆、深喉、舌吻(口臭不舌)、69互动、舔蛋蛋、亲咪咪、胸推、毒龙、指滑、黑丝高跟、性感情趣等,制服多多,三点敏感,姿势配合 加尚项目:拍照(不露脸)加200,颜射加200 标签:#舌吻 #69 #毒龙 #深喉 私聊:@Bai_he888 双向:@BaiHe_8888bot 频道:https://t.me/Dgjygl

17 Aug 2026, 13:17 UTC≈1,350 views3 reactionsread 18 August 2026
Photo

花名:#乔菲护士 坐标:#河南岸 车费:#7p/13pp 服务内容:鸳鸯浴,水中萧,舔眯眯,舔蛋蛋,十指调情,深喉口,无套吹,kis,69,爱爱姿势都会配合满足。情趣丝袜可选🉑甜🉑浴。 标签:#kiss #水中箫 联系:@qiaofei158 双向:@qiaoyi158bot 频道:https://t.me/qiaoyi18520

3

17 Aug 2026, 11:41 UTC900 viewsread 18 August 2026
Photo

花名:#甄妮妮 坐标:#惠城 车费:#7p/13pp 服务内容:鸳鸯浴无套吹丝袜制服搓背69舔 标签:#六九 #制服 #御姐 私聊:@TTN1N1 双向:@N1N1666_bot 频道:https://t.me/N1N1666

17 Aug 2026, 08:21 UTC≈1,010 views1 reactionsread 18 August 2026
Photo

花名:#纹纹 坐标:#江北 车费:#6p/12pp 服务内容:陪浴 指滑调情 无套口 亲咪咪 丝袜制服诱惑。各种姿势配合 标签:#调情 #制服 私聊:@wenwen1681 频道:https://t.me/wenwen8975

1

17 Aug 2026, 08:00 UTC816 viewsread 18 August 2026
Photo

花名:#泰国诗琳 坐标:#港惠 #惠城 车费:#全套650 #95口爆450 #98快餐450 服务内容:舌吻 鸳鸯浴 精油按摩 无套吹 舔蛋 亲嘴 乳交 可舔B 情趣内衣 丝袜诱惑 可配合多种姿势 标签: #肛交 #口爆 #颜射 #泰国 私聊:@MGYH02 双向:@MGYH02bot 频道:https://t.me/YDXL888

17 Aug 2026, 07:50 UTC956 viewsread 18 August 2026
Photo

花名:#研可 坐标:#龙丰 车费:#600p 1200pp 服务内容:69 無套深喉 老汉推车 鸳鸯浴 水中潇 观音坐莲🤩激情爱爱 舔吸🉑kiss 排课轻松不催钟 可配合任意姿势。 标签:#六九 #深喉 #嫩妹 私聊:@huichengyanke2233 频道:https://t.me/huichengyanke223

16 Aug 2026, 15:01 UTC477 views2 reactionsread 16 August 2026
Photo

花名:#媛媛 坐标:#麦地 车费:#7p/13pp 服务内容:鸳鸯浴,水中萧 过水 漫游各种情趣丝袜 🐍吻 毒龙 69,口爆, 臀推 双飞 💋💋💋服务不满意包退 标签:#舌吻 #69 #口爆 #毒龙 私聊:@yuanyuan996324 频道:https://t.me/yuanyuan996532

2

16 Aug 2026, 10:11 UTC800 views2 reactionsread 16 August 2026
Photo

花名:#糖小北 坐标:#江北 车费:#600p 1200pp 服务内容:鸳鸯戏水,水中萧,胸推,指划,鼻吸。舌漫,可舌吻。口挑逗你的小弟弟,胸部舌尖漫游,亲小奶头,舔蛋,情趣丝袜,制服高跟诱惑 ,不事不催。 标签:#舌吻 #舌漫 #舔蛋 私聊:@qiqi999995 频道:https://t.me/xiaoqi999995

2

16 Aug 2026, 09:07 UTC831 views1 reactionsread 16 August 2026
Photo

花名:#御姐 坐标:#江北 车费:#700 #1300 服务内容:看课表有的都有 标签:#水床 #莞试 私聊: @Q88ww33 频道: https://t.me/Q888ww33

1

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

Citation-graph rank

Citation-graph rank — 226,195 of 1,549,704entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“❤️‍🔥惠州公开榜单❤️‍🔥” (@jkjkz257), 19,968 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/jkjkz257.

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.