.короче чтоб когда я проснулся тут было 42 реакта
custom 52491985840872128028🍌1

Channel
@Four45canon
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
55subscribers
+5 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003851593480 |
|---|---|
| Type | Channel |
| Username | @Four45canon |
| Created | Between 1 February 2026 and 9 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/Four45canon |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 13:38 | 55 | +1 |
| 31 Aug 2026, 10:09 | 54 | +2 |
| 23 Aug 2026, 14:27 | 52 | +1 |
| 10 Aug 2026, 10:46 | 51 | no change |
| 8 Aug 2026, 21:28 | 51 | +1 |
| 8 Aug 2026, 06:06 | 50 | first reading |
11 posts held, back to 9 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 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 11 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
145 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 58.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249198584087212802 | 85 | 58.6% | |
| ❤ | 14 | 9.66% | |
| 🎉 | 14 | 9.66% | |
| custom 5388873892670480984 | 7 | 4.83% | |
| 💘 | 7 | 4.83% | |
| custom 5359663931759564551 | 6 | 4.14% | |
| custom 5429287000895136016 | 6 | 4.14% | |
| 🍌 | 4 | 2.76% | |
| 🍓 | 2 | 1.38% |
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 10 of the 11 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 145 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 9 July 2026 to 7 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.
.короче чтоб когда я проснулся тут было 42 реакта
custom 52491985840872128028🍌1
.второй арт за день!!! .вот это да!!! .давайте реакты как всегда по красоте 🤩 чтоб я радовался и рисовал больше 🤩 .три 3️⃣3️⃣3️⃣3️⃣3️⃣
custom 524919858408721280215custom 53888738926704809847❤3🍌1
.привет , это гифт моей доче на др ! .он уже прошел, но вы можете все равно поздравить ее в коментах 😍
custom 524919858408721280210custom 53596639317595645513🍌1🎉1💘1
😭 .делаю всё, кроме извинений .
custom 524919858408721280215💘5❤4🍓1🎉1
ноль контекста
custom 52491985840872128027❤1
привееет с августой вас ч вернулась и теперь буду делоть вам арты очен часто i promise #animalhospital #Bfdi #Onethree уантройки в виде медсестер из aha дадада
custom 52491985840872128027🎉2
🤩.хай поцантре, у меня новый мониторчик и теперь я снова могу рисовать!! .часть артов я забыл выложить до поломки, часть новая.... 😻 .РЕАКТЫ БЫСТРЕЕ. БЕГОМ. я сказал бегом. 🤩🤩
custom 524919858408721280213custom 54292870008951360166🎉3custom 53596639317595645513🍓1💘1
Обоже
🎉5
.ПРИВЕТ НЬЮШКИ и олдушки 🤩 .короче, опять у меня проблемки, я беру рест на неопределенный срок. .я не могу рисовать щя, тк у меня сломался нахуй монитор. починить его нельзя, новый купить только... так что, это займет какое-то время .я могу, конечно, постить сюда скетчи на бумаге ... возможно, я так и буду делать, чтобы канал совсем не пустовал. не знаю... .не теряйте в общем... 🤩
custom 524919858408721280210❤1🍌1🎉1
Posted without readable text
йоу мне чипсы купили. и вы кушайте. . #sweetdessertau #osc #полноценка
❤5🎉1
Showing the 11 most recent of 11 posts we hold for @Four45canon. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“.Кирюша Новьер⁴² 🇪🇪” (@Four45canon), 55 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Four45canon.
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.