Telegram RegisterThe public register of Telegram
Telegram profile photo for Грузчики 22-Барнаул

Supergroup

Грузчики 22-Барнаул

@gruz2222

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

9,112members

+2,457 since we began measuring on 7 August 2026

5 online right now

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

Register entry

Telegram ID-1001356953858
TypeSupergroup
Username@gruz2222
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live1 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/gruz2222

Topic

Job listings — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 the other topics.

Growth

6,6559,1127,883.57 August 2026 — 6,655 members8 August 2026 — 6,660 members11 August 2026 — 6,737 members15 August 2026 — 6,844 members17 August 2026 — 6,916 members20 August 2026 — 7,029 members23 August 2026 — 7,126 members26 August 2026 — 7,223 members26 August 2026 — 7,223 members29 August 2026 — 7,327 members1 September 2026 — 7,373 members4 September 2026 — 7,491 members9 September 2026 — 7,631 members13 September 2026 — 7,708 members16 September 2026 — 7,785 members25 September 2026 — 8,021 members4 October 2026 — 8,522 members11 October 2026 — 8,727 members14 October 2026 — 8,808 members17 October 2026 — 8,875 members20 October 2026 — 8,918 members23 October 2026 — 9,027 members26 October 2026 — 9,011 members29 October 2026 — 9,093 members1 November 2026 — 9,112 members7 August 20261 November 2026
25 measurements spanning 85 days, net +2,457. 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 6,286–9,481 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
1 Nov 2026, 05:199,112+19
29 Oct 2026, 11:509,093+82
26 Oct 2026, 12:409,011-16
23 Oct 2026, 14:579,027+109
20 Oct 2026, 11:398,918+43
17 Oct 2026, 01:498,875+67
14 Oct 2026, 10:048,808+81
11 Oct 2026, 04:378,727+205
4 Oct 2026, 22:178,522+501
25 Sept 2026, 05:388,021+236
16 Sept 2026, 18:027,785+77
13 Sept 2026, 05:197,708+77
9 Sept 2026, 12:567,631+140
4 Sept 2026, 08:207,491+118
1 Sept 2026, 07:467,373+46
29 Aug 2026, 12:047,327+104
26 Aug 2026, 21:487,223no change
26 Aug 2026, 15:547,223+97
23 Aug 2026, 23:447,126+97
20 Aug 2026, 10:267,029first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 1 November 2026 — this entry's latest reading, not the date you are reading this.

“Грузчики 22-Барнаул” (@gruz2222), 9,112 members as measured 1 November 2026. Telegram Register, tgregister.com/channel/gruz2222.

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.