Telegram RegisterThe public register of Telegram
Telegram profile photo for #Berbatas

Channel

#Berbatas

@Berbatas

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

155subscribers

-2 since we began measuring on 9 August 2026

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

Register entry

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

Growth

1551571569 August 2026 — 157 subscribers10 August 2026 — 157 subscribers16 August 2026 — 156 subscribers24 August 2026 — 155 subscribers9 August 202624 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 155–157 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 21:27155-1
16 Aug 2026, 16:37156-1
10 Aug 2026, 00:31157no change
9 Aug 2026, 09:17157first reading

Engagement

20 posts held, back to 17 May 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 25 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

25 Jul 2026, 07:05 UTC31 viewsread 9 August 2026

@kmelinci ufs di 6xx bisa ke 5xx kalau fullpay yahh

Signed Ryufan.

25 Jul 2026, 06:43 UTC35 viewsread 9 August 2026

@mikagei @zvinny all ufs 160k/@ huhu lagi inrush bwt buku

Signed ‎𝜗ৎ 🎄 neath wayn 𓃴 🧣⊹ ࣪ ˖ JASTIP USERNAME

18 Jul 2026, 09:58 UTC67 viewsread 9 August 2026

avail trade juga kuy tapi ke gift

Signed ‎𝜗ৎ 🎄 neath wayn 𓃴 🧣⊹ ࣪ ˖ JASTIP USERNAME

17 Jul 2026, 11:46 UTC69 viewsread 9 August 2026

@knagi @mikagei @zvinny lagi Buu huhu ufs yupp tanya ke bot @berbatasbot

Signed ‎𝜗ৎ 🎄 neath wayn 𓃴 🧣⊹ ࣪ ˖ JASTIP USERNAME

10 Jul 2026, 06:36 UTC98 viewsread 9 August 2026

take yang in dong inrush banget bangett 🥺

Signed ‎𝜗ৎ 🎄 neath wayn 𓃴 🧣⊹ ࣪ ˖ JASTIP USERNAME

10 Jul 2026, 05:11 UTC84 viewsread 9 August 2026

halloo @mikagei stil ufs ya

Signed ‎𝜗ৎ 🎄 neath wayn 𓃴 🧣⊹ ࣪ ˖ JASTIP USERNAME

1 Jul 2026, 02:14 UTC123 viewsread 9 August 2026

sebelum back NFS best

Signed ‎𝜗ৎ 🎄 neath wayn 𓃴 🧣⊹ ࣪ ˖

30 Jun 2026, 16:29 UTC119 viewsread 9 August 2026

@knagi ufs inrush best

Signed ‎𝜗ৎ 🎄 neath wayn 𓃴 🧣⊹ ࣪ ˖

28 Jun 2026, 14:21 UTC127 viewsread 9 August 2026

Muewlnya ada di 1xx yaa, for more boleh ke bot. Gak gigit kok 🥰

Signed Mysha

14 Jun 2026, 12:44 UTC189 viewsread 9 August 2026

bye @.suamti @.parksuynghoon take sisanya yok abisin @Sualmi 1xx @TaheyungKim 25k

Signed dni

14 Jun 2026, 03:33 UTC186 viewsread 9 August 2026

@zvinny qyop

Signed ‎𝜗ৎ 🎄 neath wayn 𓃴 🧣⊹ ࣪ ˖

9 Jun 2026, 11:34 UTC206 viewsread 9 August 2026

hi take usn dibawah, All inrush jabgan dijadiin patokan. @.Suamti pu fg 2xx inrush @Sualmi 1xx awal inrush @TaheyungKim 25k @ParkSuynghoon 15k Avail nego tebel ya lagi inrush

Signed dni

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

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

“#Berbatas” (@Berbatas), 155 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/Berbatas.

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.