Channel
@gd47g
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
579subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002840628774 |
|---|---|
| Type | Channel |
| Username | @gd47g |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/gd47g |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 12:02 | 579 | -1 |
| 7 Aug 2026, 04:00 | 580 | no change |
| 7 Aug 2026, 03:48 | 580 | first reading |
14 posts held, back to 6 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 14 (6 July 2026 – 27 July 2026) |
| Views total | 1,096 |
| Reactions total | 32 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 04:00 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.
63 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 76.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 48 | 76.2% | |
| 🔥 | 14 | 22.2% | |
| 🤯 | 1 | 1.59% |
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 14 of the 14 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 63reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 6 July 2026 to 27 July 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.
Пример хорошей композиции: ⤵️ Композиция чаще всего субъективна и зависит от вашей идеи, но вы должны хотя бы базово знать как лучше располагать объекты в сцене, это вам пригодится в создании артов, эндскрина, структур и декора, с опытом вы начнёте лучше понимать композицию и даже намерено нарушать её правила если этого требует идея. Если я что-то упустил то комментарии всегда открыты
❤7🔥2🤯1
Signed DP47
#гайд #декор #геймплей 🏘 Композиция ℹ️ Это продуманное расположение элементов таким образом, чтобы они гармонично сочетались и передавали общую идею в целом Это понятие универсальное и применяется в разных видах творчества, в гд это может проявляться в расположении структур и пил в уровне или деталей, цветов в декоре 1. В гд с помощью композиции вы указываете игроку куда ему смотреть, без неё он просто не поймёт …
❤8🔥1
Signed DP47
📅
🔥11❤2
Signed DP47
Общие рекомендации: Чтобы закрепить камеру на меню используйте Static Camera, желательно совместно с Camera Guide чтобы видеть границы экрана меню. Можете ещё использовать UI триггер если Вам это нужно Сделайте визуализацию выбора, если у меня это стрелка которая двигается, у вас это может быть смена размера или цветов, или всё вместе. Также для приятного эффекта можете добавить SFX Если у вас много кнопок в меню,…
❤4
Signed DP47
Уровень из видео
❤1
Signed DP47
ℹ️ Использует коллизии и триггеры коллизии, визуально понятнее, но логика такая же. Система понимает выбор кнопки благодаря касаниям коллизии которая перемещается от нажатий 1. Движение коллизии При активации Event коллизия двигается вверх/вниз с помощью Move проходя через колиззии 1 2 3, но чтобы она не выходила за границы этих колиззиий активация движения проходит через Instant Collision Если при нажатии вправо …
❤2
Signed DP47
Второй способ: коллизии ⤵️ Объяснение ниже
❤2
Signed DP47
Уровень из видео
❤2
Signed DP47
ℹ️ Заключается в создании механики меню через числовые триггеры. В общем система понимает что Вы выбрали благодаря текущему числу которое изменяется в зависимости от нажатий 1. Нажатие влево/вправо: Event триггеры активируют Instant Count которые проверяют больше или меньше Item1 чем указанное в триггере число, если да то активирует цепь триггеров дальше Нажатие вправо: если Item1 меньше 2 то стрелка двигается вни…
❤2
Signed DP47
Первый способ: Item триггеры ⤵️ Объяснение ниже
❤2
Signed DP47
#гайд #триггер 🛠 Гайд на меню уровня ℹ️ Обычно такие меню где можно выбрать язык, настроить уровень или выйти из него встречаются в платформерах и мини играх ⤵️ Существует два популярных способа как сделать меню:
❤4
Signed DP47
🎮 Как делать управление мы уже давно разобрались, но некоторые просили показать тутор на меню с кнопками, об этом и будет следущий пост
❤3
Signed DP47
Showing the 12 most recent of 14 posts we hold for @gd47g. 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 — 957,256 of 1,183,361entries 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.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Гайды по редактору Geometry Dash” (@gd47g), 579 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/gd47g.
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.