Telegram RegisterThe public register of Telegram
Telegram profile photo for Afinka News

Channel

Afinka News

@HolyWorIdBot

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

1,712subscribers

-223 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-1002088501332
TypeChannel
Username@HolyWorIdBot
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/HolyWorIdBot

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 96% 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 1 other registered channel. 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 (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@AfinkaTG/34517 Jan 2026, 17:57 UTC@HolyWorIdBot/719 · this entry17 Jan 2026, 17:57 UTC1.00under a minute
@HolyWorIdBot/723 · this entry28 Jan 2026, 12:29 UTC@AfinkaTG/34628 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
@AfinkaTG5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (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 0 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 8 comparable posts for this entry, running 17 January 2026 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 channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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,7121,9361,82413 August 2026 — 1,935 subscribers13 August 2026 — 1,936 subscribers16 August 2026 — 1,930 subscribers19 August 2026 — 1,917 subscribers23 August 2026 — 1,911 subscribers26 August 2026 — 1,907 subscribers29 August 2026 — 1,899 subscribers1 September 2026 — 1,889 subscribers4 September 2026 — 1,864 subscribers9 September 2026 — 1,857 subscribers13 September 2026 — 1,849 subscribers18 September 2026 — 1,842 subscribers27 September 2026 — 1,821 subscribers5 October 2026 — 1,792 subscribers11 October 2026 — 1,782 subscribers14 October 2026 — 1,776 subscribers17 October 2026 — 1,772 subscribers21 October 2026 — 1,764 subscribers24 October 2026 — 1,757 subscribers27 October 2026 — 1,749 subscribers30 October 2026 — 1,744 subscribers2 November 2026 — 1,737 subscribers5 November 2026 — 1,732 subscribers9 November 2026 — 1,721 subscribers13 November 2026 — 1,712 subscribers13 August 202613 November 2026
25 measurements spanning 92 days, net -223. 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,678–1,970 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
13 Nov 2026, 16:111,712-9
9 Nov 2026, 03:161,721-11
5 Nov 2026, 09:491,732-5
2 Nov 2026, 17:551,737-7
30 Oct 2026, 08:091,744-5
27 Oct 2026, 18:071,749-8
24 Oct 2026, 10:551,757-7
21 Oct 2026, 06:361,764-8
17 Oct 2026, 21:061,772-4
14 Oct 2026, 22:261,776-6
11 Oct 2026, 05:221,782-10
5 Oct 2026, 09:171,792-29
27 Sept 2026, 06:581,821-21
18 Sept 2026, 07:201,842-7
13 Sept 2026, 19:191,849-8
9 Sept 2026, 19:211,857-7
4 Sept 2026, 12:191,864-25
1 Sept 2026, 04:051,889-10
29 Aug 2026, 04:051,899-8
26 Aug 2026, 13:361,907first reading

Engagement

20 posts held, back to 17 January 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 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

34 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 58.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2058.8%
👍1029.4%
🔥38.82%
🎉12.94%

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 12 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 34 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 17 January 2026 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.

Telegram Stars

Stars received
7
across the posts below
Posts paid on
3
of 18 we hold a reading for · 17%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @HolyWorIdBot. 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 20 most recent posts we hold for this entry, published 17 January 2026 to 8 June 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

8 Jun 2026, 10:04 UTC33 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 Holyworld | Afinka

3 Jun 2026, 11:57 UTC40 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 Holyworld | Afinka

17 May 2026, 10:30 UTC113 views1 reactionsread 13 August 2026

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

👍1

15 Apr 2026, 06:20 UTC176 viewsread 13 August 2026
Forwarded from @AfinkaTG

Posted without readable text

Signed Holyworld | Afinka

15 Apr 2026, 06:14 UTC175 views2 reactionsread 13 August 2026
Forwarded from @AfinkaTG

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

👍2

Signed Holyworld | Afinka

1 Feb 2026, 04:50 UTC620 views11 reactions1 Starread 13 August 2026
Photo

Наш состав:

❤9🎉1👍1

Signed Holyworld | Afinka

31 Jan 2026, 09:43 UTC606 views6 reactions5 Starsread 13 August 2026

Победил кандидат №1

👍5❤1

30 Jan 2026, 15:09 UTC564 views2 reactions1 Starread 13 August 2026
Photo

Спойлер х2

❤2

Signed Holyworld | Afinka

29 Jan 2026, 18:42 UTC471 views2 reactionsread 13 August 2026

Итоги ровно через 24 часа!

❤2

Signed Holyworld | Afinka

29 Jan 2026, 18:40 UTC451 views1 reactionsread 13 August 2026
Poll

Попросил всех кандидатов написать кратко как они будут улучшать бота Afinka. Выберайте теперь сами.

  1. Кандидат №175%
  2. Кандидат №27%
  3. Кандидат №310%
  4. Кандидат №48%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

❤1

Signed Holyworld | Afinka

29 Jan 2026, 18:40 UTC382 viewsread 13 August 2026

Кандидат №1 Я буду обеспечивать стабильную работу Afinka 24/7, регулярно выпускать качественные обновления и проводить розыгрыши. Бывший кодер Afinka Кандидат №2 Я буду строго следить за соблюдением правил, относиться ко всем честно и без исключений, выпускать обновления каждый месяц и делать бота лучше с каждым днём. Ст.Модер Afinka Кандидат №3 Я буду радовать вас контентом каждый день, никогда не отключать бота и…

Signed Holyworld | Afinka

29 Jan 2026, 18:34 UTC324 views1 reactionsread 13 August 2026

Итак...... Пора выбрать человека на должность ГЛ.Админа который будет управлять ботом и всеми каналами.

🔥1

Signed Holyworld | Afinka

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

29 Jan 2026, 18:40 UTCAnonymous Poll116 voters

Попросил всех кандидатов написать кратко как они будут улучшать бота Afinka. Выберайте теперь сами.

  1. Кандидат №175%
  2. Кандидат №27%
  3. Кандидат №310%
  4. Кандидат №48%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 17 January 2026 to 8 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“Afinka News” (@HolyWorIdBot), 1,712 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/HolyWorIdBot.

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.