Telegram RegisterThe public register of Telegram
Telegram profile photo for ILCOIN News

Channel

ILCOIN News

@officialilcoin

On this record: Growth · Engagement · Posts · Cite this entry

910subscribers

-8 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001323446394
TypeChannel
Username@officialilcoin
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/officialilcoin

Growth

9109189146 August 2026 — 918 subscribers7 August 2026 — 918 subscribers15 August 2026 — 917 subscribers23 August 2026 — 910 subscribers6 August 202623 August 2026
4 measurements spanning 17 days, net -8. 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”. The vertical axis spans 909–919 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 20:14910-7
15 Aug 2026, 18:03917-1
7 Aug 2026, 20:54918no change
6 Aug 2026, 21:32918first reading

Engagement

20 posts held, back to 25 February 2026the 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.

ERR · 30 days
39.7%
avg views ÷ 910 subscribers
Avg views / post
361
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 July 2026
Posts held20 (25 February 202631 July 2026)
Views total361
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 21:32 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.

Recent posts

31 Jul 2026, 15:53 UTC361 viewsread 6 August 2026
Photo

⚠️ ANOTHER WILC BURN IS COMING SOON! ⚠️ Two token burns completed; another is coming. On the 15th of August, 2026, there will be another... 25 MILLION (25.000.000) WRAPPED ILCOIN 🔥 BURNED 🔥 ...across all integrated blockchains. This will bring the total burned tokens up to 75 Million (75.000.000). Then, two weeks after, we'll be expanding for Coinbase integration on the 1st of September.

Signed Thor

16 Jul 2026, 18:17 UTC879 viewsread 6 August 2026
Photo

🔥TOTAL WILC BURNED FROM EACH INTEGRATED CHAIN🔥 2026.07.01 -25.000.000 WILC ETH: https://etherscan.io/tx/0x0c16357c91228d7014e605f796eb28acea61228263dadd2a9129e74c5d7fda54 BNB: https://bscscan.com/tx/0x64e5b43ab11782e214c461dd9be03af2e22f00cd25dea05d1ae393ecd2f2bfa3 2026.07.15 -25.000.000 WILC ETH: https://etherscan.io/tx/0x9a27545234e4739cab74898c5dbf40e5e80f62e5186d93d44be6cc369139cd48 BNB: https://bscscan.com/tx/

Signed Thor

16 Jul 2026, 01:31 UTC682 viewsread 6 August 2026
Photo

PROGRESS AS OF 2026.07.15 Binance Has Accepted To Update Our Info If you don't see the information updated, please perform a hard refresh of the page. (Ctrl + R on Windows, for example) https://bscscan.com/token/0x813bd94b8c40e0e7536a4c1438875054caef49df#transactions WILC Token Burning Today WILC ERC-20 contract burning 25M WILC (Ethereum ETH chain): https://etherscan.io/tx/0x9a27545234e4739cab74898c5dbf40e5e80f62e

Signed Thor

2 Jul 2026, 01:57 UTC843 viewsread 6 August 2026
Photo

PROGRESS AS OF TODAY 2026.07.01 WILC integrated in Binance environment at this address: https://bscscan.com/token/0x813Bd94B8C40e0E7536a4C1438875054cAeF49Df#transactions In Progress: * Updated the BEP20 contract info, currently waiting for BscScan response. * After, we will start on the swap of both sides between the ETH network and BNB network. * We will be working on adding liquidity as well. * Max Supply 1:1, s

Signed Thor

24 Jun 2026, 17:47 UTC973 viewsread 6 August 2026
Photo

CHECK WHICH DOMAIN YOU'RE USING ilcoincrypto.com 🚫 ilcoinwebwallet.com 🚫 ilcoincrypto.net ✅ ilcoinwebwallet.net ✅ Make sure you're pointing to the correct one. Our previous .com domain may have been compromised by our previous web host. The .com version is up, but they never replied to our messages; hence, why we changed to .net. So please, use the utmost precaution and... ONLY USE THE APPROVED .NET DOMAIN

Signed Thor

15 Jun 2026, 18:17 UTC≈1,140 viewsread 6 August 2026
Photo

TIMELINE UPDATE - EXTENSION Due to an overwhelming amount of requests, ILCOIN upper management has decided to extend the privatization by 10 days to allow for an ample opportunity for community members who have not yet swapped be allowed to do so. As a result, the first token burning (which was to take place today) will also be postponed to have a better estimate of how many tokens are freely available (unowned) an

Signed Thor

27 May 2026, 19:53 UTC≈1,120 viewsread 6 August 2026
Photo

The Android wallet is still undergoing some issues which we are working to solve. If you want to transfer coins from your Android wallet to the web wallet for swapping, there is an alternative way. Contact our team for assistance. Most importantly of note, swaps are working normally. Other than that, our services should be fully operational. If you find you are still having issues using our blockchain, please conta

Signed Thor

26 May 2026, 19:01 UTC848 viewsread 6 August 2026
Photo

Electricity is out at the C3P's location! We'll advise as soon as power has been restored and we bring everything back online. Apologies for the inconvenience. Downtime: Unknown

Signed Thor

18 May 2026, 19:23 UTC867 viewsread 6 August 2026
Photo

ARE YOU STILL HAVING ISSUES? Our services should be fully operational. If you find you are still having issues using our blockchain, please try using a VPN. Due to some regions blockage of crypto-related services, it may be necessary. If that does not solve the issue, please contact our team. We'll solve the issue together.

Signed Thor

15 May 2026, 17:12 UTC869 viewsread 6 August 2026
Photo

BLOCKCHAIN OFFLINE DUE TO ISP ISSUES Just our luck... a soon as we are back online from C3P synchronisation issues, our ISP is having connectivity issues in one of the C3P locations. Apologies for the inconvenience. Technicians have been notified, and it's only a matter of time before service is restored.

Signed Thor

14 May 2026, 01:40 UTC993 viewsread 6 August 2026
Photo

NETWORK ISSUES FIXED Blockchain Explorer - ONLINE ✅ ilcoincrypto.net - ONLINE ✅ QT Wallet - RECONNECTED ✅ Android Wallet - RECONNECTED ✅ Services should be fully restored. We migrated ilcoincrypto to a new web host. It's now under ilcoincrypto.net. When ilcoincrypto issue get resolved for our previous web hosting client, we can reclaim the domain. If you're experiencing any further issues, please let us know! Tha

Signed Thor

5 May 2026, 16:47 UTC848 viewsread 6 August 2026

↔️ SWAP FIX IMPLEMENTED ↔️ If someone needs to swap, please try now. The service should be fixed. If it is not fixed, please let me know!

Signed Thor

Showing the 12 most recent of 20 posts we hold for @officialilcoin. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“ILCOIN News” (@officialilcoin), 910 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/officialilcoin.

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.