小青柠追踪自即日起停更 感谢所有用户一路以来的陪伴 卡密验证及店铺已关闭 网络不是法外之地,请于24小时之内删除有关小青柠的所有应用,使用即代表同意《操作免责协议》 大家有缘再见,希望下个赛季我还会站在国体的这个地方
👍34🖕25😭14🤬5👎3
Signed 若楠

Channel
@RNHOOK6
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
13,491subscribers
+5,106 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002209947859 |
|---|---|
| Type | Channel |
| Username | @RNHOOK6 |
| Description | عزيزي فريق الدعم Telegram ، مرحبا ! أنا مشغل هذاtelegram@rnhook6 مع معرف القناة @ rnhook6 . . . . . . . نحن هنا نعلمك عن الامتثال لهذه القناة : منذ إنشائها ، هذه القناة تلتزم بدقة " تلغرام شروط الخدمة " والسياسات |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/RNHOOK6 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 13:17 | 13,491 | -8 |
| 31 Aug 2026, 12:45 | 13,499 | +6 |
| 30 Aug 2026, 16:05 | 13,493 | +77 |
| 29 Aug 2026, 16:33 | 13,416 | +55 |
| 28 Aug 2026, 16:57 | 13,361 | +36 |
| 27 Aug 2026, 13:57 | 13,325 | +36 |
| 26 Aug 2026, 11:14 | 13,289 | +90 |
| 25 Aug 2026, 09:22 | 13,199 | +269 |
| 24 Aug 2026, 07:23 | 12,930 | +311 |
| 22 Aug 2026, 13:05 | 12,619 | +292 |
| 21 Aug 2026, 03:19 | 12,327 | +303 |
| 20 Aug 2026, 05:11 | 12,024 | +415 |
| 19 Aug 2026, 03:03 | 11,609 | +2,517 |
| 16 Aug 2026, 04:36 | 9,092 | +680 |
| 12 Aug 2026, 16:14 | 8,412 | +25 |
| 9 Aug 2026, 07:51 | 8,387 | +2 |
| 8 Aug 2026, 11:02 | 8,385 | first reading |
328 posts held, back to 31 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 41 pages of Telegram’s post history, 20 posts per page.
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 304 of 315 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 328 (31 July 2026 – 31 August 2026) |
| Views total | 447,309 |
| Reactions total | 7,483 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 15:26 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.
Lifetime counters from Telegram’s own channel header, read 1 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.
Measured directly from 32 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.
7,508 reactions across 309 posts, in 23 distinct kinds. The most used accounts for 83.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6,235 | 83.0% | |
| ❤ | 319 | 4.25% | |
| 🖕 | 162 | 2.16% | |
| 😍 | 93 | 1.24% | |
| 🔥 | 83 | 1.11% | |
| 🍌 | 74 | 0.986% | |
| 🤯 | 68 | 0.906% | |
| 🤬 | 65 | 0.866% | |
| 👎 | 56 | 0.746% | |
| 😡 | 54 | 0.719% | |
| 🤓 | 52 | 0.693% | |
| 🤪 | 39 | 0.519% | |
| 🥰 | 36 | 0.479% | |
| 🤔 | 35 | 0.466% | |
| 😁 | 28 | 0.373% | |
| 😨 | 21 | 0.28% | |
| 👏 | 19 | 0.253% | |
| 😭 | 19 | 0.253% | |
| 😘 | 15 | 0.2% | |
| 🤩 | 14 | 0.186% | |
| 3 further kinds | 21 | 0.28% |
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 309 of the 328 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 7,508 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 328 most recent posts we hold, published 31 July 2026 to 31 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.
小青柠追踪自即日起停更 感谢所有用户一路以来的陪伴 卡密验证及店铺已关闭 网络不是法外之地,请于24小时之内删除有关小青柠的所有应用,使用即代表同意《操作免责协议》 大家有缘再见,希望下个赛季我还会站在国体的这个地方
👍34🖕25😭14🤬5👎3
Signed 若楠
再见了
👍29😡9❤3🎉3🖕2
Signed 冰释 @qer88_bot
好奇怪,我为什么不卡伤1分25秒清图
👍34❤2
Signed 冰释 @qer88_bot
踏空的真正使用教程发现有些人不会用😂
👍31❤2👎2😍2
Signed 冰释 @qer88_bot
Video, posted without a caption
👍23😍3👎2
Signed 冰释 @qer88_bot
小学生都没钱买卡密?😂 📱📱抖音代发视频👏👏 🟢帮忙发视频素材,嘎嘎赚钱🟢发了就有80 📱📱一个视频 📱📱视频以上📱📱 📱📱视频以上📱📱📱 📱做单认准:@qizhawwg 双向群评论区艾特我,我私你 ⚠️⚠️⚠️一次诚信合作终身帮发
👍24❤1
さようなら
👍32
Signed 冰释 @qer88_bot
网络不是法外之地,再见了兄弟们 已经到公安局写保证书了
👍48❤1🔥1
Signed 若楠
直播找我领卡,现在全体卡密加卡一天 @ScriptXY
👍35
Signed 若楠
小青柠追踪 pinned a file
小青柠3.3.zip ❗️❗️❗️❗️❗️ 🌟🌟🌟🌟 🪽4.6.4🪽 收费 反馈 @ScriptXY 😂😂😂😂😂😂😂 ⚠️此版本中更新了准度 购买 https://new.818fka.com/shop/1A3LP0TA/gi1evh
👍25❤5👎1🥰1
Photo, posted without a caption
👍32❤2🤓2
Showing the 12 most recent of 328 posts we hold for @RNHOOK6. 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.
@RNHOOK6 edited 4 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.
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
需不需要更新
Shares as published. No per-option vote count is published by Telegram, so none is shown.
原版简洁的UI好还是经过美化的UI好
Shares as published. No per-option vote count is published by Telegram, so none is shown.
对于下版本收费问题投票采集 Pro版享有更强大的追踪算法,更多娱乐功能 Pro和普通版本飞天踏空保持不变 (快饿死了无奈出此下策,支持一下吧)
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 328 most recent posts we hold, published 31 July 2026 to 31 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 440,534 of 1,629,362 entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“小青柠追踪” (@RNHOOK6), 13,491 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/RNHOOK6.
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.