Telegram RegisterThe public register of Telegram
Telegram profile photo for CODM Config File 2024

Channel

CODM Config File 2024

@codmconfigfile

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

13,256subscribers

-97 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002269282361
TypeChannel
Username@codmconfigfile
Created14 October 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held22
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/codmconfigfile

Growth

13,25113,35313,3027 August 2026 — 13,353 subscribers7 August 2026 — 13,353 subscribers8 August 2026 — 13,351 subscribers9 August 2026 — 13,352 subscribers10 August 2026 — 13,344 subscribers11 August 2026 — 13,340 subscribers13 August 2026 — 13,331 subscribers14 August 2026 — 13,333 subscribers16 August 2026 — 13,327 subscribers17 August 2026 — 13,318 subscribers18 August 2026 — 13,314 subscribers19 August 2026 — 13,306 subscribers20 August 2026 — 13,309 subscribers21 August 2026 — 13,298 subscribers22 August 2026 — 13,295 subscribers24 August 2026 — 13,285 subscribers25 August 2026 — 13,268 subscribers26 August 2026 — 13,260 subscribers27 August 2026 — 13,251 subscribers28 August 2026 — 13,255 subscribers29 August 2026 — 13,258 subscribers30 August 2026 — 13,256 subscribers13,2567 August 202630 August 2026
22 measurements spanning 22 days, net -97. 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 13,236–13,368 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
30 Aug 2026, 03:2513,256-2
29 Aug 2026, 05:5313,258+3
28 Aug 2026, 09:0613,255+4
27 Aug 2026, 10:1213,251-9
26 Aug 2026, 10:3413,260-8
25 Aug 2026, 11:3813,268-17
24 Aug 2026, 14:0413,285-10
22 Aug 2026, 18:2613,295-3
21 Aug 2026, 07:0713,298-11
20 Aug 2026, 09:1513,309+3
19 Aug 2026, 10:1213,306-8
18 Aug 2026, 11:4713,314-4
17 Aug 2026, 15:0613,318-9
16 Aug 2026, 05:1613,327-6
14 Aug 2026, 14:1313,333+2
13 Aug 2026, 01:5813,331-9
11 Aug 2026, 04:3113,340-4
10 Aug 2026, 07:1513,344-8
9 Aug 2026, 04:1113,352+1
8 Aug 2026, 07:0013,351first reading

Engagement

1 post held, back to 14 October 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 42 pagesof 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 14 October 2024. 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 @codmconfigfile. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“CODM Config File 2024” (@codmconfigfile), 13,256 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/codmconfigfile.

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.