Telegram RegisterThe public register of Telegram
Telegram profile photo for гаечный ключ 🔧

Channel

гаечный ключ 🔧

@dayyroo

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

30subscribers

+2 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-1003112255447
TypeChannel
Username@dayyroo
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live10 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 10 September 2026
On Telegramt.me/dayyroo

Growth

2830299 August 2026 — 28 subscribers11 August 2026 — 28 subscribers17 August 2026 — 29 subscribers1 September 2026 — 30 subscribers9 August 20261 September 2026
4 measurements spanning 23 days, net +2. 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 28–30 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 05:4430+1
17 Aug 2026, 15:5829+1
11 Aug 2026, 06:4528no change
9 Aug 2026, 01:1728first reading

Engagement

19 posts held, back to 22 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 page of 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 19 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
36s
Average length
18s

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

132 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 39.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5239.4%
🔥1813.6%
custom 5451693630530034683118.33%
🥰107.58%
custom 524721461843411331164.55%
💘64.55%
custom 526038672478519538953.79%
❤‍🔥53.79%
😱53.79%
💋43.03%
custom 526029954124405693332.27%
🍓32.27%
🙏32.27%
💊10.758%

Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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

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

3 Aug 2026, 16:46 UTC13 views4 reactionsread 11 August 2026
Photo

у моего бро сегодня день рождения!! для него тоже арт :3 ох уж эти др.. я давно так быстро арты не заканчивала.. это кстати второй мой полноценный арт, нарисованный в крите XD #арт

3🔥1

Signed ʀᴇʟᴍᴀx

31 Jul 2026, 12:08 UTC125 views7 reactionsread 11 August 2026
Photo

сегодня день рождения у моего второго полукубия, в честь этого нарисовала ей артик <3 🐧 #арт

3🔥3💘1

Signed ʀᴇʟᴍᴀx

26 Jul 2026, 11:08 UTC36 views7 reactionsread 11 August 2026
Photo

вчера вышел финал моего любимого майнкрафт сериала, небольшой скетчек по фану 😔 #вайтпайн #скетч

3❤‍🔥3🔥1

Signed ʀᴇʟᴍᴀx

11 Jul 2026, 20:05 UTC51 views3 reactionsread 11 August 2026
Photo

прикольчик с ос #ос

3

Signed ʀᴇʟᴍᴀx

27 Jun 2026, 14:03 UTC254 views11 reactionsread 11 August 2026
Photo

synchron duo core: #скетч #ос

custom 545169363053003468362🔥2custom 52603867247851953891

Signed ʀᴇʟᴍᴀx

23 Jun 2026, 21:21 UTC87 views10 reactionsread 11 August 2026
Photo

сегодня рисовали с бро шарплоу в магме, я справа 👀 #арт #шарплоу #шарпнесс #джудлоу

custom 54516936305300346835custom 52603867247851953894🥰1

Signed ʀᴇʟᴍᴀx

20 Jun 2026, 14:19 UTC79 views11 reactionsread 11 August 2026
Photo

понемногу начинаю заканчивать свои скетчи полноценными артами! #арт #ос

custom 52472146184341133115🥰3custom 52602995412440569332💊1

Signed ʀᴇʟᴍᴀx

17 Jun 2026, 16:23 UTC66 views9 reactionsread 11 August 2026
Photo

completed!!! смотреть #арт #ос

5🔥1🥰1custom 52472146184341133111custom 52602995412440569331

Signed ʀᴇʟᴍᴀx

13 Jun 2026, 22:12 UTC64 views7 reactionsread 11 August 2026
Photo

я уже красный 🫩 #скетч

5🍓1🥰1

Signed ʀᴇʟᴍᴀx

11 Jun 2026, 06:59 UTC57 viewsread 11 August 2026

с каких пор ютуб и роблокс разблокировали...

Signed ʀᴇʟᴍᴀx

10 Jun 2026, 08:48 UTC61 views7 reactionsread 11 August 2026
Photo

пока не было интернета нарисовала любимого лоэна 🫪 думаю это первый раз, когда мне настолько понравился арт... #арт #геншин

💋41💘1🔥1

Signed ʀᴇʟᴍᴀx

23 May 2026, 16:21 UTC67 views6 reactionsread 11 August 2026
Photo

привет спасибо хорошо... спойлер к будущему арту

5🍓1

Signed ʀᴇʟᴍᴀx

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

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.

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

“гаечный ключ 🔧” (@dayyroo), 30 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/dayyroo.

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.