Channel

Chrome DevTools

@ChromeDevTools

On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

53subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID	-1001386647678
Type	Channel
Username	@ChromeDevTools
Created	Between 1 March 2018 and 11 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	10 August 2026
Last confirmed live	7 October 2026
Measurements held	4
Confirmed unchanged	3 times, most recently 7 October 2026
On Telegram	t.me/ChromeDevTools

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

Growth

4 measurements spanning 37 days, net -2. 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 53–55 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
13 Sept 2026, 10:16	53	-1
14 Aug 2026, 22:37	54	-1
10 Aug 2026, 08:15	55	no change
7 Aug 2026, 06:22	55	first reading

Engagement

20 posts held, back to 11 September 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 24 June 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Jun 2022, 04:48 UTC817 viewsread 10 August 2026

This channel will try to collect useful macros, aka recordings, for use with the Recorder tab in the Dev Tools of the Chrome browser. https://developer.chrome.com/docs/devtools/recorder/

22 Oct 2020, 15:39 UTC≈1,010 viewsread 10 August 2026

📢 New engineering blog by Fawaz & @nsatragno! Learn how we built the WebAuthn tab - also share about how we solve a challenge (race condition) when implementing the solution. Give it a read! 👉🏼 https://t.co/SPA04Stl62 https://t.co/Re25uiyFnv _____ http://twitter.com/ChromeDevTools/status/1319288651436548104

18 Oct 2020, 21:39 UTC768 viewsread 10 August 2026

@itsprakash87 https://t.co/zCTl3W2dW3 _____ http://twitter.com/ChromeDevTools/status/1317935527459368960

15 Oct 2020, 10:39 UTC634 viewsread 10 August 2026

There will be Chrome DevTools session as well. Come join us! https://t.co/UsSdlRhKiG _____ http://twitter.com/ChromeDevTools/status/1316683456047280128

12 Oct 2020, 15:39 UTC517 viewsread 10 August 2026

Feedback needed! 👋🏽 Do you find the Performance panel easy / hard to use (or never use it at all)? 🤔 The Chrome DevTools team is currently working on improving the Performance panel. Help us by completing this short 5 questions survey. 👉🏼 https://t.co/SY9tHCBgjC _____ http://twitter.com/ChromeDevTools/status/1315664772701073409

11 Oct 2020, 15:39 UTC442 viewsread 10 August 2026

Have you updated your Chrome? Here's a video highlights the top new features in Chrome DevTools 86. Try out the new Media panel, local fonts emulation and more! Video 👉🏼 https://t.co/LyUe8CQWKg _____ http://twitter.com/ChromeDevTools/status/1315302384646537219

10 Oct 2020, 15:39 UTC355 viewsread 10 August 2026

Did you know DevTools support emulate locales by setting location? 🗺 We skipped the What's new video for Chrome 83 earlier. (You know, the beginning of pandemic. 🤷🏽&zwj;♀️) It's back now! We "backfill" it. 😉 Watch it here 👉🏼 https://t.co/8YsxZGbWoY _____ http://twitter.com/ChromeDevTools/status/1314939996936101889

9 Oct 2020, 15:39 UTC292 viewsread 10 August 2026

TGIF! A tip for you! 😏 Want to *always* view both the Styles & Computed pane? Yes you can! Spot the new button. You can now toggle the Computed side pane *anytime* you want. The feature is in. Make sure you update your Chrome. 😉 https://t.co/JnxCWB51CJ _____ http://twitter.com/ChromeDevTools/status/1314577609028558854

8 Oct 2020, 15:39 UTC255 viewsread 10 August 2026

The Issues tab is designed to help you understand what happened, and give actionable advice on how to fix your site issues. Here's the backstage story by @sigurdschn and Jan on how the team built it - from prototype to implementation to future plan. 👉🏼 https://t.co/HCUfpD9bmP https://t.co/mT3xem5afy _____ http://twitter.com/ChromeDevTools/status/1314215220831682560

7 Oct 2020, 15:42 UTC208 viewsread 10 August 2026

🎉 Chrome 86 is here! We have new Media panel and 3 new emulations to help you debug the web better. Oh, and no more issues warning bar. Update your Chrome today! Watch or read the full list of What's new in DevTools 👉🏼 https://t.co/wLInTnw9UX https://t.co/LQkVxiFeAo _____ http://twitter.com/ChromeDevTools/status/1313852833326723073

2 Oct 2020, 15:39 UTC195 viewsread 10 August 2026

RT @EdgeDevTools: We were pleased to create grid tooling for Edge, Chrome, and other Chromium-based browsers in collaboration with our colleagues at @ChromeDevTools. Good things happen when you work together! 😊 _____ http://twitter.com/ChromeDevTools/status/1312051850519212037

2 Oct 2020, 15:39 UTC188 viewsread 10 August 2026

RT @nsatragno: There's a new #WebAuthn tab on @ChromeDevTools, coming up in version 87! There's no need to carry around a bag with different authenticators to debug your implementations anymore. Just create a virtual authenticator and watch it play the part of a real device. https://t.co/7Zy4G5DeZu _____ http://twitter.com/ChromeDevTools/status/1312051475212836865

Showing the 12 most recent of 20 posts we hold for @ChromeDevTools. 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.

Mentions

Names

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

Addy Osmani
@addyosmani · 71 post GoogleDevExpert
@GoogleDevExpert · 21 post

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.

Handles this channel named that no longer answer

Dead references: 9; handles named in this channel’s posts, vacant today
Evidenced gone: 0; we ourselves saw one of these resolve, at some point
Never seen alive: 9; vacant every time we have ever looked

@ChromeDevTools named 9 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.

Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.

Never seen alive

References a handle that is not a live channel — we have no record it ever was one.

@nsatragno
named in 2 posts, 11 August 2026 – 11 August 2026

@sigurdschn
named in 2 posts, 11 August 2026 – 11 August 2026

@itsprakash87
named in 1 post, 11 August 2026 – 11 August 2026

@jecelynyeen
named in 1 post, 11 August 2026 – 11 August 2026

@mgechev
named in 1 post, 11 August 2026 – 11 August 2026

@sulco
named in 1 post, 11 August 2026 – 11 August 2026

@edgedevtools
named in 1 post, 11 August 2026 – 11 August 2026

@timvdlippe
named in 1 post, 11 August 2026 – 11 August 2026

@gdgbangkok
named in 1 post, 11 August 2026 – 11 August 2026

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

“Chrome DevTools” (@ChromeDevTools), 53 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/ChromeDevTools.

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.