BitcoinEthereumTetherXRPCardanoDogeCoinSolanaTron - $BIGCOIN is being protected by @SafeguardRobot Click below to verify you're human

Channel
BitcoinEthereumTetherXRPCardanoDogeCoinSolanaTron - $BIGCOIN
@BigcoinERC20
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001979573622 |
|---|---|
| Type | Channel |
| Username | @BigcoinERC20 |
| Created | 22 August 2023 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BigcoinERC20 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:31 | 10 | no change |
| 7 Aug 2026, 10:29 | 10 | first reading |
Engagement
16 posts held, back to 22 August 2023 — 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 16 posts for this entry, the most recent from 22 August 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 4
- Links
- 7
Lifetime counters from Telegram’s own channel header, read 12 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.
Recent posts
DEV BUY BACK & BURN 🔥🔥🔥
https://etherscan.io/tx/0x83eb2eda41a35e986e3b4b61ccddd5cf9efff9b0df9f9e3a0477907068f2f89a
Big coin ⬜️🟥 https://t.me/BigcoinERC20 https://www.dextools.io/app/ether/pair-explorer/0xa3a4e90173774ae5185aa1440ddbacb1a355e052 0/2
TRENDING PAID
https://etherscan.io/tx/0xcdae50048c35ee3964d30593d29205fc4633d69f499138bcbb15d52e53551c0f
𝐓𝐇𝐈𝐒 𝐈𝐒 𝐍𝐎𝐓 𝐁𝐈𝐓𝐂𝐎𝐈𝐍, 𝐓𝐇𝐈𝐒 𝐈𝐒 𝐁𝐈𝐆𝐂𝐎𝐈𝐍 𝐖𝐇𝐈𝐂𝐇 𝐈𝐒 𝐁𝐄𝐓𝐓𝐄𝐑 𝐀𝐍𝐃 𝐖𝐈𝐋𝐋 𝐁𝐈𝐆𝐆𝐄𝐑 𝐓𝐇𝐀𝐍 𝐁𝐈𝐓𝐂𝐎𝐈𝐍!!!
🎒BitcoinEthereumTetherXRPCardanoDogeCoinSolanaTron 🎒$BIGCOIN Degen at 10k MC taking a shot on $BIGCOIN these tickers have been running heavy Looks like it just locked for 2 months as well and taxes are only 0/2 so watch slip! Dex: https://dexscreener.com/ethereum/0xa3A4E90173774ae5185aA1440dDBACB1A355e052 CA: 0xcf06278d31e6889A1E32563d2C314E8968651BC7 Telegram : https://t.me/BigcoinERC20 Twitter : https://twitt…
RENOUNCED
https://etherscan.io/tx/0xaa56968f7e06cf721c0ed90371d1ff375f7fc17e76c517ca48f762e4907ff3b3
LOCK 2 MONTHS
https://app.uncx.network/amm/uni-v2/pair/0xa3A4E90173774ae5185aA1440dDBACB1A355e052
Showing the 12 most recent of 16 posts we hold for @BigcoinERC20. 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
Citation-graph rank — 1,117,657 of 1,480,944entries 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.
Forward network
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 1 registered channel — 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“BitcoinEthereumTetherXRPCardanoDogeCoinSolanaTron - $BIGCOIN” (@BigcoinERC20), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/BigcoinERC20.
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.