Telegram RegisterThe public register of Telegram
Telegram profile photo for NodeUA - JavaScript and Node.js in Ukraine

Supergroup

NodeUA - JavaScript and Node.js in Ukraine

@nodeua

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Referenced elsewhere · Cite this entry

3,219members

-16 since we began measuring on 6 August 2026

121 online right now

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

Register entry

Telegram ID-1001124482287
TypeSupergroup
Username@nodeua
Created17 August 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded9 September 2026
Last confirmed live27 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/nodeua

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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,2073,2373,2226 August 2026 — 3,235 members7 August 2026 — 3,233 members9 August 2026 — 3,235 members12 August 2026 — 3,229 members16 August 2026 — 3,231 members19 August 2026 — 3,229 members22 August 2026 — 3,222 members26 August 2026 — 3,214 members28 August 2026 — 3,211 members1 September 2026 — 3,207 members4 September 2026 — 3,237 members9 September 2026 — 3,233 members9 September 2026 — 3,233 members13 September 2026 — 3,227 members17 September 2026 — 3,220 members27 September 2026 — 3,219 members3,2196 August 202627 September 2026
16 measurements spanning 51 days, net -16. 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,203–3,242 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
27 Sept 2026, 02:573,219-1
17 Sept 2026, 21:183,220-7
13 Sept 2026, 09:163,227-6
9 Sept 2026, 23:343,233no change
9 Sept 2026, 16:373,233-4
4 Sept 2026, 10:013,237+30
1 Sept 2026, 06:133,207-4
28 Aug 2026, 23:053,211-3
26 Aug 2026, 06:543,214-8
22 Aug 2026, 22:073,222-7
19 Aug 2026, 06:543,229-2
16 Aug 2026, 17:043,231+2
12 Aug 2026, 23:243,229-6
9 Aug 2026, 21:113,235+2
7 Aug 2026, 01:523,233-2
6 Aug 2026, 17:563,235first 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.

Mentions

Named by 4 registered channels — 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.

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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

User Group (uk.wikipedia.org)
“…– група українських користувачів [[Amazon Web Services|AWS]]. [https://t.me/nodeua NodeUA] – група розробників на мові програмування [[JavaScript]].…”
read 13 September 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 27 September 2026 — this entry's latest reading, not the date you are reading this.

“NodeUA - JavaScript and Node.js in Ukraine” (@nodeua), 3,219 members as measured 27 September 2026. Telegram Register, tgregister.com/channel/nodeua.

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.