Telegram RegisterThe public register of Telegram
Telegram profile photo for 巴西实卡接码。

Channel

巴西实卡接码。

@vivobrcom

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

24subscribers

+2 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1003728043525
TypeChannel
Username@vivobrcom
Created2 May 2026 — measured — dated from the channel’s first post
First recorded19 August 2026
Last confirmed live5 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/vivobrcom

Topic

Hacking & security — 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 1 October 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.

Growth

212422.519 August 2026 — 22 subscribers20 August 2026 — 22 subscribers26 August 2026 — 21 subscribers3 September 2026 — 22 subscribers25 September 2026 — 23 subscribers5 October 2026 — 24 subscribers19 August 20265 October 2026
6 measurements spanning 47 days, net +2. 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 21–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Oct 2026, 18:5724+1
25 Sept 2026, 04:4023+1
3 Sept 2026, 06:3622+1
26 Aug 2026, 16:3521-1
20 Aug 2026, 13:1822no change
19 Aug 2026, 13:1522first reading

Engagement

12 posts held, back to 2 May 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 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 12 posts for this entry, the most recent from 18 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4100.0%

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

Measured over the 12 most recent posts we hold, published 2 May 2026 to 18 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.

Recent posts

18 Aug 2026, 12:32 UTC13 views1 reactionsread 19 August 2026

新业务上线|巴西本土数据资源一手供应 提供巴西任何资料,非国家级网站资料,都可以提供,一手供应,如博彩料,股民料等等,合适盘口对接,精聊,快杀。https://t.me/topupm2

❤1

13 Aug 2026, 21:35 UTC38 viewsread 19 August 2026
Photo

出巴西公司。一套完整公司资料+法人资料,包括身份信息都有。有需要私聊我。https://t.me/topupm2

4 Aug 2026, 22:14 UTC74 viewsread 19 August 2026

🇧🇷 巴西 WhatsApp 老号|源头供应 专注巴西本土账号资源,长期稳定供应。 ✅ 老号资源充足 ✅ 支持批量采购 ✅ 一手渠道,品质稳定 ✅ 快速交付,长期售后 ✅ 欢迎代理、工作室、企业客户合作 坚持正规合作,诚信经营,让每一次合作都值得信赖。 联系 @topupm2

20 Jul 2026, 09:23 UTC117 viewsread 19 August 2026

做巴西盘口的盘总有吗?聊一聊,给我个机会,送你个惊喜。 @topupm2

17 Jun 2026, 15:02 UTC199 views3 reactionsread 19 August 2026
Photo

几十部设备同时在线,上新嘎嘎猛

❤3

9 Jun 2026, 07:32 UTC210 viewsread 19 August 2026

🇧🇷 巴西实卡源头 🔥 接码服务,实卡邮寄中国/香港 长期在线维护,量大稳定供应 📦 有需求直接聊,欢迎骚扰 🤝 合作共赢,长期发展 📈 @topupm2

8 Jun 2026, 14:59 UTC172 viewsread 19 August 2026
Photo

🚀 巴西 WhatsApp 资源稳定供应 🚀 🔥 上新嘎嘎快,复接嘎嘎及时! 🔥 巴西实卡资源充足,长期稳定供货! 🔥 设备齐全,流程成熟,响应迅速! 🔥 支持批量需求,大单小单统统接! 🔥 专业团队运营,售后跟进无忧! ✅ 巴西实卡 ✅ WhatsApp 注册 ✅ 长期稳定复接 ✅ 资源持续更新 ✅ 快速交付 有量你就来! 有单尽管砸! 实力接单,诚信合作,共赢发展! 📲 欢迎咨询 @topupm2 🤝 长期合作优先 💰 大客户价格更优 巴西资源 · 稳定供应 · 快速响应 你的订单,我们全力以赴!

22 May 2026, 04:47 UTC188 viewsread 19 August 2026
Photo

🇧🇷 大量出巴西VIVO正规SIM卡|自带话费·即插即用·可漫游可续费 ✅ 正规Vivo原卡(+55号段) 巴西最大运营商,覆盖全、信号稳,支持4G/5G。 ✅ 到手即用,自带话费 无需实名、无需激活,插卡即可用,内含余额/流量。 ✅ 有效期长: 首次有效期3个月(90天),足够长期使用。 ✅ 支持国际漫游(含中国) 回国也能收短信、接验证码、登WhatsApp,稳定不掉线。 ✅ 可邮寄回国 巴西直发/国内代发,全国可邮,轻松拿到巴西本地号。 ✅ 续费简单划算 续费仅35巴币(R$35),即可延长3个月有效期,保号无忧。 🔥 适合人群 • ✅ 巴西WhatsApp/SMS群发(官方通道首选) • ✅ 跨境电商、外贸、海外社媒运营 • ✅ 需要长期持有巴西本地号 • ✅ 收验证码、注册巴西各类平台 📦 规格 • 运营商:Vivo(巴西) • 号段:+55 • 初始有效期:90天 • 续费:R$35 …

2 May 2026, 18:55 UTC218 viewsread 19 August 2026
Photo

✅ 真实TIM实卡资源(非虚拟号,成功率更高) ✅ 支持主流平台验证码 ✅ 本地巴西号段,风控低,适合长期养号 ✅ 接码速度快,秒收验证码 ✅ 稳定批量产出,可持续放量 ✅联系方式:@topupm2

2 May 2026, 18:52 UTC204 viewsread 19 August 2026
Photo

稳定供应巴西Vivo实卡,支持多地区区号资源输出。 国际漫游覆盖175国,适合渠道合作、批量使用及海外业务布局,长期稳定供货。联系方式:@topupm2

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

Mentions

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.

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

“巴西实卡接码。” (@vivobrcom), 24 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/vivobrcom.

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.