Telegram RegisterThe public register of Telegram
Telegram profile photo for Go4C - ENG

Channel

Go4C - ENG

@go4crypto_eng

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

26subscribers

-2 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-1001359232402
TypeChannel
Username@go4crypto_eng
CreatedBetween 1 March 2018 and 30 April 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live25 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/go4crypto_eng

Growth

2628277 August 2026 — 28 subscribers11 August 2026 — 28 subscribers16 August 2026 — 27 subscribers25 August 2026 — 26 subscribers7 August 202625 August 2026
4 measurements spanning 17 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 26–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 01:3326-1
16 Aug 2026, 21:3327-1
11 Aug 2026, 06:3128no change
7 Aug 2026, 21:1428first reading

Engagement

20 posts held, back to 30 April 2020the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 34s
Average length
1m 34s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

5 Jul 2026, 07:59 UTC8 viewsread 11 August 2026

There are no updates for the project for over 17 month. If something will change a info will be displayed here.

4 Jul 2026, 17:07 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

10 Mar 2023, 11:50 UTC89 viewsread 11 August 2026

Dear investors, We would like to inform you that all pending withdrawals and wallets have been reset. We noticed that some wallet addresses were invalid or out of date and need to be updated for future payouts. Unfortunately, some providers who have made payments in the past no longer exist on the market. We want to make sure your payouts are sent to the correct and new wallets in the future. Starting today, you ha

12 Mar 2022, 09:01 UTCviews —

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 28 days, that account will self-destruct and this channel may no longer have an owner.

29 Jun 2021, 22:53 UTC147 viewsread 11 August 2026

https://insights.glassnode.com/the-week-on-chain-week-26-2021/

29 Jun 2021, 22:53 UTC130 viewsread 11 August 2026

https://insights.glassnode.com/the-week-on-chain-week-25-2021/

20 Jul 2020, 12:30 UTC151 viewsread 11 August 2026

Dear members today and next week, we will not have a Monday webinar. From August we will be there for you as usual on Mondays and Wednesdays.

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

Citation-graph rank

Citation-graph rank — 607,979 of 1,621,754entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“Go4C - ENG” (@go4crypto_eng), 26 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/go4crypto_eng.

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.