Telegram RegisterThe public register of Telegram
Telegram profile photo for Wancen calls

Channel

Wancen calls

@berkahcalls

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

248subscribers

-3 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-1001695071944
TypeChannel
Username@berkahcalls
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/berkahcalls

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

248251249.57 August 2026 — 251 subscribers7 August 2026 — 251 subscribers6 September 2026 — 250 subscribers28 September 2026 — 249 subscribers7 October 2026 — 248 subscribers7 August 20267 October 2026
5 measurements spanning 62 days, net -3. 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 248–251 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 18:16248-1
28 Sept 2026, 02:19249-1
6 Sept 2026, 10:38250-1
7 Aug 2026, 02:18251no change
7 Aug 2026, 01:12251first reading

Engagement

20 posts held, back to 10 October 2025 — 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 5 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 May 2026, 17:35 UTC158 viewsread 7 August 2026

https://dexscreener.com/ethereum/0x970d44425e72193204edc05d6f31b0e3fddced85eaa8d570c5dd129d75b6b76e

Signed Jee👨‍🚀🧸

4 Feb 2026, 06:41 UTC309 viewsread 7 August 2026
Sticker

Sticker, posted without a caption

Signed Jee👨‍🚀🧸

16 Nov 2025, 11:03 UTC353 viewsread 7 August 2026

When btc hits 110k aster gnna be at ath

Signed Jee👨‍🚀🧸

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

“Wancen calls” (@berkahcalls), 248 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/berkahcalls.

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.