Channel
@Makvinski
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
237subscribers
+76 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003714383074 |
|---|---|
| Type | Channel |
| Username | @Makvinski |
| Created | 21 May 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/Makvinski |
Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 85% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 13:01 | 237 | +26 |
| 30 Sept 2026, 03:21 | 211 | +2 |
| 16 Sept 2026, 01:00 | 209 | +15 |
| 8 Sept 2026, 10:56 | 194 | -4 |
| 30 Aug 2026, 05:54 | 198 | +1 |
| 23 Aug 2026, 03:38 | 197 | +26 |
| 16 Aug 2026, 15:35 | 171 | +9 |
| 9 Aug 2026, 14:11 | 162 | +1 |
| 9 Aug 2026, 10:00 | 161 | first reading |
5 posts held, back to 21 May 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
38 reactions across 4 posts, in 10 distinct kinds. The most used accounts for 15.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5438260982872822751 | 6 | 15.8% | |
| custom 5332369814025419541 | 5 | 13.2% | |
| custom 5474480077007780142 | 5 | 13.2% | |
| custom 5442659424520921632 | 4 | 10.5% | |
| custom 5866066131013342982 | 4 | 10.5% | |
| custom 5192996832485063350 | 3 | 7.89% | |
| custom 5352669272575321097 | 3 | 7.89% | |
| custom 5435988399712387580 | 3 | 7.89% | |
| custom 5458604164189797786 | 3 | 7.89% | |
| custom 5866017584997995877 | 2 | 5.26% |
Custom emoji. Every row above is a 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 4 of the 5 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 38 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 21 May 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.
✨✨✨✨✨✨✨✨✨✨ ➿➿➿➿➿➿➿➿➿➿➿ 𝘙𝘜𝘓𝘌𝘚 𝘈𝘋𝘔𝘐𝘕𝘚 𝘉𝘖𝘖𝘚𝘛 𝘛𝘐𝘒𝘛𝘖𝘒 𝘊𝘏𝘈𝘛 𝘝𝘐𝘋𝘌𝘖 𝘔𝘌𝘔𝘌𝘚 𝘈𝘕𝘖𝘕 𝘈𝘙𝘊𝘏𝘐𝘝𝘌
custom 53323698140254195412custom 53526692725753210972custom 51929968324850633501custom 54359883997123875801custom 54382609828728227511custom 54426594245209216321custom 54744800770077801421custom 58660661310133429821
✨✨✨✨✨✨ ➿➿➿➿➿➿➿ название «𝙢𝙘𝙦𝙪𝙞𝙣𝙫𝙞𝙡𝙡𝙚» принадлежит только нам. при схожести с нашим названием — мы имеем полное право попросить сменить название вашего. ➿➿➿➿➿➿➿ действует с: 2⃣1⃣➖0⃣5⃣➖2⃣0⃣2⃣6⃣
custom 54382609828728227512custom 54744800770077801422custom 51929968324850633501custom 53323698140254195411custom 54426594245209216321custom 58660175849979958771custom 58660661310133429821
✨✨✨✨✨ ➿➿➿➿➿➿➿➿➿➿ незнание правил не освобождает вас от ответственности. ➿➿➿➿➿➿➿➿➿➿ не оскорблять никого в чате, будь это простой участник или админ. есть какие-то проблемы — переходите в личку, не впутывайте других в вашу ссору. не затрагиваем политику/религию/внешность/вкусы ( в форме буллинга) других участников. общение только на русском языке, или пишите перевод в этом же сообщении селф./расчлененку/+18 контент…
custom 54426594245209216322custom 54586041641897977862custom 53323698140254195411custom 54359883997123875801custom 54744800770077801421custom 58660175849979958771custom 58660661310133429821
✨✨✨✨✨✨ ➿➿➿➿➿➿➿➿➿➿ 𝘖𝘞𝘕𝘌𝘙💋 @MCQJLP | @XAXAXAXAX_HAXYU 𝘚𝘌𝘕𝘐𝘖𝘙 𝘈𝘋𝘔𝘐𝘕💋 @ZAR2D1 | @hkmrtt 𝘊𝘏𝘈𝘛 𝘈𝘋𝘔𝘐𝘕 — 😡 𝘈𝘊𝘛𝘐𝘝𝘌 𝘈𝘋𝘔𝘐𝘕💋 @qwwug_h 𝘝𝘐𝘋𝘌𝘖 𝘈𝘋𝘔𝘐𝘕💋 @H4RK0T1K | @sselodk 𝘕𝘌𝘞 𝘈𝘋𝘔𝘐𝘕 — 😡 ➿➿➿➿➿➿➿➿➿➿ идет активный набор в администрацию. обращаться к владельцу
custom 54382609828728227513custom 51929968324850633501custom 53323698140254195411custom 53526692725753210971custom 54359883997123875801custom 54586041641897977861custom 54744800770077801421custom 58660661310133429821
Channel created
Showing the 5 most recent of 5 posts we hold for @Makvinski. 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.
Named by 8 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“𝙢𝙘𝙦𝙪𝙞𝙣𝙫𝙞𝙡𝙡𝙚 𝙞𝙣𝙛𝙤” (@Makvinski), 237 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/Makvinski.
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.