Telegram RegisterThe public register of Telegram
Telegram profile photo for BotWitter

Channel

BotWitter

@BotWitterTG

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

162subscribers

+46 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-1003401893559
TypeChannel
Username@BotWitterTG
CreatedBetween 1 November 2025 and 10 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live17 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/BotWitterTG

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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

1161621397 August 2026 — 116 subscribers9 August 2026 — 116 subscribers16 August 2026 — 119 subscribers23 August 2026 — 122 subscribers29 August 2026 — 129 subscribers6 September 2026 — 136 subscribers14 September 2026 — 138 subscribers28 September 2026 — 148 subscribers7 October 2026 — 151 subscribers15 October 2026 — 154 subscribers23 October 2026 — 156 subscribers31 October 2026 — 157 subscribers7 November 2026 — 158 subscribers17 November 2026 — 162 subscribers7 August 202617 November 2026
14 measurements spanning 102 days, net +46. 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 109–169 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 11:18162+4
7 Nov 2026, 21:07158+1
31 Oct 2026, 13:46157+1
23 Oct 2026, 13:28156+2
15 Oct 2026, 21:07154+3
7 Oct 2026, 23:01151+3
28 Sept 2026, 07:41148+10
14 Sept 2026, 16:58138+2
6 Sept 2026, 19:17136+7
29 Aug 2026, 22:37129+7
23 Aug 2026, 12:17122+3
16 Aug 2026, 18:04119+3
9 Aug 2026, 05:16116no change
7 Aug 2026, 20:28116first reading

Engagement

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

Reaction mix

2 reactions across 2 posts, 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 5 of the 20 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 20 most recent posts we hold, published 10 January 2026 to 8 July 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

8 Jul 2026, 19:07 UTC175 viewsread 9 August 2026

Hello, We've released the python version of the castle test code: BotWitter/twitter-castle-test-py Please make sure to match the proxy country with the castle country We also don't recommend curl_cffi TLS — it was getting flagged at high thread

6 Jul 2026, 15:10 UTC204 viewsread 9 August 2026

Hello, The Castle token has been updated. Chrome/149 user agent is now required We've also updated the test code and the CUID generation, which now uses the dashed format instead of bare — you can review our test code here: BotWitter/twitter-castle-test Old: 7f7d99b3c36a412c9c4829a2eb80e1d1 New: 7f7d99b3-c36a-412c-9c48-29a2eb80e1d1 Current results: 94%+ success rate with 100 threads.

1 Jul 2026, 20:21 UTC229 viewsread 9 August 2026

Hello, We noticed that the success rate has dropped again BotWitter/Castle is currently free while we're testing. Please note that we will be running high-thread tests, so the success rate may temporarily decrease during this period Rate limit: 7 requests/second. Exceeding the limit will consume PAYG credits Thank you for your understanding

13 Jun 2026, 06:16 UTC302 views0 reactionsread 9 August 2026

We've temporarily disabled subscription plans Currently only the pay-as-you-go plan is supported The price has been updated to $0.55 per 1K

13 Jun 2026, 05:54 UTC283 viewsread 9 August 2026

Castle test code for the new Twitter API (JFAPI) is now available: https://github.com/BotWitter/twitter-castle-test

11 Jun 2026, 18:31 UTC271 viewsread 9 August 2026

Hi, we added Android application support, tested with DailyPay. Check the documentation for an example We also tested the Rockstar/forgotten endpoint, and it works with 50 threads

11 Jun 2026, 14:28 UTC246 views0 reactionsread 9 August 2026

Hi, we pushed an update for the X/Twitter Castle token DM for trial/test key. were still testing

25 Mar 2026, 13:54 UTC491 viewsread 9 August 2026
Photo

Hi, the registration rate has been improved (90%) on Twitter use 145 user agent.

Signed x

16 Mar 2026, 18:45 UTC504 viewsread 9 August 2026

Hello, sorry for the delay, I was busy Castle success rate has been improved ( registration is still not 100% stable, I will check it) Subscriptions have been extended by 1 week

Signed x

4 Mar 2026, 15:31 UTC499 views0 reactionsread 9 August 2026

Hi, Castle solver is not working for now ill fix.

Signed x

Showing the 12 most recent of 20 posts we hold for @BotWitterTG. 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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“BotWitter” (@BotWitterTG), 162 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/BotWitterTG.

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.