๐ROSE๐ PREMIUM BOT ๐ ๐SRC LEAKED๐ ๐๏ธALL FEATURES LOADED ๐ ๐๏ธLEAKED BY @fruxff570 ๐ ๐Click here ๐ https://t.me/Frux_api_strebot?start=BQADAQADog4AArOsuEf8Anxg_E9xbBYE
Signed ๐ ๐ ๐๐๐ ๐๐ ๐

Channel
@fruxapii
On this record: Topic ยท Observations ยท Channels linked by matching posts ยท Growth ยท Engagement ยท Reactions ยท Posts ยท Citations ยท Handles named that no longer answer ยท Cite this entry
531subscribers
-19 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1003905935647 |
|---|---|
| Type | Channel |
| Username | @fruxapii |
| Created | Between 1 April 2026 and 5 August 2026 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/fruxapii |
Hacking & security โ 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 2 other registered channels. This entry also sits inside a group of 4 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @fruxapii/133 ยท this entry6 Aug 2026, 10:08 UTC | @vaibhavxapi/19576 Aug 2026, 10:08 UTC | 1.00 | under a minute |
| @fruxapii/136 ยท this entry6 Aug 2026, 20:38 UTC | @vaibhavxapi/19716 Aug 2026, 20:38 UTC | 1.00 | under a minute |
| @vaibhavxapi/19737 Aug 2026, 03:18 UTC | @fruxapii/138 ยท this entry7 Aug 2026, 03:18 UTC | 1.00 | under a minute |
| @vaibhavxapi/19757 Aug 2026, 08:49 UTC | @fruxapii/139 ยท this entry7 Aug 2026, 08:49 UTC | 1.00 | under a minute |
| @fruxapii/140 ยท this entry7 Aug 2026, 08:57 UTC | @vaibhavxapi/19767 Aug 2026, 08:57 UTC | 1.00 | under a minute |
| @fruxapii/133 ยท this entry6 Aug 2026, 10:08 UTC | @vaibhavapix/8516 Aug 2026, 10:08 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @vaibhavxapi | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (3โ2) |
| @vaibhavapix | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4โ3) |
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 13 comparable posts for this entry, running 5 August 2026 to 8 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.
Of the group of 4 channels, the one whose matching posts we hold earliest is @fruxapii โ 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 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.
This channel is in a group of 4 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 07:16 | 531 | -9 |
| 7 Nov 2026, 04:00 | 540 | -11 |
| 30 Oct 2026, 10:51 | 551 | -14 |
| 22 Oct 2026, 09:41 | 565 | -4 |
| 14 Oct 2026, 21:45 | 569 | -8 |
| 8 Oct 2026, 04:38 | 577 | -16 |
| 28 Sept 2026, 14:56 | 593 | -10 |
| 15 Sept 2026, 06:15 | 603 | -9 |
| 8 Sept 2026, 10:39 | 612 | +1 |
| 30 Aug 2026, 18:23 | 611 | +63 |
| 24 Aug 2026, 19:04 | 548 | +5 |
| 16 Aug 2026, 20:34 | 543 | -11 |
| 8 Aug 2026, 17:41 | 554 | +4 |
| 8 Aug 2026, 03:45 | 550 | no change |
| 7 Aug 2026, 23:32 | 550 | first reading |
20 posts held, back to 5 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 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 August 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 1 | 100.0% |
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 1 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 1 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 5 August 2026 to 8 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.
๐ROSE๐ PREMIUM BOT ๐ ๐SRC LEAKED๐ ๐๏ธALL FEATURES LOADED ๐ ๐๏ธLEAKED BY @fruxff570 ๐ ๐Click here ๐ https://t.me/Frux_api_strebot?start=BQADAQADog4AArOsuEf8Anxg_E9xbBYE
Signed ๐ ๐ ๐๐๐ ๐๐ ๐
๐ฅ FreeFire Accounts Follow Capability Checker ๐ฅ Automate account screening for follow actions โ fast, secure, and live! โจ Features: - โก Multi-threaded (5 workers) for blazing speed - ๐ Auto JWT fetch โ no manual tokens needed - ๐ก Live progress โ see each accountโs status instantly - ๐พ Auto-saves capable accounts to accounts_cap.json - ๐ง Full error feedback โ HTTP codes, server fail_info, exceptions ๐ฏ Perfect for: โฆ
Signed ๐ ๐ ๐๐๐ ๐๐ ๐
โข FF ACCOUNT 30 DAY BAN โข FF ACCOUNT PERMANENT BAN โข ACCESS TOKEN TO BIND CHANGE โข ACCESS TOKEN TO UNBIND โข ACCESS TOKEN TO BIND CANCEL โข ACCESS TOKEN TO CHECK BIND INFO โข REVOKE ACCESS TOKEN โข ACCESS TOKEN TO LOGIN DM - @T10_Rox
Signed T10 ใก ๐น๐ถ๐ฟ
๐ ๐๐๐4 ๐๐๐ ๐๐๐๐๐๐ ๐ โข ๐ ๐๐๐๐ ๐๐๐๐๐๐๐ ๐๐๐๐ ๐๐๐๐๐๐๐ ๐๐ โค โข ๐๐๐๐๐๐๐๐ ๐๐๐ ๐๐๐๐๐๐๐ ๐ ๐จโ๐ป ๐๐๐๐๐๐๐: @spideyabd ๐๐๐ @ROX_T10 ๐จโ๐ป ๐ ๐๐๐๐ @SPIDEYFREEFILES ๐๐๐ @T10INDRAJIT ๐ ๐๐ ๐๐๐๐ ๐๐๐๐๐ ๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐๐... ๐
Signed T10 ใก ๐น๐ถ๐ฟ
DOSTO AJ 1K COMPLETE HOJYEGA KYA https://t.me/fruxapi
Signed ๐ ๐ ๐๐๐ ๐๐ ๐
DM TO BUY 30 DAY BAN SRC DM - @T10_ROX
Signed T10 ใก ๐น๐ถ๐ฟ
๐ T10 SMS BOMBER SCRIPT ๐ Version: 1.0 Status: โ Fully Updated & Working โญ Features: - 70+ live Indian SMS APIs - Infinite bombing loop - Colorful terminal UI - No dependency hell (uses curl & cfonts optional) - Lightweight & fast ๐ก๏ธ For Educational Purposes Only ๐ซ Not For Sale โ Strictly for security research ๐จโ๐ป Created By: @spideyabd & @ROX_T10 ๐จโ๐ป ๐ Join @SPIDEYFREEFILES And @T10INDRAJIT For More Tools And Sโฆ
Signed T10 ใก ๐น๐ถ๐ฟ
๐๏ธTELEGRAM PRIME HOSTING BOT SRC LIG ๐๏ธ ๐ User Panel ๐ Admin Panel ๐ Hosting Plans (Basic / Pro / Premium / Enterprise) ๐ Buy Hosting ๐ bKash / Nagad / Rocket Payment ๐ Auto Order System ๐ Support Ticket ๐ User Statistics ๐ My Services ๐ Order History ๐ License Key Generator ๐ Domain Checker ๐ Server Status ๐ Broadcast Message ๐ Promo Code System ๐ Referral System ๐ Daily Bonus ๐ Anti-Spam Protection ๐ Admin-Only Coโฆ
Signed ๐ ๐ ๐๐๐ ๐๐ ๐
๐๐๐๐๐๐๐ ๐๐ ๐ ๐๐๐ ๐๐๐ ๐ ๐'๐ ๐ ๐๐๐ ๐๐ โโโโโโโโโโโโโโโโโโโ ๐ ๐๐๐๐๐๐๐๐ : ๐ ๐๐๐ ๐ ๐๐๐๐ ๐๐๐๐ : ๐๐๐๐๐๐๐ ๐๐๐๐ ๐ ๐๐๐ : ๐๐ ๐ฎ๐ณ ๐๐๐๐๐๐๐ : ๐๐๐๐๐ โโโโโโโโโโโโโโโโโโโ ๐ ๐ผ๐ฐ๐ธ๐ฝ ๐ฒ๐ท๐ฐ๐ฝ๐ฝ๐ด๐ป ๐ https://t.me/fruxapi ๐ ๐ต๐๐๐ ๐ฒ๐พ๐ผ๐ผ๐๐ฝ๐ธ๐๐ ๐ https://t.me/fruxapis ๐ ๐ฑ๐ฐ๐ฒ๐บ๐๐ฟ ๐ฒ๐ท๐ฐ๐ฝ๐ฝ๐ด๐ป ๐ https://t.me/fruxapii ๐ ๐ฑ๐ฐ๐ฒ๐บ๐๐ฟ ๐ถ๐๐พ๐๐ฟ ๐ https://t.me/fruxgroup ๐๐ฐ๐ง๐๐ซ :@fruxff570 ๐ "๐๐๐ช๐จ๐ก๐ ๐๐ช๐ก๐๐ฃ๐ ๐๐๐๐ฃ, ๐ง๐๐๐๐๐๐ฃ ๐ ๐๐ช๐ ๐๐๐ฃ๐๐ฉ๐ ๐๐๐๐ฃ, ๐ ๐ค ๐๐๐๐ ๐จ๐ ๐๐ช๐๐, ๐ฌ๐ค๐ ๐จ๐๐ฅ๐ฃ๐
Signed ๐ ๐ ๐๐๐ ๐๐ ๐
๐BAN CHECK๐ API SRC ๐ ๐Working all region๐ ๐Ready to deploy vercel ๐ ๐Click here ๐ https://t.me/Frux_api_strebot?start=BQADAQADbxEAAgFoqUfN8omWLMXOoBYE ๐โ๐๏ธLEAKED BY :๐ @fruxff570
Signed ๐ ๐ ๐๐๐ ๐๐ ๐
๐INFO API๐ ALL SERVER ๐WORKING API๐ With endpoint given ๐Credit ๐ @fruxff570๐ Api link here ๐ https://t.me/Frux_api_strebot?start=BQADAQAD0A0AAgFoqUcrWN_SrIJvRxYE
Signed ๐ ๐ ๐๐๐ ๐๐ ๐
๐INFO API๐ ALL SERVER ๐WORKING API๐ ๐Credit ๐ @fruxff570๐ Api link here ๐
Signed ๐ ๐ ๐๐๐ ๐๐ ๐
Showing the 12 most recent of 20 posts we hold for @fruxapii. 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.
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 3 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.
@fruxapii 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.
References a handle that is not a live channel โ we have no record it ever was one.
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 17 November 2026 โ this entry's latest reading, not the date you are reading this.
โโก๐๐ฅ๐จ๐ซ ๐๐ฃ๐ ๐ข๐ณ๐ณ๐ถ๐ฐ๐ถ๐ฎ๐น โกโ (@fruxapii), 531 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/fruxapii.
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.