Telegram RegisterThe public register of Telegram
Telegram profile photo for Севастополь чат

Supergroup

Севастополь чат

@sevastopolchat1

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

9,092members

-695 since we began measuring on 7 August 2026

247 online right now

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

Register entry

Telegram ID-1001373895412
TypeSupergroup
Username@sevastopolchat1
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live25 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 25 October 2026
On Telegramt.me/sevastopolchat1

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

8,8719,8049,337.57 August 2026 — 9,787 members8 August 2026 — 9,774 members10 August 2026 — 9,752 members14 August 2026 — 9,804 members17 August 2026 — 9,670 members21 August 2026 — 9,666 members23 August 2026 — 9,666 members24 August 2026 — 9,615 members28 August 2026 — 9,498 members31 August 2026 — 9,457 members3 September 2026 — 9,429 members8 September 2026 — 9,557 members12 September 2026 — 9,581 members16 September 2026 — 9,569 members30 September 2026 — 9,468 members7 October 2026 — 9,186 members13 October 2026 — 9,017 members16 October 2026 — 8,935 members19 October 2026 — 8,889 members22 October 2026 — 8,871 members25 October 2026 — 9,092 members9,0927 August 202625 October 2026
21 measurements spanning 79 days, net -695. 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 8,731–9,944 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 21
Measured (UTC)MembersChange
25 Oct 2026, 08:569,092+221
22 Oct 2026, 12:268,871-18
19 Oct 2026, 10:098,889-46
16 Oct 2026, 20:388,935-82
13 Oct 2026, 13:059,017-169
7 Oct 2026, 20:189,186-282
30 Sept 2026, 21:179,468-101
16 Sept 2026, 11:419,569-12
12 Sept 2026, 06:209,581+24
8 Sept 2026, 00:189,557+128
3 Sept 2026, 07:399,429-28
31 Aug 2026, 05:259,457-41
28 Aug 2026, 08:239,498-117
24 Aug 2026, 23:349,615-51
23 Aug 2026, 11:239,666no change
21 Aug 2026, 05:389,666-4
17 Aug 2026, 19:349,670-134
14 Aug 2026, 08:159,804+52
10 Aug 2026, 20:589,752-22
8 Aug 2026, 05:559,774first reading

Engagement

No public post preview. We read this entry on 23 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.

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 25 October 2026 — this entry's latest reading, not the date you are reading this.

“Севастополь чат” (@sevastopolchat1), 9,092 members as measured 25 October 2026. Telegram Register, tgregister.com/channel/sevastopolchat1.

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.