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

Channel

Laravel World

@laravel_it

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

7,975subscribers

-34 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001276220555
TypeChannel
Username@laravel_it
DescriptionНовости о Laravel и PHP. Уроки и секреты.
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/laravel_it

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

7,9238,0097,9666 August 2026 — 8,009 subscribers7 August 2026 — 8,008 subscribers10 August 2026 — 8,002 subscribers13 August 2026 — 8,007 subscribers17 August 2026 — 7,995 subscribers20 August 2026 — 7,994 subscribers23 August 2026 — 7,988 subscribers26 August 2026 — 7,978 subscribers30 August 2026 — 7,974 subscribers6 September 2026 — 7,971 subscribers11 September 2026 — 7,967 subscribers15 September 2026 — 7,959 subscribers19 September 2026 — 7,947 subscribers29 September 2026 — 7,932 subscribers6 October 2026 — 7,924 subscribers12 October 2026 — 7,927 subscribers15 October 2026 — 7,925 subscribers17 October 2026 — 7,923 subscribers21 October 2026 — 7,926 subscribers24 October 2026 — 7,990 subscribers27 October 2026 — 7,994 subscribers1 November 2026 — 7,992 subscribers5 November 2026 — 7,980 subscribers8 November 2026 — 7,982 subscribers12 November 2026 — 7,975 subscribers7,9756 August 202612 November 2026
25 measurements spanning 98 days, net -34. 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 7,910–8,022 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
12 Nov 2026, 14:507,975-7
8 Nov 2026, 12:517,982+2
5 Nov 2026, 08:297,980-12
1 Nov 2026, 21:257,992-2
27 Oct 2026, 13:157,994+4
24 Oct 2026, 03:457,990+64
21 Oct 2026, 03:487,926+3
17 Oct 2026, 23:287,923-2
15 Oct 2026, 07:567,925-2
12 Oct 2026, 13:107,927+3
6 Oct 2026, 07:007,924-8
29 Sept 2026, 08:177,932-15
19 Sept 2026, 16:207,947-12
15 Sept 2026, 02:587,959-8
11 Sept 2026, 02:017,967-4
6 Sept 2026, 13:377,971-3
30 Aug 2026, 05:097,974-4
26 Aug 2026, 19:557,978-10
23 Aug 2026, 23:597,988-6
20 Aug 2026, 05:177,994first reading

Engagement

50 posts held, back to 28 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 47 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
70.1%
avg views ÷ 7,975 subscribers
Avg views / post
5,590
17 posts measured
Reaction rate
0.732%
reactions ÷ views · ER floor
Posts in window
17
of 50 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held50 (28 May 2026 – 16 November 2026)
Views total95,080
Reactions total696
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 03:37 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈1,400
Videos
≈34
Links
≈2,240

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
30s
Average length
30s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

1,781 reactions across 50 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,781100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 50 of the 50 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1,781 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 50 most recent posts we hold, published 28 May 2026 to 16 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
7
across the posts below
Posts paid on
5
of 50 we hold a reading for · 10%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @laravel_it. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 50 most recent posts we hold for this entry, published 28 May 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 4 of 17 posts held from the last 30 days (23.5%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 07:05 UTC≈2,550 views36 reactionsread 17 November 2026

Модели искусственного интеллекта ненавидят Python и любят PHP https://blog.jetbrains.com/ai/2026/11/ai-models-hate-python-and-love-php-we-asked-12-of-them-1-200-times/

❤36

9 Nov 2026, 07:05 UTC≈4,470 views25 reactionsread 17 November 2026
Video

PHP Debugger — облегчённая альтернатива Xdebug с поддержкой AI-агентов Разработчики представили PHP Debugger — бесплатный open-source отладчик PHP, созданный на основе Xdebug. Главная цель проекта — обеспечить полноценную пошаговую отладку с минимальными накладными расходами. Высокая производительность — отладчик можно держать постоянно активным, даже когда IDE не подключена. В тестах авторов на Symfony накладные р…

❤25

6 Nov 2026, 07:05 UTC≈4,500 views38 reactionsread 17 November 2026
Photo

Вышел PhpStorm 2026.3 JetBrains выпустила третье крупное обновление PhpStorm в этом году. Основной акцент — на работе с AI-агентами, PHP 8.6, Laravel и удалённой разработке. JetBrains Air — единое пространство для работы с Claude Code, Codex, Gemini, Copilot, OpenCode и другими агентами. Можно использовать существующие подписки и API-ключи без JetBrains AI. Доступен бесплатный Junie Lite. Изменения агентов можно пр…

❤38

5 Nov 2026, 10:46 UTC≈5,280 views73 reactionsread 17 November 2026
Photo

Flock 1.0 — бесплатное окружение для PHP-разработки Состоялся первый стабильный релиз Flock — open-source инструмента для локальной разработки на PHP и Laravel. Работает на Windows, macOS и Linux без Docker, WSL и виртуальных машин. Основные возможности: - PHP 8.1–8.5 и Node.js — несколько версий одновременно, индивидуальные настройки для каждого проекта. - Автоматические домены и HTTPS — адреса вида project.test, …

❤73

3 Nov 2026, 07:05 UTC≈3,950 views50 reactionsread 17 November 2026

Inertia.js получила Live Props — реактивные данные без ручной работы с WebSocket Тейлор представил одно из самых интересных обновлений Inertia.js 3 за последнее время — Live Props. Они позволяют автоматически обновлять данные на странице при получении событий от сервера, без перезагрузки страницы и постоянного polling. Вместе с этим в последних релизах появилось ещё несколько полезных возможностей. 1. Live Props — …

❤50

2 Nov 2026, 07:05 UTC≈4,250 views64 reactionsread 17 November 2026
Photo

Elephc: PHP-код может работать в десятки и сотни раз быстрее Разработчики компилятора Elephc продолжают оптимизировать преобразование PHP в нативный машинный код. В новом PR улучшена работа с массивами, циклами, строками и встроенными функциями. В отдельных синтетических тестах ускорение достигает сотен раз по сравнению с обычным PHP. Пока Elephc не готов заменить PHP в Laravel и других крупных фреймворках. Но перс…

❤64

1 Nov 2026, 08:05 UTC≈4,510 views32 reactionsread 17 November 2026
Photo

Вышел Composer 2.11 Главное нововведение — механизм cooldown, позволяющий откладывать установку новых версий пакетов на заданное время (например, 24 часа). Это снижает риск атак через скомпрометированные зависимости. По умолчанию функция отключена. Также исправлен ряд уязвимостей безопасности, включая утечку токенов в composer.lock, ускорено разрешение зависимостей, снижено потребление памяти и убран автоматический…

❤32

23 Oct 2026, 12:54 UTC≈7,430 views20 reactionsread 17 November 2026
Photo

PHP: разработчики предупредили о дополнительном сценарии RCE (CVE-2026-115560). Уязвимость проявляется при редком сочетании настроек: приложение должно переключать session.serialize_handler с php_binary или php_serialize на php во время выполнения, при включённом session.upload_progress. До выхода следующего релиза PHP рекомендуется установить session.upload_progress.enabled=0. Если настройка уже отключена после пр…

❤20

22 Oct 2026, 09:09 UTC≈7,980 views110 reactionsread 17 November 2026
Photo

Ondřej Surý выпустил обновлённые пакеты PHP с исправлениями критических уязвимостей для всех веток, представленных в его репозитории, включая устаревшие и официально не поддерживаемые версии вплоть до PHP 5.6. Обновления распространяются через репозитории Sury для Debian и Ubuntu.

❤110

21 Oct 2026, 16:18 UTC≈8,590 views19 reactionsread 17 November 2026

Node.js сегодня закрыл 4 уязвимости высокой степени опасности Самая серьёзная, CVE-2026-111497, находится в декодере Brotli и, по словам Node.js, позволяет выполнять код удалённо. Две ошибки позволяли обойти проверку имени хоста в TLS. Ваше приложение может принять за действительный сертификат, который не принадлежит серверу, с которым оно общается. Если у вас есть что-то на Node.js: ➡️ Выполните node -v. Если ве…

❤19

21 Oct 2026, 15:00 UTC≈5,610 views22 reactionsread 17 November 2026
Photo

PHP2Shell: Искусственный интеллект обнаружил критические уязвимости удаленного выполнения (RCE), затрагивающие 70% интернета Статья непосредственно от исследователей, обнаруживших уязвимости. Технический разбор четырёх ошибок управления памятью в ядре PHP, которые исследователи объединили под названием PHP2Shell. Ошибки существовали более десяти лет, но их было чрезвычайно сложно превратить в работающий эксплойт. Ис…

❤22

21 Oct 2026, 14:06 UTC≈5,340 views32 reactionsread 17 November 2026
Photo

Вышли пропатченные версии PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12 https://www.php.net/archive/2026.php#2026-10-21-5

❤32

Showing the 12 most recent of 50 posts we hold for @laravel_it. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Timeweb Cloud Alerts
@timewebcloud_alerts · 25,846
Telegram ranks this channel #25 of 87 here — alongside 86 others — read 9 September 2026
Веб-страница
@tproger_web · 22,132
Telegram ranks this channel #64 of 96 here — alongside 95 others — read 20 September 2026
Golang
@Golang_google · 40,420
Telegram ranks this channel #73 of 90 here — alongside 89 others — read 30 August 2026
Библиотека Go-разработчика | Golang
@goproglib · 23,889
Telegram ranks this channel #81 of 91 here — alongside 90 others — read 17 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Laravel World” (@laravel_it), 7,975 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/laravel_it.

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.