Telegram RegisterThe public register of Telegram
Telegram profile photo for JavaScript test

Channel

JavaScript test

@js_test

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

9,559subscribers

-340 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-1001360497414
TypeChannel
Username@js_test
DescriptionJavascript и все что с ним связано Ссылка: @Portal_v_IT Сотрудничество: @oleginc
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/js_test

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

9,5599,8999,7296 August 2026 — 9,899 subscribers6 August 2026 — 9,899 subscribers9 August 2026 — 9,898 subscribers12 August 2026 — 9,892 subscribers15 August 2026 — 9,881 subscribers18 August 2026 — 9,869 subscribers22 August 2026 — 9,857 subscribers25 August 2026 — 9,844 subscribers28 August 2026 — 9,837 subscribers31 August 2026 — 9,823 subscribers4 September 2026 — 9,816 subscribers9 September 2026 — 9,806 subscribers13 September 2026 — 9,799 subscribers17 September 2026 — 9,781 subscribers25 September 2026 — 9,748 subscribers4 October 2026 — 9,713 subscribers11 October 2026 — 9,692 subscribers14 October 2026 — 9,684 subscribers18 October 2026 — 9,674 subscribers21 October 2026 — 9,669 subscribers24 October 2026 — 9,646 subscribers27 October 2026 — 9,633 subscribers30 October 2026 — 9,614 subscribers2 November 2026 — 9,603 subscribers6 November 2026 — 9,589 subscribers9 November 2026 — 9,582 subscribers14 November 2026 — 9,559 subscribers6 August 202614 November 2026
27 measurements spanning 100 days, net -340. 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 9,508–9,950 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
14 Nov 2026, 06:509,559-23
9 Nov 2026, 10:149,582-7
6 Nov 2026, 08:179,589-14
2 Nov 2026, 22:279,603-11
30 Oct 2026, 16:009,614-19
27 Oct 2026, 09:469,633-13
24 Oct 2026, 13:459,646-23
21 Oct 2026, 05:189,669-5
18 Oct 2026, 07:369,674-10
14 Oct 2026, 21:469,684-8
11 Oct 2026, 17:159,692-21
4 Oct 2026, 22:369,713-35
25 Sept 2026, 13:199,748-33
17 Sept 2026, 11:209,781-18
13 Sept 2026, 01:579,799-7
9 Sept 2026, 09:599,806-10
4 Sept 2026, 01:369,816-7
31 Aug 2026, 13:389,823-14
28 Aug 2026, 19:169,837-7
25 Aug 2026, 16:139,844first reading

Engagement

97 posts held, back to 28 July 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 69 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.06%
avg views ÷ 9,559 subscribers
Avg views / post
293
51 posts measured
Reaction rate
0.554%
reactions ÷ views · ER floor
Posts in window
51
of 97 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. It is computed over the 20 of 51 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held97 (28 July 2026 – 16 November 2026)
Views total14,926
Reactions total32
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 01:01 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
≈3,130
Videos
≈18
Links
≈4,830

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
57s
Average length
11s

Measured directly from 5 videos 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

32 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2475.0%
❤412.5%
🔥412.5%

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 20 of the 97 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 97 most recent posts we hold, published 28 July 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.

Advertising

Ad load
1.03%
1 of 97 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
302
over 1 measured post
Median views · rest
301
over 96 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2Vtzqv7GszW15 November 20265 November 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 97 most recent posts we hold, published 28 July 2026 to 16 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 7 of 51 posts held from the last 30 days (13.7%) 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, 16:13 UTC110 viewsread 17 November 2026
Video

Легко распознавай лица в JavaScript! С этой библиотекой ты сможешь сделать это с минимальным количеством кода. Лучше всего то, что она работает в браузере, без серверов > npm i face-api.js 🖥 JavaScript test // чат

16 Nov 2026, 11:27 UTC195 viewsread 17 November 2026
Photo

❓Что будет на выходе? function Animal() {} const dog = new Animal(); console.log(dog.constructor === Animal); Ответ: true JavaScript test | ChatGPT

16 Nov 2026, 09:30 UTC225 viewsread 17 November 2026
Photo

Полезный репозиторий для тренировки по JavaScript Сохраняйте подборку вопросов по JS, в которой можно проверить и освежить свои знания или подготовиться к собеседованию. Список вопросов обновляется и сейчас там 155 пунктов. ➡️ Забираем здесь 🖥 JavaScript test // чат

15 Nov 2026, 11:17 UTC258 viewsread 17 November 2026
Photo

🔥Что будет на выходе? var foo = {}; var bar = Object.create(foo); foo.a = 1; console.log(bar.a); Ответ: 1 JavaScript test | ChatGPT

14 Nov 2026, 11:20 UTC249 viewsread 17 November 2026
Photo

🧠Что будет на выходе? function asyncSum(arr) { return arr.reduce(async (acc, num) => (await acc) + num, Promise.resolve(0)); } async function computeTotal() { const result = await asyncSum([1, 2, 3, 4, 5]); console.log(result); } computeTotal(); Ответ: 15 JavaScript test | ChatGPT

13 Nov 2026, 16:11 UTC258 views1 reactionsread 17 November 2026
Photo

Неэффективные практики JavaScript: Использование var вместо let и const (источник) Следует применять только let и const по ряду причин: 1. область видимости становится более четкой (между скобками); 2. не создаются глобальные объекты; 3. отмечаются ошибки, если вы повторно объявляете их. Если только вы не используете старый браузер, например IE11, вам стоит отказаться от var. 🖥 JavaScript test // чат

❤1

13 Nov 2026, 11:23 UTC260 viewsread 17 November 2026
Photo

🧩Что будет на выходе? function recursiveFibonacci(n) { return n <= 1 ? n : recursiveFibonacci(n - 1) + recursiveFibonacci(n - 2); } const result = recursiveFibonacci(6); console.log(result); Ответ:8 JavaScript test | ChatGPT

12 Nov 2026, 16:10 UTC286 views2 reactionsread 17 November 2026
Photo

Дока — документация по фронтенду, которую хочется читать Проект собирает статьи по HTML, CSS, JavaScript, доступности, вёрстке и другим темам — без заумных слов и перегруженных терминов. Всё написано понятно, живо и с примерами. 🖥 JavaScript test // чат

👍1🔥1

12 Nov 2026, 11:22 UTC289 views1 reactionsread 17 November 2026
Photo

❓Что будет на выходе? function recursivePalindromeCheck(str) { if (str.length <= 1) { return true; } return str[0] === str[str.length - 1] && recursivePalindromeCheck(str.slice(1, -1)); } const result = recursivePalindromeCheck("radar"); console.log(result); Ответ: true JavaScript test | ChatGPT

❤1

11 Nov 2026, 16:11 UTC302 views1 reactionsread 17 November 2026
Video

Как работает Javascript: шпаргалка для разработчика ➡️ Источник 🖥 JavaScript test // чат

👍1

11 Nov 2026, 15:49 UTC265 viewsread 17 November 2026
Photo

Вакансии Айтишника — ежедневная подборка актуальных вакансий для айтишников. Для тех, кто только закончил учебу, ищет работу получше или тебя заменили нейросетью.

11 Nov 2026, 11:22 UTC266 viewsread 17 November 2026
Photo

❓Что будет на выходе? function recursiveBinarySearch(arr, target, start = 0, end = arr.length - 1) { if (start > end) { return -1; } const mid = Math.floor((start + end) / 2); if (arr[mid] === target) { return mid; } else if (arr[mid] < target) { return recursiveBinarySearch(arr, target, mid + 1, end); } else { return recursiveBinarySearch(arr, target, start, mid - 1); } } const resu…

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

Posts recorded as deleted after publishing

We recorded 7 posts on @js_test as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
12 August 2026
Most recent seen missing
12 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
1

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,852
Telegram ranks this channel #20 of 90 here — alongside 89 others — read 2 October 2026
FrontEndDev
@front_end_dev · 25,363
Telegram ranks this channel #34 of 95 here — alongside 94 others — read 13 September 2026
Senior Frontend - javascript, html, css
@seniorFront · 23,437
Telegram ranks this channel #43 of 89 here — alongside 88 others — read 17 September 2026
Веб-страница
@tproger_web · 22,132
Telegram ranks this channel #50 of 96 here — alongside 95 others — read 20 September 2026
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,572
Telegram ranks this channel #53 of 93 here — alongside 92 others — read 25 September 2026
Frontender's notes [ru]
@frontendnoteschannel_ru · 30,704
Telegram ranks this channel #60 of 95 here — alongside 94 others — read 6 September 2026

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

“JavaScript test” (@js_test), 9,559 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/js_test.

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.