有需求,可以私聊 @CodyD
😱12❤8🤡1😇1

Channel
@voice_google
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
22,672subscribers
-258 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001227044103 |
|---|---|
| Type | Channel |
| Username | @voice_google |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/voice_google |
Ecommerce storefront — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 |
|---|---|---|
| 8 Sept 2026, 04:57 | 22,672 | -17 |
| 5 Sept 2026, 02:57 | 22,689 | -9 |
| 3 Sept 2026, 07:45 | 22,698 | -4 |
| 2 Sept 2026, 00:34 | 22,702 | -14 |
| 31 Aug 2026, 21:27 | 22,716 | -11 |
| 30 Aug 2026, 19:45 | 22,727 | -6 |
| 29 Aug 2026, 22:55 | 22,733 | -8 |
| 29 Aug 2026, 00:33 | 22,741 | -6 |
| 27 Aug 2026, 22:44 | 22,747 | -1 |
| 27 Aug 2026, 00:07 | 22,748 | -2 |
| 26 Aug 2026, 01:22 | 22,750 | -4 |
| 24 Aug 2026, 21:57 | 22,754 | -16 |
| 23 Aug 2026, 10:16 | 22,770 | -12 |
| 22 Aug 2026, 00:08 | 22,782 | -12 |
| 20 Aug 2026, 19:03 | 22,794 | -4 |
| 19 Aug 2026, 22:11 | 22,798 | -7 |
| 18 Aug 2026, 19:56 | 22,805 | -9 |
| 17 Aug 2026, 21:14 | 22,814 | -36 |
| 16 Aug 2026, 18:46 | 22,850 | -14 |
| 15 Aug 2026, 05:09 | 22,864 | first reading |
19 posts held, back to 11 November 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 58 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 16 August 2026 |
|---|---|
| Posts held | 19 (11 November 2023 – 16 August 2026) |
| Views total | 3,200 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 12:04 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.
929 reactions across 18 posts, in 18 distinct kinds. The most used accounts for 32.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 300 | 32.3% | |
| 👍 | 298 | 32.1% | |
| 🤡 | 71 | 7.64% | |
| 🤣 | 67 | 7.21% | |
| 🤔 | 49 | 5.27% | |
| 💔 | 42 | 4.52% | |
| 😁 | 40 | 4.31% | |
| 😱 | 12 | 1.29% | |
| 🎅 | 11 | 1.18% | |
| 💯 | 9 | 0.969% | |
| 👎 | 8 | 0.861% | |
| 👀 | 6 | 0.646% | |
| 👏 | 4 | 0.431% | |
| 🔥 | 4 | 0.431% | |
| 🎉 | 3 | 0.323% | |
| 😴 | 3 | 0.323% | |
| 🖕 | 1 | 0.108% | |
| 😇 | 1 | 0.108% |
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 18 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 929 reactions 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 11 November 2023 to 16 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.
有需求,可以私聊 @CodyD
😱12❤8🤡1😇1
表 0. 07月09日特价号码 | 价格 | 所属州 (757) 447-4444 | 1000 | Virginia 每2分钟更新一波 #GoogleVoice 列表更新于: 16:02:36
💔42❤34👍17😁10👎4🤡1
Google Voice 靓号 ✨ pinned Deleted message
看到这个Bot @SptenBot 请举报 #spam
❤35👍6👀4💯4👏3
又来了,乍一看是官方链接,但点击后却指向了这个Spam Bot。还不知道该如何举报这个SB Bot ……
😁26❤15👍8💯3👀2🖕1
Telegram/电报/飞机注册疑难杂症 注册Telegram有可能碰到的问题是: 1. Telegram提示验证已发送到其他Telegram客户端 2. Telegram注册后不久就被封 针对问题1的误提示,主要是因为注册客户端的问题(少部分情况是因为注册IP质量较差)。网页客户端或电脑客户端无法用于注册,只能用于账号登录,建议使用苹果手机客户端进行注册。 Android设备(不包括华为)可以重新安装官方客户端: - 官方Telegram客户端 - 官方Telegram X客户端 苹果手机设备可以卸载后重新安装Telegram客户端。 针对问题2,问题可能是由注册环境(IP或客户端)引起的,此时只能尝试向Telegram申诉。具体方法有四种: 1. 直接点击被封页面的“Help”按钮发送邮件申诉 2. 在x.com上私聊@smstelegram 3. 在Telegram应用设置页面点击“Ask a Question”联系…
❤16👍13🎉3😴3💯2
有点以假乱真的感觉... 这开了会员的账号这么耐操么 #scam
👍18❤3
🇬🇧 GiffGaff实体卡 还有几张(零月租,无需实名,且保号成本极低),激活后即插即用,也可以转换为 eSIM。 余额=0,价格50元包邮到家 余额=15英镑,价格150元包邮到家 可以免费帮忙生成 eSIM 二维码,供 5ber 或 estk 等芯片卡直接扫描。感兴趣的私聊管理,或直接加微信 CodyDoby #giffgaff
❤36👍16👎4
1Password Family车,年付35元。自备账号,拉你进家庭组。 9月09日:还剩1个位置 #1password
❤10👍5
🎉🎁Netflix 合租🎁🎉 合租人数:5人 合租价格:15元/人/月 合租方式:子账号登陆 地域限制:最好都用美国节点(因为我的是美国节点) 8月21刚订购的家庭成员共享计划,感兴趣的私聊! #netflix
👍25❤10🔥2
Telegram 会员(原价35.99美元/年)骨折价代充 价格: 限时优惠26USD = 186 RMB / 年 方式: 登号开通 正规途径,非盗刷,需要的私聊管理 #telegram
🤔27👍10❤5😁4
需要尼日利亚 eSIM 的朋友请联系,11美元(最近办理问题多,涨价了)一个。这是黑人兄弟亲自去当地营业厅按指纹办理的,来之不易。eSIM扫码即可下载到手机使用。 接收短信是免费的,发送短信、接打电话或使用流量可以通过“Pay As You Go”方式进行(费用较高),也可以选择订购7日,14日,30日漫游包。 保号成本非常低,只需人民币5元左右即可一次性保号3年(只需订购一个订阅,无需担心充值或使用的细节)。 更多关于号码的细节,来询哈! PS 说到走向非洲,他们国家的身份也可随意注册,感兴趣的也可以聊聊! #MTN #eSIM
❤27👍12🤔4
Showing the 12 most recent of 19 posts we hold for @voice_google. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
美国备受欢迎的运营商US Mobile的eSIM绝版套餐,每月$5,包括500分钟通话和500条短信(500MB流量可有可无)。在大陆可以通过Wi-Fi Calling使用通话和短信,现在官网已停售,有感兴趣的吗?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 19 most recent posts we hold, published 11 November 2023 to 16 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
@voice_google named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Google Voice 靓号 ✨✔️” (@voice_google), 22,672 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/voice_google.
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.