Telegram RegisterThe public register of Telegram
Telegram profile photo for 💸 сплетни Москвы

Channel

💸 сплетни Москвы

@spletni_moscow1

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

6,253subscribers

+577 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002804492627
TypeChannel
Username@spletni_moscow1
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live1 November 2026
Measurements held22
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/spletni_moscow1

Topic

Memes & entertainment — 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 90% 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

5,6766,2535,964.57 August 2026 — 5,676 subscribers11 August 2026 — 5,733 subscribers14 August 2026 — 5,749 subscribers17 August 2026 — 5,788 subscribers21 August 2026 — 5,809 subscribers24 August 2026 — 5,836 subscribers27 August 2026 — 5,870 subscribers29 August 2026 — 5,870 subscribers31 August 2026 — 5,892 subscribers3 September 2026 — 5,905 subscribers8 September 2026 — 5,967 subscribers12 September 2026 — 5,993 subscribers16 September 2026 — 6,031 subscribers2 October 2026 — 6,127 subscribers8 October 2026 — 6,181 subscribers13 October 2026 — 6,235 subscribers17 October 2026 — 6,234 subscribers20 October 2026 — 6,227 subscribers22 October 2026 — 6,229 subscribers26 October 2026 — 6,221 subscribers29 October 2026 — 6,227 subscribers1 November 2026 — 6,253 subscribers7 August 20261 November 2026
22 measurements spanning 85 days, net +577. 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 5,589–6,340 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
1 Nov 2026, 00:286,253+26
29 Oct 2026, 06:116,227+6
26 Oct 2026, 03:116,221-8
22 Oct 2026, 23:586,229+2
20 Oct 2026, 02:306,227-7
17 Oct 2026, 06:556,234-1
13 Oct 2026, 21:586,235+54
8 Oct 2026, 20:356,181+54
2 Oct 2026, 00:416,127+96
16 Sept 2026, 07:216,031+38
12 Sept 2026, 12:215,993+26
8 Sept 2026, 10:195,967+62
3 Sept 2026, 12:395,905+13
31 Aug 2026, 05:045,892+22
29 Aug 2026, 22:205,870no change
27 Aug 2026, 22:335,870+34
24 Aug 2026, 14:475,836+27
21 Aug 2026, 01:345,809+21
17 Aug 2026, 16:575,788+39
14 Aug 2026, 16:235,749first 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.

“💸 сплетни Москвы” (@spletni_moscow1), 6,253 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/spletni_moscow1.

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.