Telegram RegisterThe public register of Telegram
Telegram profile photo for LPM ROBLOX

Supergroup

LPM ROBLOX

@lpm_mabar_roblox

2 usernames

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

3,949members

-57 since we began measuring on 7 August 2026

354 online right now

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

Register entry

Telegram ID-1003246707425
TypeSupergroup
Usernames@grub_mabar @lpm_mabar_roblox
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live11 October 2026
Measurements held23
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/lpm_mabar_roblox

Topic

Gaming — 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 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 why it has no browse page of its own yet.

Growth

3,9464,1334,039.57 August 2026 — 4,006 members8 August 2026 — 4,012 members11 August 2026 — 4,041 members15 August 2026 — 4,058 members18 August 2026 — 4,035 members21 August 2026 — 4,053 members24 August 2026 — 3,968 members28 August 2026 — 4,009 members31 August 2026 — 4,108 members3 September 2026 — 4,133 members4 September 2026 — 4,133 members7 September 2026 — 4,126 members8 September 2026 — 4,132 members11 September 2026 — 4,125 members13 September 2026 — 4,128 members15 September 2026 — 4,090 members17 September 2026 — 4,067 members24 September 2026 — 4,027 members25 September 2026 — 4,022 members4 October 2026 — 4,005 members4 October 2026 — 4,003 members11 October 2026 — 3,946 members11 October 2026 — 3,949 members3,9497 August 202611 October 2026
23 measurements spanning 65 days, net -57. 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,918–4,161 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
11 Oct 2026, 13:593,949+3
11 Oct 2026, 09:393,946-57
4 Oct 2026, 23:584,003-2
4 Oct 2026, 20:404,005-17
25 Sept 2026, 22:194,022-5
24 Sept 2026, 23:164,027-40
17 Sept 2026, 00:584,067-23
15 Sept 2026, 07:154,090-38
13 Sept 2026, 02:014,128+3
11 Sept 2026, 22:194,125-7
8 Sept 2026, 19:584,132+6
7 Sept 2026, 22:164,126-7
4 Sept 2026, 23:084,133no change
3 Sept 2026, 17:564,133+25
31 Aug 2026, 09:124,108+99
28 Aug 2026, 02:084,009+41
24 Aug 2026, 19:243,968-85
21 Aug 2026, 08:024,053+18
18 Aug 2026, 08:124,035-23
15 Aug 2026, 04:144,058first 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 11 October 2026 — this entry's latest reading, not the date you are reading this.

“LPM ROBLOX” (@lpm_mabar_roblox), 3,949 members as measured 11 October 2026. Telegram Register, tgregister.com/channel/lpm_mabar_roblox.

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.