Telegram RegisterThe public register of Telegram
Telegram profile photo for Holyworld | Afinka

Channel

Holyworld | Afinka

@AfinkaTG

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,872subscribers

-230 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002566347047
TypeChannel
Username@AfinkaTG
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/AfinkaTG

Topic

Giveaways & airdrops — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 the other topics.

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 in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@AfinkaTG/340 · this entry9 Jan 2026, 18:42 UTC@AfinkaPlayers/2649 Jan 2026, 18:42 UTC1.00under a minute
@AfinkaTG/341 · this entry10 Jan 2026, 17:57 UTC@AfinkaPlayers/26510 Jan 2026, 17:57 UTC1.00under a minute
@AfinkaTG/343 · this entry12 Jan 2026, 16:00 UTC@AfinkaPlayers/26712 Jan 2026, 16:00 UTC1.00under a minute
@AfinkaTG/346 · this entry28 Jan 2026, 12:29 UTC@AfinkaPlayers/27028 Jan 2026, 12:29 UTC1.00under a minute
@AfinkaTG/345 · this entry17 Jan 2026, 17:57 UTC@HolyWorIdBot/71917 Jan 2026, 17:57 UTC1.00under a minute
@HolyWorIdBot/72328 Jan 2026, 12:29 UTC@AfinkaTG/346 · this entry28 Jan 2026, 12:29 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@AfinkaPlayers10 (8/8 hand-verifiable sample passed)1.00under a minute@AfinkaPlayers (8–2)
@HolyWorIdBot5 (5/5 hand-verifiable sample passed)1.00under a minute@HolyWorIdBot (4–1)

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. None of the 6 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 27 November 2025 to 8 June 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @AfinkaPlayers. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

1,8722,1021,98713 August 2026 — 2,102 subscribers13 August 2026 — 2,102 subscribers14 August 2026 — 2,099 subscribers17 August 2026 — 2,093 subscribers20 August 2026 — 2,083 subscribers24 August 2026 — 2,076 subscribers27 August 2026 — 2,066 subscribers30 August 2026 — 2,061 subscribers2 September 2026 — 2,052 subscribers7 September 2026 — 2,027 subscribers12 September 2026 — 2,013 subscribers15 September 2026 — 2,008 subscribers29 September 2026 — 1,972 subscribers6 October 2026 — 1,950 subscribers12 October 2026 — 1,942 subscribers15 October 2026 — 1,939 subscribers18 October 2026 — 1,936 subscribers22 October 2026 — 1,926 subscribers25 October 2026 — 1,920 subscribers28 October 2026 — 1,913 subscribers31 October 2026 — 1,900 subscribers4 November 2026 — 1,895 subscribers6 November 2026 — 1,888 subscribers9 November 2026 — 1,881 subscribers14 November 2026 — 1,872 subscribers13 August 202614 November 2026
25 measurements spanning 93 days, net -230. 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 1,838–2,137 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
14 Nov 2026, 13:491,872-9
9 Nov 2026, 15:411,881-7
6 Nov 2026, 17:281,888-7
4 Nov 2026, 03:171,895-5
31 Oct 2026, 22:201,900-13
28 Oct 2026, 16:151,913-7
25 Oct 2026, 09:151,920-6
22 Oct 2026, 14:061,926-10
18 Oct 2026, 23:461,936-3
15 Oct 2026, 21:371,939-3
12 Oct 2026, 18:081,942-8
6 Oct 2026, 08:581,950-22
29 Sept 2026, 15:011,972-36
15 Sept 2026, 14:412,008-5
12 Sept 2026, 03:382,013-14
7 Sept 2026, 13:172,027-25
2 Sept 2026, 09:432,052-9
30 Aug 2026, 13:032,061-5
27 Aug 2026, 18:532,066-10
24 Aug 2026, 15:112,076first reading

Engagement

20 posts held, back to 27 November 2025 — 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 20 posts for this entry, the most recent from 8 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

16 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1275.0%
😭318.8%
🤝16.25%

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 9 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 16 reactions 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 27 November 2025 to 8 June 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

8 Jun 2026, 10:04 UTC108 viewsread 13 August 2026
Forwarded from @bedrich_tgkPhoto

🎉 ГРАНДИОЗНЫЙ РОЗЫГРЫШ 2026 ГОДА! 🎉 💰 Общий призовой фонд — 20 000 коинов! 💰 Не упусти шанс выиграть крупные призы! Участвуй прямо сейчас и стань одним из победителей. 🏆 Призы: 🥇 1 место — 10 000 коинов 🤯 🥈 2 место — 5 000 коинов 😵‍💫 🥉 3 место — 2 500 коинов 🤤 🎖 4 место — 1 500 коинов 🤫 🎖 5 место — 1 000 коинов 🤑 📌 Для участия необходимо: ✅ Подписаться на все указанные каналы: ⭐️ @bedrich_tgk ⭐️ @RP_Hydra ⭐️ @mybo…

Signed Sardor Narzimurodov

3 Jun 2026, 11:57 UTC129 viewsread 13 August 2026
Forwarded from @bedrich_tgkPhoto

🩷 Розыгрыш 1 000 коинов на HolyWorld Lite! 🩷 👀 У тебя есть шанс получить бесплатные коины на HolyWorld Lite и попасть в число победителей. Участвуй прямо сейчас! 🏆 Призы: 🥇 1 место — 300 коинов 🥈 2 место — 250 коинов 🥉 3 место — 200 коинов 🎖 4 место — 150 коинов 🎖 5 место — 100 коинов 📌 Как принять участие? 🔴 Подпишись на все каналы ниже. 🔴 Дождись подведения итогов. 📣 Каналы для подписки: ➡️ Bedrich <ТЫК> 👆 Jony_…

Signed Sardor Narzimurodov

17 May 2026, 10:30 UTC239 views3 reactionsread 13 August 2026

Парни открылся новый реферальный бот (типо как афинка) @NodeLinkBot

❤3

Signed Sardor Narzimurodov

15 Apr 2026, 06:13 UTC535 viewsread 13 August 2026

Всем привет! Афинка бот был на гране открытие, но правило 2.6 которая гласит что такого бота делать нельзя остановило открытия.

Signed Sardor Narzimurodov

29 Jan 2026, 18:41 UTC986 views1 reactionsread 13 August 2026

Переходим на канал @HolyWorIdBot там происходит голосование на роль Гл.Админа!

❤1

Signed Afinka help

28 Jan 2026, 12:29 UTC934 viewsread 13 August 2026

Нужен качественный Telegram бот или современный сайт? Готов реализовать вашу идею за низкую цену и в короткие сроки. Языки разработки: Python и JavaScript. Пишите, обсудим, и я сразу приступлю к работе. Для связи: @nb_lover

Signed QWERTY

17 Jan 2026, 17:57 UTC≈1,020 viewsread 13 August 2026

🔥 Добрый день, дорогие пользователи бота Afinka! Недавно владелец проекта, известный вам как Бедрич, добровольно покинул свой пост. 🤍 На данный момент владельцем проекта Afinka стал я. Псевдоним у меня появится немного позже. Моя главная цель — сделать Afinka и всех её пользователей счастливее. Я приложу максимум усилий, чтобы проект развивался, становился лучше и процветал. Надеюсь на продуктивное и долгосрочное …

Signed Afinka поддержка

12 Jan 2026, 16:00 UTC732 viewsread 13 August 2026
Photo

🎉 Бот Afinka 26 официально открыт! Он уже ждёт вас с обновлённым дизайном и зимними обновлениями ❄️ ⛓ Присоединяйся быстрее и зарабатывай легко и в удовольствие 💸 ⬅️ @hwAfinkaBot ➡️ 👀 Следите за новостями в официальных каналах: 🖥 Официальный канал Afinka Bot — @HolyWorIdBot 🔗 Afinka | Players — @AfinkaPlayers ✉️ Holyworld | Afinka — @AfinkaTG 🤖 Сам бот Afinka: @hwAfinkaBot

Signed °♡✧*𝗡ϒ𝗥𝓞☓Ể𝘓*✧♡°

12 Jan 2026, 15:30 UTC326 viewsread 13 August 2026
Forwarded from @HolyWorIdBot

Новости! Открытье бота Afinka 26 через 30 минут.

Signed °♡✧*𝗡ϒ𝗥𝓞☓Ể𝘓*✧♡°

10 Jan 2026, 17:57 UTC493 views2 reactionsread 13 August 2026
Photo

📢 Поиск спонсоров для бота Afinka — 🔥 @hwAfinkaBot 🔥 💰 Прозрачные условия сотрудничества: Вы платите за каждого подписчика, который переходит на ваш Telegram-канал через бота. 📉 Чем больше заказ — тем ниже цена за подписчика: • до 100 подписчиков — 2 ₽ / саб • 100–300 подписчиков — 1,9 ₽ / саб • 300–500 подписчиков — 1,8 ₽ / саб • 500–1000 подписчиков — 1,7 ₽ / саб • 1000+ подписчиков — 1,6 ₽ / саб 🛒 После покупки…

❤1🤝1

Signed °♡✧*𝗡ϒ𝗥𝓞☓Ể𝘓*✧♡°

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

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.

Mentions

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

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

“Holyworld | Afinka” (@AfinkaTG), 1,872 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/AfinkaTG.

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.