Telegram RegisterThe public register of Telegram
Telegram profile photo for ELONGATE - Staking Alerts

Channel

ELONGATE - Staking Alerts

@EGStakingAlerts

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

60subscribers

-1 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-1001632879126
TypeChannel
Username@EGStakingAlerts
CreatedBetween 1 December 2021 and 20 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live9 October 2026
Measurements held3
Confirmed unchanged4 times, most recently 9 October 2026
On Telegramt.me/EGStakingAlerts

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

606160.57 August 2026 — 61 subscribers10 August 2026 — 61 subscribers8 September 2026 — 60 subscribers7 August 20268 September 2026
3 measurements spanning 32 days, net -1. 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 60–61 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 04:1560-1
10 Aug 2026, 04:3061no change
7 Aug 2026, 04:0461first reading

Engagement

20 posts held, back to 20 June 2022 — 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 22 June 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Jun 2022, 06:18 UTC372 viewsread 10 August 2026

🔴 Unstaked 717,977,700 (717M) worth $ 8.4 ELONGATE from EG Vault https://bscscan.com/tx/0x6976e623f00c7ba6a00081b57f992872587d37815d99384df017a1f2ab2fb38f

21 Jun 2022, 21:07 UTC366 viewsread 10 August 2026

🔴 Unstaked 175,579,931,510 (175B) worth $ 2,124 ELONGATE from EG Vault https://bscscan.com/tx/0x311b8a789b94799e4bf32a611e04751602444b67ce6834221fb39ab1b4662aaa

21 Jun 2022, 20:33 UTC293 viewsread 10 August 2026

🚀 Staked 48,308,533 (48M) worth $ 0.5 ELONGATE into EG Vault https://bscscan.com/tx/0x48c33ef74beba5d9286f3de69394bfc5963c9503c0bedc90385762f9c0f2d7ba

21 Jun 2022, 19:41 UTC199 viewsread 10 August 2026

🔴 Unstaked 1,203,126,589 (1.2B) worth $ 14 ELONGATE from EG Vault https://bscscan.com/tx/0x36b5c2777758508fab61e6270efde915465a385fe45e43248e71c4cbdd036978

21 Jun 2022, 17:19 UTC142 viewsread 10 August 2026

🚀 Staked 892,820,418 (892M) worth $ 10 ELONGATE into EG Vault https://bscscan.com/tx/0x61e0f6b4388fdf8f7ed679f1dbda7056d198be758aa16c4866cdc70629c7d42b

21 Jun 2022, 16:25 UTC118 viewsread 10 August 2026

🚀 Staked 460,156,650 (460M) worth $ 5.6 ELONGATE into EG Vault https://bscscan.com/tx/0xe8950aa2226f826f52641187118ed01d72919eb61947c6da4404b9b6a2bcca24

21 Jun 2022, 15:46 UTC95 viewsread 10 August 2026

🔴 Unstaked 528,562,737 (528M) worth $ 6.4 ELONGATE from EG Vault https://bscscan.com/tx/0x1dc45dc60d263e8e33aa257766c63b118ed9635972457c04b066a145f72350a9

21 Jun 2022, 12:32 UTC83 viewsread 10 August 2026

🔴 Unstaked 20,681,761,565 (20B) worth $ 246 ELONGATE from EG Vault https://bscscan.com/tx/0x21c13e3395afe04837ead534c1bcf4a1fb31dd18cae061cf8cf2737b06b43f57

21 Jun 2022, 11:07 UTC80 viewsread 10 August 2026

🔴 Unstaked 5,124,766,761 (5.1B) worth $ 61 ELONGATE from EG Vault https://bscscan.com/tx/0xe7ab04abadd001a39206a5ecd104ab63d482c1a8884a2da71b86f58260ced4f9

21 Jun 2022, 06:10 UTC73 viewsread 10 August 2026

🔴 Unstaked 1,675,000,602 (1.6B) worth $ 20 ELONGATE from EG Vault https://bscscan.com/tx/0xa75e17a34e9b57504ee0093b5dd86fa2f5a2b89615f6ff39a134429620190587

21 Jun 2022, 05:22 UTC74 viewsread 10 August 2026

🔴 Unstaked 113,629,646,260 (113B) worth $ 1,355 ELONGATE from EG Vault https://bscscan.com/tx/0xec687de339eef364348cdcdb3db14547902878d7dbf0b5781396e80d6f9bafc6

21 Jun 2022, 02:50 UTC67 viewsread 10 August 2026

🚀 Staked 3,588,132,791 (3.5B) worth $ 42 ELONGATE into EG Vault https://bscscan.com/tx/0x8ac0c2b1a07944c54f599cb301f13c11372b96a7a6f68af0817ea4f85faf1ca1

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

“ELONGATE - Staking Alerts” (@EGStakingAlerts), 60 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/EGStakingAlerts.

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.