Telegram RegisterThe public register of Telegram
Telegram profile photo for Arachne.Games

Channel

Arachne.Games

@arachnegames

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

219subscribers

+3 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-1001837677792
TypeChannel
Username@arachnegames
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/arachnegames

Growth

216219217.57 August 2026 — 216 subscribers8 August 2026 — 216 subscribers22 August 2026 — 219 subscribers7 August 202622 August 2026
3 measurements spanning 15 days, net +3. 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 216–219 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 08:57219+3
8 Aug 2026, 10:47216no change
7 Aug 2026, 12:09216first reading

Engagement

20 posts held, back to 15 March 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 3 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 01s
Average length
31s

Measured directly from 2 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

50 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 42.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2142.0%
👍1122.0%
🤮714.0%
👎612.0%
🥰48.00%
💔12.00%

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

Measured over the 20 most recent posts we hold, published 15 March 2026 to 3 April 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

3 Apr 2026, 13:56 UTC127 views6 reactionsread 8 August 2026

оценки вроде можно ставить ток спустя 10 минут геймплея

2🤮2👎1💔1

3 Apr 2026, 13:56 UTC126 views6 reactionsread 8 August 2026

⭐️!опубликовано!⭐️ если много звезд поставите то скину сколько я с нее заработал, если нет то нет :)

4👍1🥰1

3 Apr 2026, 13:54 UTC127 views4 reactionsread 8 August 2026

Стик паук супергерой: выстрел паутины https://yandex.ru/games/app/stik-pauk-supergeroi-vystrel-pautiny-494175?utm_source=app_page

4

30 Mar 2026, 15:16 UTC130 viewsread 8 August 2026

Игру отклонили, сейчас с Яндекс поддержкой решаем этот момент :)

24 Mar 2026, 15:46 UTC173 viewsread 8 August 2026

Сколько сейчас модерация длится???

23 Mar 2026, 12:37 UTC141 views4 reactionsread 8 August 2026
Video

вот он! РЕМЕЙК СТАРОГО ПАУКА❤️ оцените пожалуйста:

👍2👎1🤮1

18 Mar 2026, 12:17 UTC168 views6 reactionsread 8 August 2026

это проект, глянем что выйдет

👍4👎1🤮1

18 Mar 2026, 12:17 UTC162 views6 reactionsread 8 August 2026

прямо сейчас делаю кое что, позже скину:))

👍4👎1🤮1

Showing the 12 most recent of 20 posts we hold for @arachnegames. 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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“Arachne.Games” (@arachnegames), 219 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/arachnegames.

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.