Channel
@Golden_Squad_INFO
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
22subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001753227782 |
|---|---|
| Type | Channel |
| Username | @Golden_Squad_INFO |
| Description | 🔰Owner: @Golden_Squad_47 🔰Trust: @Trust_Golden |
| Created | 7 November 2021 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Golden_Squad_INFO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 13:15 | 22 | no change |
| 9 Aug 2026, 10:55 | 22 | first reading |
2 posts held, back to 7 November 2021 — 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 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 2 posts for this entry, the most recent from 7 November 2021. An engagement rate over an empty window would be a number about nothing.
𝗘𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 𝗬𝗼𝘂 𝗡𝗲𝗲𝗱 𝗧𝗼 𝗞𝗻𝗼𝘄 𝗔𝗯𝗼𝘂𝘁 [𝗠𝗘] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 𝗠𝘆 𝗝𝗼𝗯: 𝗖𝗿𝗮𝗰𝗸 RDP [ VPS / Server ] 𝗖𝗿𝗮𝗰𝗸 PSN 𝗖𝗿𝗮𝗰𝗸 Account COD Mobile =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 𝗠𝘆 𝗖𝗵𝗮𝗻𝗻𝗲𝗹: 1# @Trust_Golden 2# @Trust_crack_codm 3# @general_psn [ @CODM_Centeer ] 4# @G0LDEN_Crack 5# @bank_hack 6# @CraCking_Farsi 7# @DarkStay 8# @Ninja_Crack 9# @PowerCodes 10# @Iraniancrack 11# @NG_RDP 12# @SellHub 13# @i…
Channel created
Showing the 2 most recent of 2 posts we hold for @Golden_Squad_INFO. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@Golden_Squad_INFO named 18 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“ǤØĿÐЄИ $ҨЦÂД (@Golden_Squad_INFO), 22 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Golden_Squad_INFO.
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.