Telegram RegisterThe public register of Telegram
Telegram profile photo for Maknemy

Channel

Maknemy

@theMaknemy

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

18,160subscribers

+743 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002330748173
TypeChannel
Username@theMaknemy
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/theMaknemy

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 74% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@bfsnews/17693 Aug 2026, 17:42 UTC@theMaknemy/5159 · this entry4 Aug 2026, 07:11 UTC1.0013 hours
@bfsnews/17724 Aug 2026, 11:27 UTC@theMaknemy/5162 · this entry4 Aug 2026, 11:27 UTC1.00under a minute
@bfsnews/17757 Aug 2026, 05:43 UTC@theMaknemy/5170 · this entry7 Aug 2026, 05:43 UTC1.00under a minute
@bfsnews/17767 Aug 2026, 08:10 UTC@theMaknemy/5171 · this entry7 Aug 2026, 08:14 UTC1.004 minutes
@bfsnews/17777 Aug 2026, 08:41 UTC@theMaknemy/5172 · this entry7 Aug 2026, 08:41 UTC1.00under a minute
@bfsnews/17807 Aug 2026, 09:55 UTC@theMaknemy/5173 · this entry7 Aug 2026, 09:56 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@bfsnews11 (8/8 hand-verifiable sample passed)1.00under a minute@bfsnews (110)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 7 of the 11 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 21 comparable posts for this entry, running 2 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @bfsnews. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

17,41718,19217,804.57 August 2026 — 17,417 subscribers8 August 2026 — 17,425 subscribers9 August 2026 — 17,778 subscribers10 August 2026 — 17,890 subscribers11 August 2026 — 17,892 subscribers12 August 2026 — 17,862 subscribers13 August 2026 — 17,881 subscribers14 August 2026 — 18,192 subscribers16 August 2026 — 18,160 subscribers18,1607 August 202616 August 2026
9 measurements spanning 9 days, net +743. 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 17,301–18,308 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 05:5618,160-32
14 Aug 2026, 16:5818,192+311
13 Aug 2026, 06:3317,881+19
12 Aug 2026, 08:5217,862-30
11 Aug 2026, 09:0217,892+2
10 Aug 2026, 05:4217,890+112
9 Aug 2026, 07:1217,778+353
8 Aug 2026, 09:5317,425+8
7 Aug 2026, 12:4617,417first reading

Engagement

37 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
23.8%
avg views ÷ 18,160 subscribers
Avg views / post
4,310
37 posts measured
Reaction rate
0.744%
reactions ÷ views · ER floor
Posts in window
37
of 37 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held37 (2 August 202614 August 2026)
Views total159,627
Reactions total1,188
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 10:28 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.

Reaction mix

1,188 reactions across 37 posts, in 43 distinct kinds. The most used accounts for 29.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
35129.5%
custom 545877225202988771813811.6%
custom 545860441759286384513711.5%
🔥857.15%
😢655.47%
🤡645.39%
🤬554.63%
👌504.21%
😭453.79%
❤‍🔥322.69%
😈221.85%
🆒191.60%
🎉181.52%
👍151.26%
💩151.26%
🤮121.01%
🖕80.673%
custom 545639252661529044540.337%
👎40.337%
💋40.337%
23 further kinds453.79%

Custom emoji. 3 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 areTelegram’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 37 of the 37 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 1,188reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 37 most recent posts we hold, published 2 August 2026 to 14 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.

Telegram Stars

Stars received
10
across the posts below
Posts paid on
2
of 37 we hold a reading for · 5%
Most on one post
9
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @theMaknemy. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 37 most recent posts we hold for this entry, published 2 August 2026 to 14 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

14 Aug 2026, 21:04 UTC≈1,830 views14 reactionsread 15 August 2026
Photo

🎬 Тизер Update 30 выйдет уже на следующих выходных! Владелец Blox Fruits поделился новой информацией о грядущем Update 30. За последние несколько дней разработчики уже начали записывать короткие фрагменты геймплея тестеров. Теперь им понадобится ещё несколько дней, чтобы смонтировать материал и добавить кинематографические сцены. 🔥 Самое главное — премьера тизера запланирована на следующие выходные. Этот тизер ст

8👎3👍2🔥1

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

14 Aug 2026, 13:01 UTC≈2,240 views19 reactionsread 15 August 2026
Photo

🎬 Будущий клип обновления может быть Absolute Cinema 🔥 Новый клип Blox Fruits может оказаться намного масштабнее предыдущих — разработчики могут совместить продолжение сюжета и демонстрацию нового контента в одной большой битве. 🔍 Одним из центральных персонажей, скорее всего, станет Felku — глава BAMP Gang и один из самых загадочных персонажей этой истории. 🧪 Его фрукт пока неизвестен. Один из возможных вариантов

👍105❤‍🔥1🔥1🆒1custom 54563925266152904451

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

14 Aug 2026, 10:03 UTC≈2,370 views24 reactionsread 15 August 2026
Photo

🤜 Будущий сюжет Blox Fruits — война 4 сторон? 🔥 Если продолжить сюжет прошлого трейлера, то сейчас в истории Blox Fruits можно выделить сразу четыре независимые стороны. 👹 Mygame43 и Красная армия Mygame43 использует Oni Fruit и представляет отдельную мощную фракцию. 🪽 rip_indra и Небесная армия Indra связан с Celestial Fruit, поэтому его сторона, скорее всего, будет представлять небесные силы. 🩸 Felku и BAMP Gan

14💋3❤‍🔥2👍1👎1👾1🔥1custom 54563925266152904451

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

14 Aug 2026, 07:53 UTC≈2,540 views24 reactionsread 15 August 2026
Photo

📖 Лор Blox Fruits — что происходит в истории? 🎬 В прошлом сюжетном трейлере нам показали сразу несколько важных персонажей: • Zero — Control Fruit • Zioles — Dark Fruit • Uzoth — Dragon Talon и ручной East Dragon • Felku — фрукт неизвестен • Mygame43 — Oni Fruit • rip_indra — Celestial Fruit • Ashen — Lightning Fruit • Gravity User — Gravity Fruit 💀 Один из главных моментов прошлого трейлера — смерть Zioles. Zero

🆒147👍1🤮1custom 54563925266152904451

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

13 Aug 2026, 08:00 UTC≈3,320 views25 reactionsread 15 August 2026
Photo

🔥 РОЗЫГРЫШ 5 DOG BLADE! 🗡️ Сразу 5 победителей — каждый заберёт по Dog Blade! 🎁 Призы: 🟠–🟠 Dog Blade 📆 Итоги — 20 августа ✍️ Для участия подпишитесь на: @theMaknemy @bftierlist @bfsnews @bloxteamshop 🎲 Целых 5 призовых мест, поэтому шанс забрать Dog Blade намного выше обычного! 🍀 Всем удачи! Возможно, именно ты станешь одним из 5 победителей.

19👍1👾1🔥1🖕1🤝1custom 54563925266152904451

Signed RandomGodBot⚡️ [Рандомайзер]

11 Aug 2026, 12:42 UTC≈4,240 views30 reactionsread 15 August 2026
Photo

🔥 Zioles прокомментировал работу над новым клипом Blox Fruits! 👀 Только что Zioles опубликовал пост в Twitter, связанный с новым клипом обновления, и написал: «This is gonna be peak mgod» Похоже, разработчики действительно готовят что-то масштабное. 🎬 Ну что, готовы увидеть новый клип обновления Blox Fruits?

🔥263👌1

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

11 Aug 2026, 11:49 UTC≈3,780 views14 reactionsread 15 August 2026
Forwarded from @bftierlist

📊 Обновление Maknemy Tierlist В тирлисте снова актуализированы цены после последних изменений в трейдах: 📈 Red Lightning — вырос 📉 Yellow Lightning — упал 📈 Celestial Pain — вырос 🌐 Все актуальные цены уже на сайте: https://maknemytierlist.site 🍀 Удачи в трейдах!

🤡9❤‍🔥31👌1

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

11 Aug 2026, 06:41 UTC≈4,350 views26 reactionsread 15 August 2026
Photo

📣 Новая система защиты промокодов в Blox Fruits ℹ️ Совсем недавно мы поднимали тему с таймером при вводе кода SUMMERUPDATE. 🔜 Если открыть меню ввода кодов и ввести SUMMERUPDATE, вместо привычной ошибки появляется сообщение с обратным отсчётом: Code “SUMMERUPDATE” is blocked for another… 👎 Тогда многие подумали, что это обратны отсчёт до какого-то изменения в игре. 🛡 Однако, как выяснилось позже, это новая систем

18👌3custom 54587722520298877183custom 54586044175928638452

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

10 Aug 2026, 20:28 UTC≈3,600 views7 reactionsread 15 August 2026
Forwarded from @bftierlist

📊 Обновление Maknemy Tierlist 🎨 Дополнительно к сегодняшнему большому обновлению дизайна мы актуализировали цены на сайте. 📈 Изменения в экономике: • Rabid Dog Blade — вырос • Dog House (Frame Break) — вырос 🖥 Все актуальные цены уже доступны на сайте: https://maknemytierlist.site Maknemy Ⓜ️ Тир Листы 📊 Trade Ru 💱 BF News 🗞️

5👌2

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

10 Aug 2026, 17:26 UTC≈3,850 views61 reactionsread 15 August 2026

🎉 Результаты розыгрыша: 🏆 Победитель: 1. Չարլզ ✔️Проверить результаты

custom 545877225202988771831🤬16😢6🎉2🔥2custom 545860441759286384521🌚1

Signed RandomGodBot⚡️ [Рандомайзер]

10 Aug 2026, 16:16 UTC457 views9 reactionsread 10 August 2026

📑 100 участников до итогов

6🤡3

Signed 𝐌𝐚𝐤𝐧𝐞𝐦𝐲

10 Aug 2026, 12:40 UTC≈4,320 views36 reactionsread 15 August 2026
Photo

🔥 РОЗЫГРЫШ БАФФНУТОГО YETI! 🥶 🔝 После последнего патча Yeti получил мощный бафф, поэтому запускаем отдельный конкурс именно на него! 🎁 Приз: 🥇 Yeti ✍️ Для участия: ✅ Подпишитесь на @BloxFruitsKonkyrsi 🎯 Итоги — при 500 участниках! 🍀 Всем удачи! Возможно, именно ты заберёшь обновлённого Yeti.

28👌3😁2custom 54586044175928638452custom 54587722520298877181

Signed RandomGodBot⚡️ [Рандомайзер]

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

Citation-graph rank — 43,656 of 1,481,217entries 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.

Forward network

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.

Mentions

Named by 12 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.

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.

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

“Maknemy” (@theMaknemy), 18,160 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/theMaknemy.

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.