Telegram RegisterThe public register of Telegram
Telegram profile photo for BlackCaesar’s 100x Calls

Channel

BlackCaesar’s 100x Calls

@CaesarsCourt

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

950subscribers

+96 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-1001468811134
TypeChannel
Username@CaesarsCourt
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/CaesarsCourt

Topic

Crypto & trading — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 42% 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

854959906.57 August 2026 — 854 subscribers7 August 2026 — 854 subscribers16 August 2026 — 857 subscribers24 August 2026 — 861 subscribers31 August 2026 — 938 subscribers9 September 2026 — 959 subscribers19 September 2026 — 950 subscribers9507 August 202619 September 2026
7 measurements spanning 43 days, net +96. 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 838–975 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 05:00950-9
9 Sept 2026, 18:21959+21
31 Aug 2026, 11:53938+77
24 Aug 2026, 02:03861+4
16 Aug 2026, 02:18857+3
7 Aug 2026, 15:04854no change
7 Aug 2026, 05:17854first reading

Engagement

20 posts held, back to 3 August 2026the 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Aug 2026, 15:08 UTC19 viewsread 7 August 2026
Forwarded from @gogolajournal

CT9JxNCdJPtAFP2oGrSHH8jAzpBpTpjtCktDZb1FtnJt This on solanac will try to slow cook it. 10k rn

4 Aug 2026, 12:13 UTC26 viewsread 7 August 2026
Forwarded from @KOLscopeVideo

🟪 MULTIPLIER DETECTED: 2x+ @CaesarsCourt made 2x+ on DISCORD. $7.6K ⮕ $16.4K 🔎 Call❕💍 KOL❕✨ Account 🆖 $BLACKCAT entered TRENDING ⚡Discover the next gem! 🟪

4 Aug 2026, 11:25 UTC19 viewsread 7 August 2026
Forwarded from @cryptoseralpha

https://dexscreener.com/solana/huflaangrjf5kenmz2nfranhjxy3jay1gszef6lqi4dd friend in my chat doing cto on this made a discord already tiktok at 4 million. https://discord.gg/fbkvt8mB5

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“BlackCaesar’s 100x Calls” (@CaesarsCourt), 950 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/CaesarsCourt.

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.