无语的时候是挺无语的!好久不见
Signed yuyi

Channel
@PerfectCallsss
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,795subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001822236613 |
|---|---|
| Type | Channel |
| Username | @PerfectCallsss |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/PerfectCallsss |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 19:51 | 1,795 | -5 |
| 7 Aug 2026, 20:35 | 1,800 | no change |
| 7 Aug 2026, 09:46 | 1,800 | first reading |
19 posts held, back to 27 November 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 19 posts for this entry, the most recent from 12 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
25 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 68.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17 | 68.0% | |
| ❤ | 6 | 24.0% | |
| 🔥 | 2 | 8.00% |
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 11 of the 19 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 25reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 27 November 2024 to 12 May 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.
无语的时候是挺无语的!好久不见
Signed yuyi
🤣
Signed yuyi
0xce33defefac76bf36367d0640b5079bb3065e9d7 真主系列以小博大
❤1
Signed yuyi
bsc主场了,三天从一万美金市值干到一亿美金市值,妥妥的万倍,这种才算暴富币,在币安链机会是有的,但是前提你要积累无限子弹,因为坑更多,大部分买了都直接归零🙃
Signed yuyi
neiro原主人发了个币现在市值和neiro差不多了,我也是钻石手很看好neiro社区即使跌成这样我也没抱怨过!对于阴谋割韭菜的狗逼们大家都不要去抬!我相信那种币大交易所也会抵制,行情好了neiro也会重新站起来
👍1
Signed yuyi
今晚的白宫会议大家都不会看好,如果说连这种级别的新闻会议都拉稀那么二级就没幻想了
Signed yuyi
btc跌破八万离6万也不远了,十二月份满仓山寨和大饼,只能等三年回本了
Signed yuyi
感谢官方,我就知道你们会看到努力做事的社区实实在在的!而不是阴谋卡点
❤2👍2🔥2
Signed yuyi
其实除了比特币大户,那几个主流刚开始跌,山寨也就那样了,目前之前比较火的几十亿市值的山寨跌的剩一个多亿!已经跌了20x也不可能再跌很多倍,其实今年就是熊市,大家一开始就知道,只不过是因为特朗普上台制造了烟雾弹大家一直才觉得牛市依然在
Signed yuyi
如果不是bybit本来已经有点回暖
👍1
Signed yuyi
草泥马二级meme再跌要去几千万美金市值了,那么一级市场几千万美金市值就得是终点了?牛市啥时候回来啊😭
Signed yuyi
二级市场有史以来崩盘最惨一次有人问满仓的怎么办?满仓凉拌已经亏了十分之九还怕那剩下的十分之一?
❤1
Signed yuyi
Showing the 12 most recent of 19 posts we hold for @PerfectCallsss. 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“🐳Perfect Calls” (@PerfectCallsss), 1,795 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/PerfectCallsss.
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.