ccmax 改0.7x了
❤1👍1

Channel
@kedaya_888
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,352subscribers
+523 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002325992178 |
|---|---|
| Type | Channel |
| Username | @kedaya_888 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/kedaya_888 |
Crypto & trading — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 |
|---|---|---|
| 15 Sept 2026, 03:00 | 6,352 | +60 |
| 11 Sept 2026, 05:01 | 6,292 | +64 |
| 6 Sept 2026, 07:59 | 6,228 | +65 |
| 2 Sept 2026, 09:48 | 6,163 | +17 |
| 30 Aug 2026, 20:08 | 6,146 | +19 |
| 27 Aug 2026, 20:53 | 6,127 | +80 |
| 24 Aug 2026, 10:11 | 6,047 | +72 |
| 20 Aug 2026, 15:11 | 5,975 | +46 |
| 17 Aug 2026, 15:46 | 5,929 | +25 |
| 14 Aug 2026, 15:07 | 5,904 | +42 |
| 11 Aug 2026, 05:55 | 5,862 | +33 |
| 8 Aug 2026, 01:52 | 5,829 | no change |
| 7 Aug 2026, 22:31 | 5,829 | first reading |
21 posts held, back to 24 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 7 pages 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 21 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
204 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 102 | 50.0% | |
| 😁 | 35 | 17.2% | |
| ❤ | 23 | 11.3% | |
| 😭 | 17 | 8.33% | |
| 🥰 | 10 | 4.90% | |
| 👎 | 8 | 3.92% | |
| 😱 | 4 | 1.96% | |
| 🔥 | 3 | 1.47% | |
| 🐳 | 1 | 0.49% | |
| 👍 | 1 | 0.49% |
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 19 of the 21 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 204 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 24 July 2026 to 10 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.
ccmax 改0.7x了
❤1👍1
kiro 0.06x了 ccmax接了个上游 给我10w余额 快帮我跑空他 ccmax两个分组都是同一个上游了 晚点下掉那个 自行检测1
😁2
下掉luna模型了 跑了一天400多亿的token就200多块钱 成本都180块钱了 一天赚20
😁21🤡17❤3🥰1
稳定分组0.08那个 除了gpt-5.6-sol和gpt-5.5 偶尔打到bugteam和plus池 其他的模型都是打到pro池
❤1
恢复了 妈的 又是半天没有扣余额 欠费的可以还一下吗 倒闭了
🤡20
先关一下站 傻逼技术 一个小时了还没修好不扣余额的bug
😁6🐳1🤡1
一直在群里私信打广告那个金苹果是骗子 别信啊
😁3❤1
还钱!!!
🤡35😭9❤1
求求你们了 不然我真倒闭了
🤡29😭4😱1
恢复了 批量补扣了 可以还我钱吗
😭4❤1
今天一天用户余额使用都没扣钱 我受不了了 先关站了
❤5
服务器爆炸了 新买的服务器硬件有问题 发工单给ovh那边两天没回复 IP直连目前已无法使用 请先使用域名
🥰9
Showing the 12 most recent of 21 posts we hold for @kedaya_888. 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“大菲猪后援会” (@kedaya_888), 6,352 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/kedaya_888.
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.