Channel
@tghjsq
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4,416subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002128293559 |
|---|---|
| Type | Channel |
| Usernames | @hjsqzy @tghjsq |
| Created | 20 January 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/tghjsq |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 14:57 | 4,416 | -4 |
| 10 Aug 2026, 21:56 | 4,420 | no change |
| 8 Aug 2026, 06:35 | 4,420 | -2 |
| 7 Aug 2026, 18:15 | 4,422 | -1 |
| 7 Aug 2026, 12:48 | 4,423 | no change |
| 7 Aug 2026, 12:48 | 4,423 | no change |
| 7 Aug 2026, 12:38 | 4,423 | first reading |
10 posts held, back to 20 January 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 6 pagesof 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 10 posts for this entry, the most recent from 22 April 2024. An engagement rate over an empty window would be a number about nothing.
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.
449 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 46.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 209 | 46.5% | |
| 👍 | 174 | 38.8% | |
| 👎 | 21 | 4.68% | |
| 😁 | 16 | 3.56% | |
| 👏 | 6 | 1.34% | |
| 💩 | 6 | 1.34% | |
| 🤮 | 4 | 0.891% | |
| 🥰 | 4 | 0.891% | |
| 🔥 | 3 | 0.668% | |
| 😢 | 3 | 0.668% | |
| 🤡 | 3 | 0.668% |
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 9 of the 10 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 449reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 20 January 2024 to 22 April 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.
😅 海角图文更新： @HJSQTV @TGhaijiao @simishe @haijiaoSQ @haijiaoshequ9 🔄 海角防丢中转频道 @HJSQSP @HJSQZZ @haijiaoai @haijiaoNB @HJSQZY @haijiaocctv @haijiaoshequ2 ⚠️ 仿冒群泛滥，请勿轻信低价！ 👉点击验证一下是否在会员群 海角交流群长期潜伏着一批克隆仿冒群的群主去主动私聊群员，介绍推销他们的便宜克隆群，请大家擦亮眼睛，认准我们置顶的会员群入群通道 🔘 自助下单加群（支付宝&微信）： @haijiaosvips_bot 🔘 人工下单入群（只支持USDT）： @haijiaokefu 海角会员群已收录600余位作者视频 💬 海角社区群组(group) 🌸 南加社区导航(channel)
❤77👍50👎10😁6🥰4👏3🔥1
海角社区SVIP💎独享定制群组： 1️⃣ 加群门槛：260 限时优惠中 2️⃣ 支付方式： 🔘 自助下单加群（支付宝&微信）： @haijiaosvips_bot 🔘 人工下单入群（只支持USDT）： @haijiaokefu ⚠️ 仿冒群泛滥，请勿轻信低价！ 🆔 海角客服 认准ID：@haijiaokefu 🤖 双向私聊机器人： @TGhjsq_Bot ⚠️本频道为免费公开预览频道‼️免费‼️免费‼️ 👉点击验证一下是否在会员群 海角交流群长期潜伏着一批克隆仿冒群的群主去主动私聊群员，介绍推销他们的便宜克隆群，请大家擦亮眼睛，认准我们置顶的会员群入群通道 本频道 只有 海角💎SVIP群，克隆仿冒我们的群太多，请认准上面的加群方式，无其他加群通道，谨防上当 ⚠️主动私聊你的都是骗子⚠️ 3️⃣ 特权功能： • 享极速更新，海角官网热帖 • 可求任意片，看片不再限制 • 精品乱伦片，父女萝莉母子 • 可看…
❤30👍19🤮4😁3
解除私聊限制 第一步：搜索 @spambot 第二步：点击 Start 第三步：点击 But I can't message non-contacts! 第四步：点击 No,I'll never do any of this! 第五步：回复 accident Dear Telegram Support, I believe my account was restricted by mistake. I strictly follow the rules and only chat with real people. Please review my account. Thank you! #教程 #私聊限制 #双向 #双向私聊限制
❤12👍9💩4
【 Telegram 注册 登录 养号 】 注册telegram账号需要手机号，有些人一般拿中国的+86手机号注册，有些人说这样不安全，但其实也还行，这点不重要。重要的是，他们在使用或登录时，遇到一些难缠的问题。 —————————— 一、养号 首先，我们如果正常注册好了一个telegram账号后，需要“养号”！不然很容易被封禁。 至于“养号”，那就是: 不要随便私聊别人（容易被举报）； 不要发违规视频和图片； 梯子节点别乱换； 短时间内别加太多群； 别长时间不登录； 尽量把自己的账号在多个设备登录着； 等等...... 比如你在官方Telegram登录算一个设备； 在Telegram X，这个官方 Telegram 测试版的APP中登录也算一个设备； 在电脑64gram上登录，也算一个设备； 总之，最好把自己的号同时登录着多个常用的设备为上策！ 因为你如果只在一个设备登录着的话，万一你的号某天掉了，或者你换新…
❤8👍6💩2
😇 海角官网 海外永久网址(翻墙): www.haijiao.com 今日大陆域名为: h2507ja8782.top 海角App 官网发布地址 https://h2j5j76b0a.top/post/details?pid=981686 https://www.haijiao.com/download ✅ 海角 安卓 app 2.3.5 https://h2j5j76b0a.top/appdown/hjappv2.3.5.apk ✅ 海角 安卓 app 2.3.6 https://www.haijiao.com/appdown/hjappv2.3.6.apk ✅ 海角 安卓 app 2.5.0 https://dl.6ab5152bd62955b0.xyz/appdown/hjappv2.5.0.apk 🍎 海角 苹果 轻量版 app 1.0.0 https://iosori.cldca9.top…
👍14❤11👎4🤡3😁1
⚠️ 𝐓𝐆 冻结帐号申诉方法 第一步：点击 ：@spambot 第二步：点击：This is a mistake 第三步：点击：Yes 第四步：回复：（点击可以复制） My account is running well, I don't understand what I did to violate the rules. I subscribed to 1 Premium this morning, but my account was frozen as soon as the membership arrived. I don't understand why, please help me unfreeze it. My account is very important to me. Thank you 第五步：回复：飞机昵称 或 号码 第六步：回复：输入能接码的邮箱（不一定需要接码） 第七步： 问你注册时…
👍6❤2👎1👏1
😂 海角图文更新： @TGhaijiao @simishe @haijiaoshequ_456 🔘 海角客服🆔： @dahufa @haijiaokefu 🔘 双向私聊机器人🤖： @TGhjsq_Bot 🔘 🇨🇳 中文语言包 👇 https://t.me/setlanguage/zhcncc »点击上方链接切换中文语言界面« 🇨🇳 #中文包 #中文 #汉化 #聪聪中文语言包 #海角社区 #电报用户名地址
👍6❤4👎3🔥2
南加社区 频道发布 🆔 @southplus https://t.me/SouthPlus #防失联
👍4❤3👎2😁1
😂 解除苹果ios用户，被限制查看色情频道方法 Telegram 如果你进入某个群或频道遇到如下提示： This channel can't displayed because it was used to spread pornographic content. 原因： 有人在群/频道里发了色情内容, 被 Telegram 官方限制了; ✅解决办法： 登录Telegram Web网页版链接： https://web.telegram.org （复制到浏览器打开） ⚡️操作： 登录网页版后 ➊点击「Settings/设置」 ➋点击「Privacy and Security/隐私和安全」 ➌找到「Sensitive content/敏感内容」并勾选「Disable filtering/禁用过滤」 ➍ 重启 iOS 客户端即可正常访问 #教程 #TG小妙招 #苹果 #ios #色情限制
❤62👍60😁5😢3👏2👎1
Channel created
Showing the 10 most recent of 10 posts we hold for @tghjsq. 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 — 989,115 of 1,151,006entries 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.
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.
@tghjsq named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“海角社区 SVIP加群 海角乱伦大神” (@tghjsq), 4,416 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/tghjsq.
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.