Telegram RegisterThe public register of Telegram
Telegram profile photo for Горящие туры Волгоград

Supergroup

Горящие туры Волгоград

@turyvolgograd

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

1,101members

-39 since we began measuring on 7 August 2026

79 online right now

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

Register entry

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

Topic

Travel — 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 6 October 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

1,0971,1411,1197 August 2026 — 1,140 members7 August 2026 — 1,141 members11 August 2026 — 1,134 members14 August 2026 — 1,125 members17 August 2026 — 1,123 members20 August 2026 — 1,116 members24 August 2026 — 1,118 members27 August 2026 — 1,120 members30 August 2026 — 1,117 members2 September 2026 — 1,111 members5 September 2026 — 1,106 members10 September 2026 — 1,102 members14 September 2026 — 1,097 members19 September 2026 — 1,101 members28 September 2026 — 1,106 members5 October 2026 — 1,115 members6 October 2026 — 1,115 members12 October 2026 — 1,110 members15 October 2026 — 1,109 members19 October 2026 — 1,108 members22 October 2026 — 1,107 members27 October 2026 — 1,106 members30 October 2026 — 1,104 members2 November 2026 — 1,100 members5 November 2026 — 1,101 members1,1017 August 20265 November 2026
25 measurements spanning 90 days, net -39. 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 1,090–1,148 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
5 Nov 2026, 09:591,101+1
2 Nov 2026, 14:461,100-4
30 Oct 2026, 20:361,104-2
27 Oct 2026, 23:271,106-1
22 Oct 2026, 03:101,107-1
19 Oct 2026, 03:371,108-1
15 Oct 2026, 21:061,109-1
12 Oct 2026, 12:091,110-5
6 Oct 2026, 05:211,115no change
5 Oct 2026, 20:001,115+9
28 Sept 2026, 10:591,106+5
19 Sept 2026, 03:571,101+4
14 Sept 2026, 19:371,097-5
10 Sept 2026, 20:561,102-4
5 Sept 2026, 22:181,106-5
2 Sept 2026, 02:551,111-6
30 Aug 2026, 04:041,117-3
27 Aug 2026, 12:361,120+2
24 Aug 2026, 09:111,118+2
20 Aug 2026, 15:591,116first 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“Горящие туры Волгоград” (@turyvolgograd), 1,101 members as measured 5 November 2026. Telegram Register, tgregister.com/channel/turyvolgograd.

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.