File, posted without a caption
โค3
Signed โโAYANA

Channel
@AYU_XU
On this record: Topic ยท Observations ยท Channels linked by matching posts ยท Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Posts edited after publishing ยท Posts recorded as deleted ยท Citations ยท Handles named that no longer answer ยท Cite this entry
19,821subscribers
+2,535 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
| Telegram ID | -1002234662123 |
|---|---|
| Type | Channel |
| Username | @AYU_XU |
| Description | ๐Welcome to our Tech & Crypto Hub! Daily tech news, crypto updates & verified airdrops. ๐ท Advertise https://telega.io/channels/ayu_xu/card Dm - @AYANA_ROBOT โขCrypto insights โขAirdrop alerts โขtools & bots โขClean, high-quality content |
| Created | Between 1 June 2024 and 30 September 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/AYU_XU |
Technology โ 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @Ayutech01/716230 Jul 2026, 16:59 UTC | @AYU_XU/7758 ยท this entry6 Aug 2026, 08:40 UTC | 1.00 | 7 days |
| @AYU_XU/7769 ยท this entry7 Aug 2026, 16:59 UTC | @Ayutech01/71677 Aug 2026, 17:00 UTC | 1.00 | under a minute |
| @AYU_XU/7807 ยท this entry12 Aug 2026, 13:46 UTC | @Ayutech01/716812 Aug 2026, 13:46 UTC | 1.00 | under a minute |
| @AYU_XU/7876 ยท this entry18 Aug 2026, 10:04 UTC | @Ayutech01/717418 Aug 2026, 10:04 UTC | 1.00 | under a minute |
| @AYU_XU/7935 ยท this entry24 Aug 2026, 23:01 UTC | @Ayutech01/717724 Aug 2026, 23:02 UTC | 1.00 | under a minute |
| @AYU_XU/7999 ยท this entry30 Aug 2026, 05:02 UTC | @Ayutech01/717831 Aug 2026, 10:49 UTC | 1.00 | 30 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Ayutech01 | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5โ2) |
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. 1 of the 1 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 64 comparable posts for this entry, running 4 August 2026 to 16 November 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @Ayutech01. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 17 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.
This channel is in a group of 2 registered channels linked by matching posts. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 23:59 | 19,821 | -5 |
| 12 Nov 2026, 12:50 | 19,826 | +81 |
| 10 Nov 2026, 09:14 | 19,745 | -61 |
| 8 Nov 2026, 20:07 | 19,806 | +75 |
| 7 Nov 2026, 12:08 | 19,731 | +30 |
| 6 Nov 2026, 11:46 | 19,701 | +96 |
| 5 Nov 2026, 09:10 | 19,605 | +31 |
| 4 Nov 2026, 11:37 | 19,574 | +2 |
| 3 Nov 2026, 14:10 | 19,572 | +31 |
| 2 Nov 2026, 17:07 | 19,541 | -28 |
| 1 Nov 2026, 19:19 | 19,569 | +81 |
| 31 Oct 2026, 18:08 | 19,488 | +99 |
| 30 Oct 2026, 17:56 | 19,389 | -43 |
| 29 Oct 2026, 15:45 | 19,432 | +37 |
| 28 Oct 2026, 16:31 | 19,395 | +53 |
| 27 Oct 2026, 18:19 | 19,342 | +62 |
| 26 Oct 2026, 19:21 | 19,280 | -30 |
| 25 Oct 2026, 20:29 | 19,310 | +29 |
| 24 Oct 2026, 23:16 | 19,281 | +156 |
| 23 Oct 2026, 20:48 | 19,125 | first reading |
158 posts held, back to 4 August 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 95 pages of Telegramโs post history, 20 posts per page.
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.
| Window | Rolling 30 days ยท latest post in window 17 November 2026 |
|---|---|
| Posts held | 158 (4 August 2026 โ 17 November 2026) |
| Views total | 33,467 |
| Reactions total | 585 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 17 Nov 2026, 17:02 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.
Lifetime counters from Telegramโs own channel header, read 17 November 2026 โ not the date at the top of this page, which is when the subscriber count was last read. Below Telegramโs rounding threshold, so these counts are exact.
Measured directly from 12 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.
1,030 reactions across 157 posts, in 15 distinct kinds. The most used accounts for 77.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 800 | 77.7% | |
| ๐ | 137 | 13.3% | |
| ๐ฅ | 38 | 3.69% | |
| ๐ | 27 | 2.62% | |
| ๐ฅฐ | 6 | 0.583% | |
| ๐ญ | 5 | 0.485% | |
| โคโ๐ฅ | 3 | 0.291% | |
| ๐ค | 3 | 0.291% | |
| ๐ฏ | 2 | 0.194% | |
| ๐ | 2 | 0.194% | |
| ๐ข | 2 | 0.194% | |
| ๐คทโโ | 2 | 0.194% | |
| โก | 1 | 0.097% | |
| ๐ | 1 | 0.097% | |
| ๐ | 1 | 0.097% |
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 157 of the 158 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,030 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 158 most recent posts we hold, published 4 August 2026 to 17 November 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โs own โeditedโ marker: 8 of 52 posts held from the last 30 days (15.4%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before โ this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
File, posted without a caption
โค3
Signed โโAYANA
โฃ ๐๐๐&๐๐ pkgโ โฃ ๐๐ฃ๐ฃ : ๐๐๐ฅ๐ ๐ง๐จ๐ก๐ก๐๐ แ แแฐ แแฌแ React แ แณแฐแญแแ๐ซ
โค5
Signed โโAYANA
Posted without readable text
๐7๐ฅ3๐1
Signed โโAYANA
GmailOn price update แ แ guys๐ฅ Gmail แจแ2FA แตแจแแฑ - $0.33 Usdt แณแแแแฝแ Gmail แซแ2FA แตแจแแฑ - $0.31 Usdt แณแแแแฝแ ๐ซReferral commisson แ แแแแชแซ 30 แแแต แจแแ แแนแตแ แฐแ 50% commission แณแแแแฝแ แ แแต gmail แฒแจแแฑ แแแแฐ $0.17 แแแต แแ๐ฅ แจแ แแฅแ 10% Commission แจแแญแณแแ แญแแแ $0.03 Usdt แแแต แแ https://t.me/Gmailpayrobot?start=u85vBMgxaVns3 2FA แแแตแจแ Video ๐ฟ https://t.me/smart_crypto8/492 ๐ฅณ
โค10
Signed ๐๐๐๐๐
wow ๐คฉ free Gemini Pro ๐ฅณ 10+ แฐแ แตแตแแฅแ 1$ แญแฐแฃแฝแแแค แจแแซ แฅแแ Gemini Pro แแแแต แตแฝแแแฝแ ๐ฑ ๐ธ แซแตแแแ แฐแแ แ Binance แจแฐแซแฝแแตแ แแแแฅ แจ 1$ แแแฎ แแแฃแต แญแปแแ ๐ฅ ๐ฅ ๐ฅ แฅแ แแแฑแ แปแแ แฅแ แแฉแ Join แ แ ๐คแค แฅแแแฐ แจแแ แแฝแแธแแ แฐแแฝ Join แแแต แ แแฃแธแ แฅแแแฐ แแแแ แ โ ๐ฅ แแแฉแต ๐ฅ ๐ ๐ ๐ ๐ https://t.me/Ggsomabot?start=ref_CG7UFTT3 ๐ https://t.me/Ggsomabot?start=ref_CG7UFTT3 #แฅแญ #online #แตแซ #Crypto แฐแจแแช แตแซ แฅแแตแแแ โค แแจแ แ แตแญแฑ ๐ @AYU_XU
โค10
Signed โโAYANA
โฃ ๐๐๐&๐๐ pkgโ โฃ ๐๐ฃ๐ฃ : ๐๐๐ฅ๐ ๐ง๐จ๐ก๐ก๐๐ แ แแฐ แแฌแ React แ แณแฐแญแแ๐ซ
โค9
Signed ๐๐๐๐๐
โก Telegram Package แ 20Birr Package แฅแป แญแฐแซแแข โจ๏ธ APP: HTTP INJECTOR โจ๏ธ SPEED: FAST โจ๏ธ METHOD: SSH Expire Date ๐ซ: NOV 17
โค8๐1
Signed Channel Help
๐ gmail farmer แ แดแแฅแญ แจแแฎ withdrew ๐ฐ แจแแณแฐแญแแ แต แ แชแ แตแซ แแ ๐ฅ 1gmail =0.30=60etb ๐ https://t.me/Gmailpayrobot?start=u85vBMgxaVns3 2FA แแแตแจแ Video ๐ฟ https://t.me/AYU_XU/8038
โค10
Signed ๐๐๐๐๐
Guys, protect yourself from this type of link. Once you click that goddamn link, they will have full access to your device and all of your accounts and data.
โค9๐1
Signed ๐๐๐๐๐
https://t.me/MyAgeApp?startapp=r6189362753 Just start แ แ แฅแ Tg แจ แจแแณแฝแแ แตแ แแ แ แญแถ , แญแฐแฃแฝแแ @AYU_XU
โค10๐ฅ1
Signed โโAYANA
โณ My Telegram is 3 years old โ older than 48% of accounts. My Age pays AGE tokens + $GRAM for account age and lets you run a paid channel.
โค10
Signed โโAYANA
๐ฉ Collecting JCH?Try this inside Telegram: โธ Hold JCH to level up your miner โธ Start mining and claim token rewards โธ Complete app tasks for extra rewards แแแญแต https://t.me/JensenChip_bot/app?startapp=ref_6189362753
โค10
Signed โโAYANA
Showing the 12 most recent of 158 posts we hold for @AYU_XU. 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.
@AYU_XU edited 1 post after it first published โ the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too โ this register can tell you the wording changed and when, not why. How this is measured.
We recorded 19 posts on @AYU_XU as deleted โ posts this register held that were missing from the channelโs public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channelโs public page, and when โ not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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.
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.
@AYU_XU named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant โ a genuine, evidenced change, not an inference from absence.
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 15 November 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐ญ๐ก๐ข๐จ ๐๐๐ญ๐๐ซ๐ฒ๐ฉ๐ญ๐จ ๐ช๐น๐๐ชโ (@AYU_XU), 19,821 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/AYU_XU.
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.