Telegram RegisterThe public register of Telegram

Channel

Web Development

@webde

Has discussion group2 usernames

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

32,145subscribers

-52 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001036339066
TypeChannel
Usernames@webde @webdel
Created4 March 2016measured — dated from the channel’s first post
First recorded5 August 2026
Last confirmed live13 August 2026
Measurements held13
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/webde

Growth

32,14532,19732,1715 August 2026 — 32,197 subscribers6 August 2026 — 32,196 subscribers7 August 2026 — 32,189 subscribers8 August 2026 — 32,191 subscribers9 August 2026 — 32,188 subscribers10 August 2026 — 32,178 subscribers10 August 2026 — 32,173 subscribers11 August 2026 — 32,167 subscribers11 August 2026 — 32,161 subscribers12 August 2026 — 32,158 subscribers12 August 2026 — 32,152 subscribers13 August 2026 — 32,146 subscribers13 August 2026 — 32,145 subscribers5 August 202613 August 2026
13 measurements spanning 8 days, net -52. 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 32,137–32,205 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:1632,145-1
13 Aug 2026, 04:5532,146-6
12 Aug 2026, 09:4632,152-6
12 Aug 2026, 02:3232,158-3
11 Aug 2026, 07:1632,161-6
11 Aug 2026, 05:1132,167-6
10 Aug 2026, 10:0732,173-5
10 Aug 2026, 02:5132,178-10
9 Aug 2026, 16:1732,188-3
8 Aug 2026, 06:1332,191+2
7 Aug 2026, 05:2032,189-7
6 Aug 2026, 07:5132,196-1
5 Aug 2026, 18:1832,197first reading

Engagement

1,663 posts held, back to 4 March 2016the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 186 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
4.11%
avg views ÷ 32,145 subscribers
Avg views / post
1,320
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 1,663 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 9 August 2026
Posts held1,663 (4 March 20169 August 2026)
Views total1,320
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 09:57 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.

Recent posts

9 Aug 2026, 19:55 UTC≈1,320 viewsread 13 August 2026
Photo

Announcing TanStack Table V9 #tanstack Read more

22 Jun 2026, 13:15 UTC≈5,700 viewsread 13 August 2026
Photo

Flow for TypeScript Users in 2026 #ts #typescript #flow Read more

16 May 2026, 19:56 UTC≈8,360 viewsread 13 August 2026
Photo

React Review: Audit Your Codebase for Bad React Code From the creator of React Doctor comes a new GitHub App (powered by React Doctor) that fetches both a pull request branch and base branch and reviews and reports on issues introduced in the PR. #react #review #performance #audit Read more

2 May 2026, 13:15 UTC≈8,060 viewsread 13 August 2026
Photo

TypeScript 7.0 Beta: 10x Faster TypeScript Compilation The Go-powered port with “about 10 times faster” compiler performance. TypeScript 6.0's deprecations and config changes will help you upgrade smoothly from v5 to v7. There are also changes to how to write your code to review. While v7 is considered "close to production-ready", a stable programmatic API won't arrive till v7.1. Read more

30 Apr 2026, 13:15 UTC≈6,760 viewsread 13 August 2026
Photo

pnpm 11.0 Released You’ve heard about its benefits, but now the popular package management tool is even better. v11 sets minimumReleaseAge to one day by default, there's an SQLite-backed store index (faster installs!), native package publishing, pack-app, and more. There's a migration guide for v10 users. Work has also resumed on a Rust-powered port called Pacquet. #pnpm Read more

28 Apr 2026, 10:17 UTC≈5,890 viewsread 13 August 2026
Video

How to Use Lazy Loading Without Hurting Web Performance 🚀 Lazy loading delays non-critical content (like images) to speed up initial page load. ⚠️ But overusing it, especially on important, above-the-fold elements, can hurt performance and user experience. 👉 Use it selectively: load key content immediately, lazy load the rest. #performance Read more

24 Apr 2026, 13:15 UTC≈5,700 viewsread 13 August 2026
Photo

What's New in VisionCamera V5? #reactnative #package #library Read more

22 Apr 2026, 13:15 UTC≈5,860 viewsread 13 August 2026
Photo

Introducing Claude Design by Anthropic Labs #design #claude #llm Read more

13 Apr 2026, 13:15 UTC≈6,530 viewsread 13 August 2026
Photo

React Color: Flexible Color Picker Components #package #lib #react Read more

8 Apr 2026, 10:49 UTC≈7,310 viewsread 13 August 2026
Photo

What To Know in JavaScript (2026 Edition) #js #javascript Read more

Showing the 12 most recent of 1,663 posts we hold for @webde. 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.

Citation-graph rank

Citation-graph rank — 433,930 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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.

Computer Science and Programming
@computer_science_and_programming · 140,958
Telegram ranks this channel #6 of 87 here — alongside 86 others — read 13 August 2026
Web Development
@webdev_trainings · 133,957
Telegram ranks this channel #25 of 65 here — alongside 64 others — read 13 August 2026
TheSanskaarSingh
@codeslearningTG · 269,931
Telegram ranks this channel #42 of 84 here — alongside 83 others — read 11 August 2026

This channel appears in 3 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Web Development” (@webde), 32,145 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/webde.

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.