Telegram RegisterThe public register of Telegram
Telegram profile photo for 卡接回U模式跑分、免押跑分、寻找个人车队合作

Channel

卡接回U模式跑分、免押跑分、寻找个人车队合作

@kaishou778

On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

11subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001772232130
TypeChannel
Username@kaishou778
Created29 March 2022 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live9 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 9 October 2026
On Telegramt.me/kaishou778

Topic

Gambling & betting — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 48% 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.

Growth

111211.57 August 2026 — 12 subscribers12 August 2026 — 12 subscribers15 September 2026 — 11 subscribers7 August 202615 September 2026
3 measurements spanning 39 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 11–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 00:3911-1
12 Aug 2026, 04:1612no change
7 Aug 2026, 09:1912first reading

Engagement

5 posts held, back to 29 March 2022 — 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 5 posts for this entry, the most recent from 15 December 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

122 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 28.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3528.7%
👏3125.4%
🥰2722.1%
👍2016.4%
🔥64.92%
🎉32.46%

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 4 of the 5 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 122 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 29 March 2022 to 15 December 2023, 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

10 Dec 2023, 10:00 UTC≈9,350 views100 reactionsread 12 August 2026

✊诚信赢天下 ,选择永远大于努力,抓住机会翻身 棋牌归集料, ✨ 免押金, 免押金, 免押金 🔥诚招:(大小车队)或(个人)(小白可学,一对一指导) 长期收U,公司正规跑分,五年以上资历,真诚寻找长期合作伙 伴!! ✈️合作详情联系ID; @qaz78799 ✈️合作详情联系ID; @qaz78799 🔥开元信誉集团大放量,(大盘口量多)日赚5000-100000很简单 🔥 主推支付宝,微信,银行卡(不限制银行)💋 ✨小白,散户,大佬,团队,皆可操作✨ 🔥流程:先把USDT准备好,财务先给你打款款+佣金,款到回我USDT。 🔥熟悉买U操作】准备好第一笔USDT来做,可循环跑。 🔥点位:15%~30%, 量大可以谈。 🔥保卡保料:死卡包赔5W,资金算我方,放心做。 🔥旗牌 二道 归集料,都是沉淀48小时以后的料子,无混,无黑。 🔥听话照做 …

👏31❤30🥰27👍12

5 Nov 2023, 12:36 UTC≈3,510 views0 reactionsread 12 August 2026

🌈🌈全网独家靠谱免押跑芬 日进斗金,机会难得 ✨正规棋牌盘口✨ 免押金, 免押金, 免押金 ✈️致富联系ID: @qaz78799 1️.开元棋牌大区盘口直出二道归集料, 都是沉淀48小时以后的料子,无混,无黑 2.日赚5000-100000很简单 3.卡接回U模式,USDT安全操作 4.佣金点位15~30% (量大可谈) 5.24小时保司法,不风控,不冻卡 6.长期对接大小车队,小白包教会 7.保卡保料:死卡包赔5W,资金算我方,放心做 8.诚信为本,长期合作共创辉煌!! 好项目想要财富.联系下方灰机 ✈️致富联系ID;@qaz78799 ✈️致富联系ID; @qaz78799

2 Apr 2022, 05:30 UTC≈1,210 views21 reactionsread 12 August 2026

只是一个跳转窗口 请点击下方ID联系我业务号细聊 ↓↓↓↓↓↓↓↓↓↓↓

👍8🔥6❤4🎉3

Showing the 5 most recent of 5 posts we hold for @kaishou778. 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.

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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“卡接回U模式跑分、免押跑分、寻找个人车队合作” (@kaishou778), 11 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/kaishou778.

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.