IG For Rex

Channel
𝙈𝙖𝙠𝙠𝙖𝙋𝙖𝙠𝙠𝙖’𝙨 𝘾𝙝𝙖𝙣𝙣𝙚𝙡
@MakkaPakkaOvO
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
7,724subscribers
+3,851 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003843509742 |
|---|---|
| Type | Channel |
| Username | @MakkaPakkaOvO |
| Description | 交流互助群:https://t.me/MakkaPakkaGroupO_O CF反代:https://github.com/MakkaPakka518/ProxyHub_Emby VPS反代:https://github.com/MakkaPakka518/EmbyProxy-VPS CF Lite简易反代:https://github.com/MakkaPakka518/EmbyProxyCF-Lite 模块合集:rex.778477.xyz 密码:public |
| Created | Between 1 February 2026 and 14 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/MakkaPakkaOvO |
Topic
Technology — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 08:59 | 7,724 | +73 |
| 12 Nov 2026, 02:40 | 7,651 | +63 |
| 8 Nov 2026, 10:16 | 7,588 | +58 |
| 5 Nov 2026, 00:20 | 7,530 | +26 |
| 2 Nov 2026, 00:28 | 7,504 | +44 |
| 30 Oct 2026, 02:09 | 7,460 | +54 |
| 26 Oct 2026, 17:28 | 7,406 | +2,640 |
| 23 Oct 2026, 17:15 | 4,766 | +30 |
| 21 Oct 2026, 03:06 | 4,736 | +43 |
| 17 Oct 2026, 22:57 | 4,693 | +84 |
| 14 Oct 2026, 22:46 | 4,609 | +78 |
| 12 Oct 2026, 01:39 | 4,531 | +221 |
| 5 Oct 2026, 01:41 | 4,310 | +200 |
| 25 Sept 2026, 20:41 | 4,110 | +37 |
| 17 Sept 2026, 13:39 | 4,073 | +73 |
| 13 Sept 2026, 16:15 | 4,000 | +31 |
| 9 Sept 2026, 16:18 | 3,969 | +17 |
| 4 Sept 2026, 09:37 | 3,952 | +17 |
| 1 Sept 2026, 01:04 | 3,935 | -4 |
| 29 Aug 2026, 02:04 | 3,939 | first reading |
Engagement
32 posts held, back to 14 April 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 31 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 43.5%
- avg views ÷ 7,724 subscribers
- Avg views / post
- 3,360
- 18 posts measured
- Reaction rate
- 0.07%
- reactions ÷ views · ER floor
- Posts in window
- 18
- of 32 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 14 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 32 (14 April 2026 – 16 November 2026) |
| Views total | 60,530 |
| Reactions total | 35 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 19:48 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
- 171
- Videos
- 13
- Links
- 67
Lifetime counters from Telegram’s own channel header, read 17 November 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
- 41s
- Average length
- 21s
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.
Reaction mix
125 reactions across 22 posts, in 4 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 75 | 60.0% | |
| 👍 | 35 | 28.0% | |
| 🥰 | 13 | 10.4% | |
| 👏 | 2 | 1.60% |
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 26 of the 32 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 125 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 14 April 2026 to 16 November 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
Telegram’s own ‘edited’ marker: 4 of 18 posts held from the last 30 days (22.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Douyin For Rex 正式启动
点我领取赛博鸡蛋 赛博鸡蛋兑换处 GPT-6.1 Sol,GPT-6 Astra模型 通过我的邀请链接进群领1000刀额度,邀请别人进群一个人1000刀 赛博鸡蛋又来了,你不来抢吗 领完点上面的兑换处去站点兑换额度 会无理由封号,别拉太多人
你发了一张咖啡的照片。 窗外的街景告诉我你在哪里,桌上的第二只杯子告诉我你不是一个人。几个小时后,你删掉了它。 你以为这样就结束了。 可我已经看见了。 VOYEUR 是一间只为Ta亮着的私人观察室。它会定时回到你的社交媒体,把账号原本能够看见的文字、照片、视频与页面截图一件件带回来。 你更新,它替我记住。 你删除,它替我保留。 你和新的人靠得更近,它也只是沉默地把那一刻放进档案。 支持监听Instagram、TikTok、抖音、Threads、X、微信朋友圈 开始视奸Ta吧🌚 开玩笑的
❤2
#模块更新 · 平台剧场新增巴哈姆特动画疯榜单 · 平台剧场新增各串流平台[真]Top10榜单,不再是TMDb模拟的[假]Top10 · 模块优化,简介和海报不再提前选择,统一走Rex官方widget.tmdb渠道按app设置内的语言获取元数据,不会再出现海报样式从我预设的海报被Rex获取到海报覆盖而闪烁的问题 Rex用户(确保你现在用的我上次发布的最新模块合集)刷新模块即可 未加密文件版本在评论区
❤9
4.1.2 新增反代自测功能 • 主线路与备用线路连通检测,emby API 路径自动识别 • 普通账号密码登录检测 • 媒体库读取与 PlaybackInfo 检测 • DirectPlay、DirectStream、转码能力判断 • Range 206 与拖动进度检测 • CF 反代与源站一致性检查 • 一键生成脱敏诊断报告
❤3👍1
4.1.1 更新了 仓库有明文
EmbyProxy-VPS 更新汇总 • 修复播放器退出后仍持续拉流、偷跑流量的问题。 • 新增背压控制,避免内存堆积。 • 换用深绿青柠主题,支持深浅模式。 • 新增版本显示、自动检查及面板一键更新,支持备份与失败回滚。 • 前后端分离配置(多数情况可不配置)移至功能最底部,支持折叠,默认收起。 • 媒体默认经 VPS 代理中转,可按节点切换直连。 • 修复媒体 302 循环、404、响应头冲突及签名路径问题。 • 媒体源缓存按节点隔离,防止向第三方媒体站泄漏账号凭据。 • 新增下游长时间停滞保护。
❤2
https://agentrouter.org/register?aff=6x0a 有老github号或者L站的可以来薅一下这个公益api 有GPT5.6,6,6.1 这几天试了一下很爽。注册送100刀,点我链接注册你可以额外获得50刀,我可以得100刀🌚没薅的可以薅一下,顺便让我吃口AFF 每天退出重登可以获得25刀有时候会获得200刀 Safari浏览器不行,推荐用谷歌浏览器
❤3
https://raw.githubusercontent.com/MakkaPakka518/Rex_Widget/refs/heads/main/dy.js
Rex看抖音AI短剧有没有搞头
TikTok For Rex
❤1
Showing the 12 most recent of 32 posts we hold for @MakkaPakkaOvO. 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.
Posts edited after publishing
@MakkaPakkaOvO edited 2 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.
- First edit seen
- 13 November 2026
- Most recent edit
- 16 November 2026
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
Named by 3 registered channels — 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“𝙈𝙖𝙠𝙠𝙖𝙋𝙖𝙠𝙠𝙖’𝙨 𝘾𝙝𝙖𝙣𝙣𝙚𝙡” (@MakkaPakkaOvO), 7,724 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/MakkaPakkaOvO.
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.