Telegram RegisterThe public register of Telegram
Telegram profile photo for 小狠的朋友圈

Channel

小狠的朋友圈

@hjygz1

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

31subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002121498978
TypeChannel
Username@hjygz1
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live31 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 31 August 2026
On Telegramt.me/hjygz1

Growth

313231.57 August 2026 — 32 subscribers11 August 2026 — 32 subscribers24 August 2026 — 31 subscribers7 August 202624 August 2026
3 measurements spanning 17 days, net -1. 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 31–32 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 08:1431-1
11 Aug 2026, 02:0232no change
7 Aug 2026, 13:0232first reading

Engagement

15 posts held, back to 10 July 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 15 posts for this entry, the most recent from 28 July 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.0%

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

Measured over the 15 most recent posts we hold, published 10 July 2024 to 28 July 2024, 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

28 Jul 2024, 09:38 UTC112 viewsread 11 August 2026

全网招qq号商 待遇直接拉满🔤🔤🔤 有多少号吃多少号🔤🔤🔤 尽量避免挤号改密码删设备的问题🔤🔤🔤 认准唯一id:@hjygz⚡️ 谨防被骗 或认准id谨防:@jinfang😀

21 Jul 2024, 14:23 UTC187 viewsread 11 August 2026
Photo

7.21清账 夜深了~大家早点休息,各位中介还是号主都要注意身体健康不能熬夜 明天早起继续奋斗💪 (欢迎各地号商来谈合作) 灰姑娘上压公群:@hjygz3

19 Jul 2024, 14:07 UTC151 viewsread 11 August 2026
Photo

7.19清账 夜深了~大家早点休息,各位中介还是号主都要注意身体健康不能熬夜 明天早起继续奋斗💪 (欢迎各地号商来谈合作) 灰姑娘上压公群:@hjygz3

18 Jul 2024, 13:43 UTC126 viewsread 11 August 2026
Photo

7.18清账 夜深了~大家早点休息,各位中介还是号主都要注意身体健康不能熬夜 明天早起继续奋斗💪 (欢迎各地号商来谈合作) 灰姑娘上压公群:@hjygz3

17 Jul 2024, 13:44 UTC113 viewsread 11 August 2026
Photo

7.17清账 夜深了~大家早点休息,各位中介还是号主都要注意身体健康不能熬夜 明天早起继续奋斗💪 (欢迎各地号商来谈合作) 灰姑娘上压公群:@hjygz3

16 Jul 2024, 13:50 UTC113 viewsread 11 August 2026
Photo

7.16清账 夜深了~大家早点休息,各位中介还是号主都要注意身体健康不能熬夜 明天早起继续奋斗💪 (欢迎各地号商来谈合作) 灰姑娘上压公群:@hjygz3

15 Jul 2024, 15:15 UTC117 viewsread 11 August 2026
Photo

7.15清账 夜深了~大家早点休息,各位中介还是号主都要注意身体健康不能熬夜 明天早起继续奋斗💪 (欢迎各地号商来谈合作) 灰姑娘上压公群:@hjygz3

14 Jul 2024, 15:39 UTC124 viewsread 11 August 2026

来qq接码号商 qq私人号买断 有需要的联系我 @jinfang

13 Jul 2024, 16:45 UTC136 viewsread 11 August 2026

全网招qq号商 价格待遇直接拉满🔤🔤🔤 有多少号吃多少号🔤🔤🔤 尽量避免挤号改密码删设备的问题🔤🔤🔤 认准唯一id:@hjygz⚡️ 谨防被骗 或认准id谨防:@jinfang😀

13 Jul 2024, 16:05 UTC139 views1 reactionsread 11 August 2026
Photo

7.13清账 夜深了~大家早点休息,各位中介还是号主都要注意身体健康不能熬夜 明天早起继续奋斗💪 (欢迎各地号商来谈合作) 灰姑娘上压公群:@hjygz3

👍1

12 Jul 2024, 19:52 UTCviews —

小狠的朋友圈 pinned «最近出现很多仿冒我 需要你们付钱的 这些一律不要相信 我不会主动私信你们 让你们付钱或者代付的 主动私信你们付钱 或代付的都是骗子😀 认准唯一id:@hjygz 谨防被骗 或认准id谨防:@jinfang»

12 Jul 2024, 19:40 UTC147 viewsread 11 August 2026

最近出现很多仿冒我 需要你们付钱的 这些一律不要相信 我不会主动私信你们 让你们付钱或者代付的 主动私信你们付钱 或代付的都是骗子😀 认准唯一id:@hjygz 谨防被骗 或认准id谨防:@jinfang

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

“小狠的朋友圈” (@hjygz1), 31 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/hjygz1.

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.