Telegram RegisterThe public register of Telegram
Telegram profile photo for Жесть Архангельской области

Channel

Жесть Архангельской области

@zgiest29

Has discussion group

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

40,119subscribers

+28 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001645624630
TypeChannel
Username@zgiest29
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live19 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/zgiest29

Topic

Local community — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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

40,02140,13240,076.56 August 2026 — 40,091 subscribers6 August 2026 — 40,081 subscribers7 August 2026 — 40,072 subscribers8 August 2026 — 40,067 subscribers9 August 2026 — 40,055 subscribers10 August 2026 — 40,045 subscribers11 August 2026 — 40,041 subscribers12 August 2026 — 40,036 subscribers12 August 2026 — 40,036 subscribers13 August 2026 — 40,027 subscribers15 August 2026 — 40,089 subscribers16 August 2026 — 40,114 subscribers17 August 2026 — 40,115 subscribers18 August 2026 — 40,113 subscribers19 August 2026 — 40,111 subscribers20 August 2026 — 40,081 subscribers21 August 2026 — 40,053 subscribers23 August 2026 — 40,065 subscribers24 August 2026 — 40,093 subscribers25 August 2026 — 40,094 subscribers26 August 2026 — 40,081 subscribers27 August 2026 — 40,075 subscribers28 August 2026 — 40,064 subscribers29 August 2026 — 40,043 subscribers30 August 2026 — 40,047 subscribers31 August 2026 — 40,045 subscribers2 September 2026 — 40,040 subscribers3 September 2026 — 40,029 subscribers5 September 2026 — 40,021 subscribers8 September 2026 — 40,060 subscribers11 September 2026 — 40,022 subscribers13 September 2026 — 40,132 subscribers14 September 2026 — 40,131 subscribers16 September 2026 — 40,123 subscribers19 September 2026 — 40,119 subscribers40,1196 August 202619 September 2026
35 measurements spanning 44 days, net +28. 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 40,004–40,149 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
19 Sept 2026, 01:2040,119-4
16 Sept 2026, 19:5640,123-8
14 Sept 2026, 23:4040,131-1
13 Sept 2026, 07:3940,132+110
11 Sept 2026, 09:2140,022-38
8 Sept 2026, 12:5940,060+39
5 Sept 2026, 09:1740,021-8
3 Sept 2026, 12:4140,029-11
2 Sept 2026, 05:3440,040-5
31 Aug 2026, 07:3740,045-2
30 Aug 2026, 07:2640,047+4
29 Aug 2026, 08:0540,043-21
28 Aug 2026, 08:1540,064-11
27 Aug 2026, 11:0740,075-6
26 Aug 2026, 12:5240,081-13
25 Aug 2026, 16:0240,094+1
24 Aug 2026, 18:0740,093+28
23 Aug 2026, 05:2440,065+12
21 Aug 2026, 20:1740,053-28
20 Aug 2026, 18:3840,081first reading

Engagement

No public post preview. We read this entry on 12 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

Mentions

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

“Жесть Архангельской области” (@zgiest29), 40,119 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/zgiest29.

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.