Telegram RegisterThe public register of Telegram
Telegram profile photo for Laravel Pro

Supergroup

Laravel Pro

@laravel_pro

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

4,123members

+128 since we began measuring on 6 August 2026

1,034 online right now

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

Register entry

Telegram ID-1001067453809
TypeSupergroup
Username@laravel_pro
CreatedBetween 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live17 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/laravel_pro

Topic

Technology — 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 66% 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,9954,1234,0596 August 2026 — 3,995 members9 August 2026 — 3,999 members12 August 2026 — 4,011 members16 August 2026 — 4,019 members19 August 2026 — 4,030 members22 August 2026 — 4,098 members25 August 2026 — 4,096 members28 August 2026 — 4,088 members31 August 2026 — 4,091 members3 September 2026 — 4,107 members4 September 2026 — 4,107 members8 September 2026 — 4,102 members13 September 2026 — 4,105 members17 September 2026 — 4,123 members6 August 202617 September 2026
14 measurements spanning 42 days, net +128. 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,976–4,142 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
17 Sept 2026, 06:224,123+18
13 Sept 2026, 01:554,105+3
8 Sept 2026, 16:364,102-5
4 Sept 2026, 23:334,107no change
3 Sept 2026, 09:554,107+16
31 Aug 2026, 05:134,091+3
28 Aug 2026, 14:134,088-8
25 Aug 2026, 14:254,096-2
22 Aug 2026, 04:254,098+68
19 Aug 2026, 06:024,030+11
16 Aug 2026, 03:344,019+8
12 Aug 2026, 17:334,011+12
9 Aug 2026, 12:413,999+4
6 Aug 2026, 10:593,995first 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Laravel Pro” (@laravel_pro), 4,123 members as measured 17 September 2026. Telegram Register, tgregister.com/channel/laravel_pro.

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.