Telegram RegisterThe public register of Telegram
Telegram profile photo for Gypsy Studio Game | DevLOG

Channel

Gypsy Studio Game | DevLOG

@gypsy_studio_game

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry

71subscribers

+5 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-1002474442547
TypeChannel
Username@gypsy_studio_game
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live29 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/gypsy_studio_game

Growth

667168.57 August 2026 — 66 subscribers10 August 2026 — 66 subscribers15 August 2026 — 68 subscribers29 August 2026 — 71 subscribers7 August 202629 August 2026
4 measurements spanning 21 days, net +5. 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 65–72 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 04:0371+3
15 Aug 2026, 20:1568+2
10 Aug 2026, 02:0166no change
7 Aug 2026, 18:5766first reading

Engagement

13 posts held, back to 15 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
35.7%
avg views ÷ 71 subscribers
Avg views / post
25.3
6 posts measured
Reaction rate
16.0%
reactions ÷ views · ER floor
Posts in window
6
of 13 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 4 of 6 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 9 August 2026
Posts held13 (15 July 20269 August 2026)
Views total152
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 02: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

Video runtime
40s
Average length
40s

Measured directly from 1 video 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

24 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 37.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥937.5%
😁416.7%
👍312.5%
🤔28.33%
👀14.17%
👎14.17%
👏14.17%
😢14.17%
😱14.17%
🤣14.17%

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

Measured over the 13 most recent posts we hold, published 15 July 2026 to 9 August 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.

Recent posts

9 Aug 2026, 08:52 UTC39 viewsread 10 August 2026
Photo

🎥👁 Вот смотрю я на эту красоту и думаю...это какой же движок мог такое нарендерить? 📎 Варианты присылайте в комментарии...но пока секрет раскрывать не буду😏

8 Aug 2026, 18:49 UTC18 views3 reactionsread 10 August 2026
Photo

💻 👁 Сегодня, общаясь в чате, в котором я сижу уже лет 10, мой корешок Бжэж, с которого, кстати, списан Бжэжэк в PineFall, высказал критику в адрес моего лучшего друга — ChatGPT. 🗣Якобы он хвалит вообще всё подряд и всех без разбора. 😄 📎Ну что ж... пришлось провести независимую экспертизу. Прикрепляю скрины, где Claude Opus хвалит то, что мы с GPT вместе сделали. Наука доказала: я всё-таки гений. 🤝😏

🤔1😁1😱1

6 Aug 2026, 16:09 UTC15 views4 reactionsread 10 August 2026
Photo

Photo, posted without a caption

🔥3🤔1

5 Aug 2026, 18:53 UTC19 viewsread 10 August 2026
Photo

Я просто сохраню это здесь....возможно когда то потом сделаю рубрику для подобных полезностей.

4 Aug 2026, 17:29 UTC24 views2 reactionsread 10 August 2026
Photo

А я думал: будет ли тут подвох? Unity же выглядел “слишком хорошим”… 👉🏻 Вот он: ретаргетинг в Unity просто пережёвывает скелетную анимацию и выплёвывает вместо неё какой-то мусор. 📎Чем это может быть критично именно мне? Я не профессиональный разработчик, и я собирался делать анимации так: брать готовые из Mixamo, дорабатывать их в Blender и уже потом гнать в движок. Так я делал в Godot и рассчитывал, что в Unity э

👎1😁1

1 Aug 2026, 14:16 UTC37 views6 reactionsread 10 August 2026
Photo

🎥👁 Случился ремастер... Больно? Немного. Но искусство требует жертв😏 📎 Практически закончил перенос всех наработок с одного движка на другой. Осталось совсем немного — и можно будет снова с головой нырнуть в разработку. Успех неизбежен. Всем мир✌🏻 #godot #unity #indiedev #horror #noire #solodev

👍3🔥2👀1

31 Jul 2026, 19:32 UTC25 viewsread 10 August 2026

Кому скучно залетайте на стримчик, у меня море монотонной работы, есть время поболтать👀 https://www.twitch.tv/gypsy_studio_game

28 Jul 2026, 11:42 UTC43 views1 reactionsread 10 August 2026
Video

Всем привет.✋🏻 🚑 Ну что, перенос PineFall на Unity уже примерно на 60% готов. 📎 Осталось ещё немного — и можно будет с чистой совестью продолжать разработку уже на новом движке.

🔥1

23 Jul 2026, 07:55 UTC43 views3 reactionsread 10 August 2026
Photo

👁🎥 Один из моих постоянных зрителей, @Sjims, на прошлом стриме сказал: «Ну всё, осталось только перейти на Unity...» Если бы он только знал... 😄 👀 Да, тестируем Unity под наш шедевр. Можете плеваться, крутить пальцем у виска и говорить, что я окончательно сошёл с ума. 📎 Но нет. Я всё ещё верю, что где-то существует та самая золотая середина между красивой графикой и удобством разработки. И пока не найду её — не ус

👏1🔥1🤣1

20 Jul 2026, 11:13 UTC31 viewsread 10 August 2026

🎥👁Дамы и господа, стрим идет уже больше двух часов а я забыл вам об этом сообщить... За что естественно извиняюсь...🤜🏻🫷🏻 https://www.twitch.tv/gypsy_studio_game

19 Jul 2026, 06:24 UTC36 views2 reactionsread 10 August 2026

PART 2: То ли мне так «повезло», то ли это проблема всех подобных нейронок, но сетка после Tripo оказалась просто отвратительной. Выделение работает криво, нормально сделать швы невозможно, а если использовать родную UV-развёртку — текстуры ложатся с кучей артефактов. В общем, после смеси ручной лепки и нейронки я наконец получил что-то похожее на нормальный костюм... и тут выяснилось, что Automatic Weights на таком

🔥1😁1

19 Jul 2026, 06:18 UTC34 views3 reactionsread 10 August 2026
Photo

PART 1: Как вы помните, из-за желания подтянуть визуал и некоторых удобств я начал переезд на UE5. Ну и, как вы помните, создал своего первого MetaHuman. Именно он должен был стать главным героем DEMO. Для версии на Godot я делал персонажей через Tripo3D, и к этой теме мы ещё обязательно вернёмся. Так вот, модели получились с кривыми текстурами и в любом случае требовали доработки. Одним из главных плюсов перехода н

🔥1😁1😢1

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

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

“Gypsy Studio Game | DevLOG” (@gypsy_studio_game), 71 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/gypsy_studio_game.

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.