Telegram RegisterThe public register of Telegram
Telegram profile photo for Fortress fumbler

Channel

Fortress fumbler

@castlesolver

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

179subscribers

+2 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002758459309
TypeChannel
Username@castlesolver
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live1 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 1 September 2026
On Telegramt.me/castlesolver

Growth

1771791788 August 2026 — 177 subscribers9 August 2026 — 177 subscribers16 August 2026 — 178 subscribers25 August 2026 — 179 subscribers8 August 202625 August 2026
4 measurements spanning 16 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 177–179 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 03:27179+1
16 Aug 2026, 21:05178+1
9 Aug 2026, 05:51177no change
8 Aug 2026, 22:00177first reading

Engagement

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

Reaction mix

23 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 52.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1252.2%
👍521.7%
🎉28.70%
👎28.70%
🙏28.70%

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 8 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 23 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 15 October 2025 to 1 April 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

1 Apr 2026, 14:18 UTC309 viewsread 8 August 2026

Looking for some people to test an api (only send otp twitter) dm me free for now

Signed Sysy's

9 Feb 2026, 19:16 UTC559 viewsread 8 August 2026

updated to solve this issue ⚠️solver is still flagged on rockstar register/login & twitter

Signed Sysy's

9 Feb 2026, 17:54 UTC567 viewsread 8 August 2026

For the idk how many people that were still using my solver even if it was flagged, i updated the db cuz im working on the solver and like it broke the hosted version, no eta for it to be up again

Signed Sysy's

6 Feb 2026, 12:20 UTC629 viewsread 8 August 2026

Looking for someone able to test twitter register (i only provide castle solver) ( atleast 50-100 threads ) dm me

Signed Sysy's

7 Dec 2025, 14:09 UTC≈1,130 views7 reactionsread 8 August 2026

As a lot of people still asking: - Solver does not work currently for twitter (still tryna find out whats flagging) - Solver seems to have stopped working for rockstar register I am still working on it, fixing things and updating everyday to hopefully fix the solver. Don't worry i keep y'all updated if i manage to fix smth, so please no need to dm me to ask if the solver is working, just check here.

👍43

Signed Sysy's

29 Nov 2025, 09:30 UTC940 views3 reactionsread 8 August 2026

Server up again, sorry for the delays

🎉21

Signed Sysy's

25 Nov 2025, 13:50 UTC895 views2 reactionsread 8 August 2026

Rockstar should be working (using the browser user agent, chrome 105-142) The launcher will not work since it's not the good headers For now i am working on twitter & the lastest castle version.

👎2

Signed Sysy's

23 Nov 2025, 11:38 UTC749 views2 reactionsread 8 August 2026

For now i'll focus on working on rockstar and then i'll work on updating for the new twitter version

2

Signed Sysy's

21 Nov 2025, 09:09 UTC779 views2 reactionsread 8 August 2026

Twitter just updated castle again a newer version, so will take even more time sorry for delays 🙏

🙏2

Signed Sysy's

17 Nov 2025, 16:05 UTC662 viewsread 8 August 2026

Working on improving the solver quality and avoid success rate drops, I've found the issue but taking some time (I was not on the right captcha version). I'll keep y'all updated

Signed Sysy's

13 Nov 2025, 16:11 UTC660 viewsread 8 August 2026

Added a edge support using the "browser" key (see docs)

Signed Sysy's

3 Nov 2025, 10:26 UTC724 viewsread 8 August 2026

Also added support for chrome version for 105+

Signed Sysy's

Showing the 12 most recent of 19 posts we hold for @castlesolver. 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 2 registered channels — 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“Fortress fumbler” (@castlesolver), 179 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/castlesolver.

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.