Telegram RegisterThe public register of Telegram
Telegram profile photo for Надежные диспетчеры (Москва, работа, подработка, грузчик)

Supergroup

Надежные диспетчеры (Москва, работа, подработка, грузчик)

@nadezhny_disp

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

5,264members

+1,501 since we began measuring on 7 August 2026

178 online right now

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

Register entry

Telegram ID-1003653213763
TypeSupergroup
Username@nadezhny_disp
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live3 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/nadezhny_disp

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

3,7635,2704,516.57 August 2026 — 3,763 members8 August 2026 — 3,780 members11 August 2026 — 3,809 members14 August 2026 — 3,938 members17 August 2026 — 4,025 members20 August 2026 — 4,196 members24 August 2026 — 4,308 members27 August 2026 — 4,388 members30 August 2026 — 4,455 members2 September 2026 — 4,524 members3 September 2026 — 4,524 members8 September 2026 — 4,682 members12 September 2026 — 4,794 members16 September 2026 — 4,852 members30 September 2026 — 5,067 members7 October 2026 — 5,128 members13 October 2026 — 5,173 members19 October 2026 — 5,148 members22 October 2026 — 5,219 members25 October 2026 — 5,205 members28 October 2026 — 5,238 members30 October 2026 — 5,270 members3 November 2026 — 5,264 members5,2647 August 20263 November 2026
23 measurements spanning 87 days, net +1,501. 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 3,537–5,496 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
3 Nov 2026, 03:145,264-6
30 Oct 2026, 19:065,270+32
28 Oct 2026, 01:485,238+33
25 Oct 2026, 12:065,205-14
22 Oct 2026, 18:375,219+71
19 Oct 2026, 22:365,148-25
13 Oct 2026, 12:165,173+45
7 Oct 2026, 00:575,128+61
30 Sept 2026, 07:365,067+215
16 Sept 2026, 07:414,852+58
12 Sept 2026, 06:024,794+112
8 Sept 2026, 02:594,682+158
3 Sept 2026, 12:244,524no change
2 Sept 2026, 14:084,524+69
30 Aug 2026, 22:154,455+67
27 Aug 2026, 15:174,388+80
24 Aug 2026, 10:394,308+112
20 Aug 2026, 20:124,196+171
17 Aug 2026, 20:434,025+87
14 Aug 2026, 21:473,938first 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“Надежные диспетчеры (Москва, работа, подработка, грузчик)” (@nadezhny_disp), 5,264 members as measured 3 November 2026. Telegram Register, tgregister.com/channel/nadezhny_disp.

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.