Telegram RegisterThe public register of Telegram
Telegram profile photo for 巴西📱ws实卡接码注册可续

Channel

巴西📱ws实卡接码注册可续

@BrailG0123

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

71subscribers

+33 since we began measuring on 18 October 2026

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

Register entry

Telegram ID-1004372106919
TypeChannel
Username@BrailG0123
CreatedBetween 1 June 2026 and 10 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 October 2026
Last confirmed live16 November 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/BrailG0123

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 7 November 2026 and assigned it the closest of 31 fixed categories, at 60% 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 the other topics.

Growth

387154.518 October 2026 — 38 subscribers18 October 2026 — 38 subscribers18 October 2026 — 42 subscribers25 October 2026 — 61 subscribers31 October 2026 — 70 subscribers7 November 2026 — 57 subscribers16 November 2026 — 71 subscribers18 October 202616 November 2026
7 measurements spanning 30 days, net +33. 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 33–76 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 17:2071+14
7 Nov 2026, 20:4657-13
31 Oct 2026, 13:4770+9
25 Oct 2026, 05:4761+19
18 Oct 2026, 21:3942+4
18 Oct 2026, 02:2238no change
18 Oct 2026, 01:4738first reading

Engagement

10 posts held, back to 10 September 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 10 posts for this entry, the most recent from 16 October 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.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 1 of the 10 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 10 September 2026 to 16 October 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

16 Oct 2026, 18:53 UTC17 viewsread 18 October 2026
Photo

西班牙M卡还有100多张 国内可发

Signed 悟空-巴西实卡接码 ws、tg等APP实卡接码

16 Oct 2026, 18:11 UTC19 viewsread 18 October 2026
Photo

巴西11号段实卡现货,其他号段支持预定!!!

Signed 悟空-巴西实卡接码 ws、tg等APP实卡接码

3 Oct 2026, 04:02 UTC94 viewsread 18 October 2026

手上一批巴西11号段实体卡 特价处理 只接码, 带回国死卡自己负责

Signed 悟空-巴西实卡接码 ws、tg等APP实卡接码

3 Oct 2026, 04:01 UTC95 viewsread 18 October 2026
Photo

巴西现货, 来各大盘口 渠道商 中介合作! 第一手 无中间商!

Signed 悟空-巴西实卡接码 ws、tg等APP实卡接码

30 Sept 2026, 14:06 UTC120 viewsread 18 October 2026
Photo

波兰实卡接码注册 ,可包月可续费! 不限次数无限接码.....

Signed 悟空-巴西实卡接码 ws、tg等APP实卡接码

30 Sept 2026, 02:44 UTC118 viewsread 18 October 2026
Photo

现货在手 巴西TIM 11号段现货,随时可以插卡

Signed 悟空-巴西实卡接码 ws、tg等APP实卡接码

30 Sept 2026, 01:12 UTC114 views2 reactionsread 18 October 2026

TG知识分享(两种方法): 一:个人账号解除双向聊天限制 👉搜索 @spambot 👉点击 Start 👉点击 But I can't message non-contacts! 👉点击 No,I'll never do any of this! 👉回复 accident 约25分钟左右就恢复正常了,有些解禁时间会较长,有些需要发邮件向官方提出解封申请 二:个人账号解除双向聊天限制: 第一步:搜索 @spambot 第二步:点击 Start 第三步:点击 This is a mistake 第四步:点击 Yes 第五步:点击 No,I'll never do any of this! 第六步:回复(点击以下英文,即可复制发送) I have no idea, I have always been very abiding by the use of telegram. It's just that there are t…

❤2

Signed 悟空-巴西实卡接码 ws、tg等APP实卡接码

30 Sept 2026, 01:11 UTC99 viewsread 18 October 2026

😀WhatsApp Messenger(个人版) 官网下载地址:https://www.whatsapp.com/download/ (包含:Mac/IOS/Android/Web) 😀WA Business(商业版) 官网下载地址:https://business.whatsapp.com/products/business-app ⭐️推荐软件下载网站(此网站可以下载市面绝大多数应用): Windows : https://www.uptodown.com/windows Mac : https://www.uptodown.com/mac Android : https://www.uptodown.com/ ❤️Telegram 官网 : https://telegram.org/ 👍TRC交易查询:https://tronscan.org/#/ 👍ERC交易查询:https://e…

Signed 悟空-巴西实卡接码 ws、tg等APP实卡接码

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

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.

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

“巴西📱ws实卡接码注册可续” (@BrailG0123), 71 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/BrailG0123.

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.