Channel
@biggesttracker
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
20subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001809102428 |
|---|---|
| Type | Channel |
| Username | @biggesttracker |
| Description | Buybot: @biggestbuybot Groups: @biggesttrending Contact: @newutilitystore |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/biggesttracker |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 15:04 | 20 | no change |
| 9 Aug 2026, 15:46 | 20 | first reading |
20 posts held, back to 12 September 2024 — 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 pageof 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 2 May 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 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.
Announcement 📢 We are preparing to unveil two powerful utility tools designed to bring real value to the crypto ecosystem. For detailed information, early access opportunities, and dedicated community support, we invite you to join our official community group. Official Group: @pumploop
Task Plan: 1. We will routinely visit the Twitter and Telegram accounts of Pumpfun, Moonshot, Cookmeme, Bonkfun, and Pumpkin. • Under each new post, we will leave a comment using a standard message we have prepared. 2. We have the Telegram addresses of some projects that are listed and trending in our ecosystem. • We will visit these projects and inform them that they are listed and trending on Mango Trending. 3…
Hello Fam! First of all, Mango Trending is now live. During the beta phase, all projects can be listed on the platform for free. Listing covers: • The entire Solana ecosystem • Pump.fun and similar models You can list your project in the following ways: • In Telegram groups where you are an admin • In groups where the Mango Tech bot is also an admin • Or by messaging the bot directly in private chat Additiona…
Hello Dear Mango Tech Token Family, We have completed two more important steps in Mango Trending! Silver Trending and Gold Trending are now live. Our next goal is to complete Diamond Trending! We have also made some improvements to the trend charts and will continue working to enhance the platform. 📌 Silver Trending: https://t.me/mangotrending/13/399 📌 Gold Trending: https://t.me/mangotrending/14/400 Thank you f…
Mango Tech Token & Mango Trending Ecosystem – A New Era Begins! The Mango Trending ecosystem instantly lists newly launched projects in the New Listings group, giving investors early access. Currently, Solana and Pumpfun projects are supported, with future expansion to major networks like ETH, BNB, TON, XRP, TRON, AVAX, and more. ✅ Instant New Listings ✅ Start Voting & Vote Now ⏳ Trend Competition: Bronze, Silver, …
🟢 Buy Bot New Group Added Chain: BSC Token: 0x14A2db256Ef18c4f7165d5E48f65a528b4155100 Group: RBCAT ARMY 💹Chart ♻️Trade 💥Groups ⚙️Tracker 🔸Trending
🟢 Buy Bot New Group Added Chain: BSC Token: 0x14A2db256Ef18c4f7165d5E48f65a528b4155100 Group: RBCAT ARMY 💹Chart ♻️Trade 💥Groups ⚙️Tracker 🔸Trending
🟢 Buy Bot New Group Added Chain: BSC Token: 0x8785d80E42B72376F21b6b293B9e8f3bb2fA81ad Group: CryptoDevFr Token 💹Chart ♻️Trade 💥Groups ⚙️Tracker 🔸Trending
🟢 Buy Bot New Group Added Chain: BSC Token: 0x364d19dbf3f13be2c09eda69535d1bd975447ef1 Group: BIGGEST SHILL 💹Chart ♻️Trade 💥Groups ⚙️Tracker 🔸Trending
🟢 Buy Bot New Group Added Chain: ETH Token: 0x812ba41e071c7b7fa4ebcfb62df5f45f6fa853ee Group: BIGGEST SHILL 💹Chart ♻️Trade 💥Groups ⚙️Tracker 🔸Trending
🟢DADDY Entered BSC TRENDING ! Token: 0xf590153d02369d2e05f8400fe65aafd97e1e6c57 Group:DADDY
🟢 Buy Bot New Group Added Chain: BSC Token: 0xf590153d02369d2e05f8400fe65aafd97e1e6c57 Group: BIGGEST SHILL 💹Chart ♻️Trade 💥Groups ⚙️Tracker 🔸Trending
Showing the 12 most recent of 20 posts we hold for @biggesttracker. 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.
Citation-graph rank — 587,481 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
@biggesttracker named 4 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Biggest Tracker” (@biggesttracker), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/biggesttracker.
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.