gemini pro 18个月 5.8r yotube 3个月会员成品号 云猫卡网:https://catfk.com/shop/mrnf1999 tg号,推特,苹果id: tg.mrnf.de tg会员 @tg_mrnf : 3个月90,6个月120,一年210
custom 53349540571927193311

Channel
@Group_res_share
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,254subscribers
+1,003 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1004304992003 |
|---|---|
| Type | Channel |
| Username | @Group_res_share |
| Created | Between 1 June 2026 and 30 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/Group_res_share |
Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 34% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 19:16 | 4,254 | +132 |
| 13 Sept 2026, 01:59 | 4,122 | +64 |
| 8 Sept 2026, 19:01 | 4,058 | +229 |
| 3 Sept 2026, 14:37 | 3,829 | +106 |
| 31 Aug 2026, 02:57 | 3,723 | +94 |
| 27 Aug 2026, 16:24 | 3,629 | +28 |
| 24 Aug 2026, 22:37 | 3,601 | +49 |
| 21 Aug 2026, 03:12 | 3,552 | +49 |
| 17 Aug 2026, 19:54 | 3,503 | +57 |
| 15 Aug 2026, 00:25 | 3,446 | +105 |
| 11 Aug 2026, 05:27 | 3,341 | +88 |
| 8 Aug 2026, 01:10 | 3,253 | +2 |
| 7 Aug 2026, 20:01 | 3,251 | no change |
| 7 Aug 2026, 19:42 | 3,251 | first reading |
20 posts held, back to 30 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 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
42 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 57.1% | |
| custom 5420141555233071341 | 8 | 19.0% | |
| 🤡 | 5 | 11.9% | |
| custom 5334954057192719331 | 2 | 4.76% | |
| 👍 | 2 | 4.76% | |
| 🤔 | 1 | 2.38% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 13 of the 20 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 July 2026 to 7 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.
gemini pro 18个月 5.8r yotube 3个月会员成品号 云猫卡网:https://catfk.com/shop/mrnf1999 tg号,推特,苹果id: tg.mrnf.de tg会员 @tg_mrnf : 3个月90,6个月120,一年210
custom 53349540571927193311
芭比Q了,发广告的注意点吧,半年会员+一大堆礼物老杜照样乱杀
🤡5❤2🤔1
峰哥ai交流群 人不多,环境一般吧 软广好像可以发 https://t.me/xenterai #信息
❤3
JZ的GPT代充交流群[禁广] 没什么广告,环境还不错的交流群,不让发广 https://t.me/Ai66888i #信息 #上下游
❤1
gemini pro 18个月链接 5.5r https://catfk.com/item/78kdi3
这个交流群软广很多,禁止发链接环境一般 #广告 #信息
这个群环境不错,没什么广告 基本都是交流为主,禁广的 https://t.me/AisouPro #信息 #上下游
❤3
这个群人挺多但是活人比感觉有点低,禁广的,感觉信息也不算多(不嫌弃的看看,也说不好万一能找到点有用的信息也说不定) https://t.me/duoqudaochengpin #信息
❤1
以前那个半叶酥的群 现在也是广告群了挺乱的 https://t.me/bysjlq #广告
API Models Group|中转群 新开的中转,价格挺便宜的(有感兴趣的可以看看) 新群人不多,不过也不让发广告 https://t.me/api_models_group
❤2👍2
这个群信息挺多的 群里有kakaopay提链(群主搞的),老外挺多的,信息比较全 https://t.me/fuck_open #信息 #上下游
贝贝商店交流群 这个交流群禁广的,群主是搞代充的(gpt claude grok gemini都有),价格还算便宜,我感觉挺靠谱(现在圈子里骗子多找个靠谱的真不算容易) 还在运营推特什么的也是玩web3混币圈的 他的推特https://x.com/sankenainai https://t.me/beibeishoo #信息 #群主安全 #上下游
❤4custom 53349540571927193311
Showing the 12 most recent of 20 posts we hold for @Group_res_share. 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.
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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“群聊资源总结” (@Group_res_share), 4,254 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Group_res_share.
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.