Telegram RegisterThe public register of Telegram
Telegram profile photo for ///>>>CodezVII<<<///

Channel

///>>>CodezVII<<<///

@CodezVII

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

21,763subscribers

-464 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001189579274
TypeChannel
Username@CodezVII
Created6 June 2021measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live5 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/CodezVII

Growth

21,76322,22721,9956 August 2026 — 22,227 subscribers6 August 2026 — 22,227 subscribers6 August 2026 — 22,225 subscribers7 August 2026 — 22,213 subscribers8 August 2026 — 22,195 subscribers9 August 2026 — 22,176 subscribers10 August 2026 — 22,154 subscribers11 August 2026 — 22,133 subscribers12 August 2026 — 22,123 subscribers14 August 2026 — 22,105 subscribers15 August 2026 — 22,080 subscribers16 August 2026 — 22,056 subscribers17 August 2026 — 22,034 subscribers18 August 2026 — 22,022 subscribers19 August 2026 — 22,009 subscribers20 August 2026 — 21,985 subscribers22 August 2026 — 21,960 subscribers24 August 2026 — 21,927 subscribers25 August 2026 — 21,910 subscribers26 August 2026 — 21,898 subscribers27 August 2026 — 21,886 subscribers28 August 2026 — 21,869 subscribers29 August 2026 — 21,862 subscribers30 August 2026 — 21,846 subscribers31 August 2026 — 21,833 subscribers1 September 2026 — 21,819 subscribers2 September 2026 — 21,804 subscribers3 September 2026 — 21,788 subscribers5 September 2026 — 21,763 subscribers6 August 20265 September 2026
29 measurements spanning 30 days, net -464. 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 21,693–22,297 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
5 Sept 2026, 08:1621,763-25
3 Sept 2026, 09:1421,788-16
2 Sept 2026, 04:1621,804-15
1 Sept 2026, 00:4821,819-14
31 Aug 2026, 00:4521,833-13
30 Aug 2026, 03:3421,846-16
29 Aug 2026, 04:3621,862-7
28 Aug 2026, 06:3321,869-17
27 Aug 2026, 04:2821,886-12
26 Aug 2026, 05:1221,898-12
25 Aug 2026, 08:1621,910-17
24 Aug 2026, 06:3521,927-33
22 Aug 2026, 11:1621,960-25
20 Aug 2026, 22:2821,985-24
19 Aug 2026, 21:5822,009-13
18 Aug 2026, 21:3422,022-12
17 Aug 2026, 20:4422,034-22
16 Aug 2026, 20:2822,056-24
15 Aug 2026, 10:2922,080-25
14 Aug 2026, 03:1722,105first reading

Engagement

1 post held, back to 6 June 2021the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 58 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 1 post for this entry, the most recent from 6 June 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 1 most recent of 1 post we hold for @CodezVII. 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

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

“///>>>CodezVII<<<///” (@CodezVII), 21,763 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/CodezVII.

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.