Telegram RegisterThe public register of Telegram
Telegram profile photo for МУП Будва | Инфо и помощь

Supergroup

МУП Будва | Инфо и помощь

@mup_budva

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

2,970members

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

83 online right now

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

Register entry

Telegram ID-1004292534350
TypeSupergroup
Username@mup_budva
CreatedBetween 1 May 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 October 2026
Last confirmed live29 October 2026
Measurements held15
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/mup_budva

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 94% 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

1022,9701,5367 August 2026 — 102 members15 August 2026 — 110 members23 August 2026 — 121 members30 August 2026 — 643 members9 September 2026 — 686 members18 September 2026 — 711 members3 October 2026 — 2,115 members3 October 2026 — 2,115 members9 October 2026 — 2,016 members14 October 2026 — 1,850 members16 October 2026 — 1,858 members19 October 2026 — 1,865 members22 October 2026 — 1,879 members26 October 2026 — 1,880 members29 October 2026 — 2,970 members7 August 202629 October 2026
15 measurements spanning 83 days, net +2,868. 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”.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
29 Oct 2026, 10:102,970+1,090
26 Oct 2026, 00:161,880+1
22 Oct 2026, 18:111,879+14
19 Oct 2026, 09:561,865+7
16 Oct 2026, 15:591,858+8
14 Oct 2026, 02:401,850-166
9 Oct 2026, 15:172,016-99
3 Oct 2026, 17:052,115no change
3 Oct 2026, 11:362,115+1,404
18 Sept 2026, 15:02711+25
9 Sept 2026, 15:20686+43
30 Aug 2026, 22:07643+522
23 Aug 2026, 14:37121+11
15 Aug 2026, 15:56110+8
7 Aug 2026, 14:17102first 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“МУП Будва | Инфо и помощь” (@mup_budva), 2,970 members as measured 29 October 2026. Telegram Register, tgregister.com/channel/mup_budva.

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.