Telegram RegisterThe public register of Telegram

Channel

nightworkslab

@nightworkslab

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

3subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1004440249919
TypeChannel
Username@nightworkslab
DescriptionСозданию всякое полезное и не очень https://nw-lab.com
Created17 July 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/nightworkslab

Growth

39 August 2026 — 3 subscribers13 August 2026 — 3 subscribers9 August 202613 August 2026
2 measurements spanning 4 days. 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:503no change
9 Aug 2026, 08:023first reading

Engagement

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

ERR · 30 days
4848.1%
avg views ÷ 3 subscribers
Avg views / post
145
9 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 11 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 2 August 2026
Posts held11 (17 July 20262 August 2026)
Views total1,309
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 10:50 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
6
Links
9

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

2 Aug 2026, 07:52 UTC98 viewsread 13 August 2026
Photo

~ где-то в то же время, как я выпустил Little Sleepy Quark, я сделал генератор пст-рцк фраз. Всё еще работает 😂 https://pst-rck.nw-lab.com/7N5o216 #web 🖥 nightworkslab @ unseeniverse

29 Jul 2026, 16:03 UTC97 viewsread 13 August 2026
Photo

~ продолжаем. #рабочее 🖥 nightworkslab @ unseeniverse

23 Jul 2026, 06:44 UTC499 viewsread 13 August 2026
Photo

~ новая версия Godot Minimize Web Build - Наконец-то опубликовал в Asset Store - Добавлена поддержка Макоси как хост-системы (как на Интеле, так и на Apple Silicon). Спасибо за помощь antzGames и Никите. В следующем мажорном релизе завезу поддержку Brotli, как варианта компрессии. #mhep #gamedev #godot 🖥 nightworkslab @ unseeniverse

20 Jul 2026, 15:04 UTC109 viewsread 13 August 2026
Photo

~ переезд на новые версии — это больно. #рабочее 🖥 nightworkslab @ unseeniverse

19 Jul 2026, 11:57 UTC273 viewsread 13 August 2026
File

~ первый тестовый билд Aseprite CRT Preview. Инструкция: 1. Скачать crt_preview.aseprite-extension и установить в Aseprite через Edit -> Preferences -> Extentions. Он автоматически начнёт ждать запуска приложения превью. 2. Скачать приложение под вашу платформу (Windows, Linux, MacOs) в удобное место. Запустить (файл самостоятельный, не требует установки). Запустить. 3. Открыть в Aseprite любой спрайт. 4. Настроить

19 Jul 2026, 09:57 UTC101 viewsread 13 August 2026

~ хотел уже выложить билд на "потыкать", но выяснилась презабавная вещь — анимации поддерживаются из коробки 🫠 А из-за долгой пересылки между асиком и превьюхой они ломаются на больших изображениях. Теперь хочу еще раз пересмотреть алгоритм обмена данными, чтобы он был достаточно шустрым, чтобы успевать отрисовывать кадры. Если не получится — выложу уже как есть, но попробовать хочется. #crtase #desktop 🖥 nightwor

18 Jul 2026, 19:29 UTC89 viewsread 13 August 2026
Photo

~ а для CRP Preview я сразу добавил локализацию на разные языки. Только не спрашивайте, почему такой набор. Потому что захотелось. #crtase #desktop 🖥 nightworkslab @ unseeniverse

18 Jul 2026, 15:33 UTC23 viewsread 13 August 2026
Photo

~ планы по Godot Miniimize Web: - Добавить билд под Мак (x64 сделали в гите, с силиконом помог Никита) - Выложить в новый Asset Store - Добавить поддержку сжатия Brotli и настройку выбора между Gzip и Br #godot #mhep 🖥 nightworkslab @ unseeniverse

18 Jul 2026, 15:30 UTC20 viewsread 13 August 2026

~ создаю всякое полезное и не очень. Закреп со списком проектов: CRT Preview для Aseprite Плагин для превью с эмуляцией различных CRT-эффектов в реальном времени. [альфа, собираю фидбэк] #crtase Minimize Web Build для Godot Автоматическое сжатие для web-билдов в Godot (4.3 и выше) [в активной разработке] #mhep Батареечки Инструмент самопроверки состояния по трём шкалам (физические силы, когнитивные способности, эм

Showing the 11 most recent of 11 posts we hold for @nightworkslab. 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 — 266,283 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

“nightworkslab” (@nightworkslab), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/nightworkslab.

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.