Other / unclassifiable — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 47% 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 (4 of the pairs behind the counts below)
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 2 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 9 comparable posts for this entry, running 23 July 2026 to 4 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 @ajjeidnxoeodjnd — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 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.
Growth
13 measurements spanning 66 days, net -2,440. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Oct 2026, 21:09
72
+2
1 Oct 2026, 18:18
70
+20
17 Sept 2026, 08:37
50
+9
8 Sept 2026, 14:56
41
-4
30 Aug 2026, 20:34
45
-2,542
27 Aug 2026, 13:17
2,587
+53
24 Aug 2026, 22:33
2,534
+5
21 Aug 2026, 00:43
2,529
+1
18 Aug 2026, 07:05
2,528
+18
15 Aug 2026, 04:46
2,510
+3
11 Aug 2026, 22:54
2,507
-5
7 Aug 2026, 20:17
2,512
no change
7 Aug 2026, 20:02
2,512
first reading
Engagement
20 posts held, back to 22 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
1m 00s
Average length
30s
Measured directly from 2 videos 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.
Reaction mix
46 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 30.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
14
30.4%
🖕
10
21.7%
🥰
8
17.4%
🤣
4
8.70%
👍
3
6.52%
🔥
3
6.52%
🤡
2
4.35%
😡
1
2.17%
🤬
1
2.17%
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 46 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 22 July 2026 to 6 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.
السلام علیکم گائز انتہائی افسوس ہے یہ پوسٹ لگانی پڑ رہی ہے جیسا کہ اپ کو پتہ ہے کہ مارکیٹ میں اس وقت جوشو شوق سے سکیمرز لوٹ رہے ہیں برائے مہربانی کر کے اپ کو جو چیز بھی چاہیے ہم سے رابطہ کریں انشاءاللہ مارکیٹ میں اپ کو یہ نہیں بولے گا کوئی کہ بلال اور طلحہ سکیمرز ہیں ایک تو سب سے کم ریٹ میں اپ کو چیز ملے گی اگر ہوئی تو اور انشاءاللہ اپ کو گلا نہیں ائے گا
@bilal_babar_982
@Itxtalha750
*BILAL-MD ❮ BUG BOT ❯*
NEW UPDATED RELEASED ✅
NEW ADDED COMMANDS ➕
*REMINI*
• CREATE AI PHOTOS
• REMOVE BACKGROUND OF PICS
• CHANGE BACKGROUND OF PICS
• ENHANCE PHOTO QUALITY HD
• EDIT YOUR PHOTO
*IMAGINE*
CREATE AI IMAGES USING PROMOTS
*.IMAGINE [IMAGE PROMOT TEXT]*
THIS COMMAND BACKUP IS
*IMAGINE2*
THEIR COMMAND BACKUP IS
*IMAGINE3*
CREATE UNLIMITED IMAGES USING AI COMPLETLY FREE WORKS 24/7
*AIVIDEO*
CREATE VID…
Telegram MD BOT script
All download
TT FB ig song video twitter URL SIM deta voice to tex all script encrypt and decrypt all to z work
Special autopost
@Tele_bilalkingbot
Test this bot
@Bilal_vipkingbot
New bug add use this bot
/bilal-efcenew
/bilal-crash
/bilal-freez
Showing the 12 most recent of 20 posts we hold for @ajjeidnxoeodjnd. 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.
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 12 October 2026 — this
entry's latest reading, not the date you are reading this.
“Bilal_King_Vip” (@ajjeidnxoeodjnd), 72 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/ajjeidnxoeodjnd.
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.
