Telegram RegisterThe public register of Telegram
Telegram profile photo for Endless Battlefield Announcements

Channel

Endless Battlefield Announcements

@EBgame_channel

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

3,352subscribers

-78 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001750192375
TypeChannel
Username@EBgame_channel
CreatedBetween 1 December 2021 and 9 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/EBgame_channel

Growth

3,3523,4303,3917 August 2026 — 3,430 subscribers7 August 2026 — 3,429 subscribers11 August 2026 — 3,418 subscribers14 August 2026 — 3,412 subscribers17 August 2026 — 3,403 subscribers20 August 2026 — 3,391 subscribers24 August 2026 — 3,366 subscribers27 August 2026 — 3,363 subscribers30 August 2026 — 3,358 subscribers3 September 2026 — 3,356 subscribers8 September 2026 — 3,352 subscribers7 August 20268 September 2026
11 measurements spanning 33 days, net -78. 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 3,340–3,442 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 20:213,352-4
3 Sept 2026, 08:383,356-2
30 Aug 2026, 17:443,358-5
27 Aug 2026, 20:123,363-3
24 Aug 2026, 11:523,366-25
20 Aug 2026, 17:423,391-12
17 Aug 2026, 21:423,403-9
14 Aug 2026, 17:573,412-6
11 Aug 2026, 05:313,418-11
7 Aug 2026, 20:203,429-1
7 Aug 2026, 01:163,430first reading

Engagement

20 posts held, back to 9 June 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages 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 3 August 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 Aug 2022, 00:30 UTC≈6,770 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1554625535287824384

Signed CalmLm

25 Jul 2022, 10:35 UTC≈5,430 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1551516002642366464

Signed CalmLm

23 Jul 2022, 14:38 UTC≈4,710 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1550851375050788864

Signed CalmLm

23 Jul 2022, 08:41 UTC≈3,130 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1550762754985799681

Signed CalmLm

22 Jul 2022, 03:46 UTC≈2,700 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1550326236479512576

Signed CalmLm

21 Jul 2022, 11:58 UTC≈2,470 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1550087264775983104

Signed CalmLm

19 Jul 2022, 12:03 UTC≈2,210 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1549363890571472897

Signed CalmLm

16 Jul 2022, 10:07 UTC≈2,050 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1548247708770570240

Signed CalmLm

11 Jul 2022, 02:41 UTC≈2,030 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1546323433222352896

Signed CalmLm

2 Jul 2022, 02:04 UTC≈1,960 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1543052687318458369

Signed CalmLm

28 Jun 2022, 02:56 UTC≈1,910 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1541616284940517377

Signed CalmLm

24 Jun 2022, 10:00 UTC≈2,130 viewsread 7 August 2026

https://twitter.com/EBMetaverse/status/1540273560911896576

Signed CalmLm

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

“Endless Battlefield Announcements” (@EBgame_channel), 3,352 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/EBgame_channel.

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.